Nov 19, 2026
Applies to: ikuTeam Office for Jira
If one person on your team can't preview attachments in ikuTeam Office while everyone else, including site admins, can see them, don't worry: this is almost always a network issue on that person's side, not a permissions problem or an issue with the app.
For one person:
the preview shows Preview blocked ("The preview can't load because of a firewall or ad blocker"), a loading error or a blank area,
the error code changes on each attempt,
a site admin can view the same attachments without any issue, and
restarting the browser or the computer doesn't help.
ikuTeam Office loads its editor from editor.ikuteam.com. When the person's browser can't reach that address at all, the preview can't load. In the browser logs (HAR file), this shows as a request with status 0 for this script:
https://editor.ikuteam.com/web-apps/apps/api/documents/api.jsA status 0 means the browser couldn't reach the server, not that access was denied. Common causes:
Stale DNS cache. The computer or internet provider has an outdated address for editor.ikuteam.com. A restart doesn't always clear it, and it can take up to 24 hours to refresh on its own.
Internet provider routing issues. A temporary break between the person's location and our servers. These usually resolve on their own.
A browser extension. Ad blockers, privacy tools or security suites sometimes block the editor script.
Corporate firewall, proxy or VPN. Network rules may block editor.ikuteam.com.
Check the connection. Ask the person to open https://editor.ikuteam.com/web-apps/apps/api/documents/api.js in their browser. If JavaScript code appears, the connection works: go to step 2. If the page is blank, times out or says the connection is blocked, go to step 4.
Hard refresh the work item. Press Ctrl + F5 (Windows) or Cmd + Shift + R (Mac) to reload everything without the cache.
Try a private or incognito window. This turns off extensions. If the preview works there, turn the extensions off one at a time to find the one that blocks it.
Allowlist the editor. Ask your IT or network team to allow this address on firewalls, proxies and content filters:
https://editor.ikuteam.comFlush the local DNS (optional). On Windows, run ipconfig /flushdns. On Mac, run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder.
Check | You should see |
|---|---|
Open https://editor.ikuteam.com/web-apps/apps/api/documents/api.js | JavaScript code |
Open the affected work item | The preview loads with no error |
Try a private or incognito window | The preview works (so an extension wasn't the cause) |
Why does the error code change every time? The code is a unique reference created for each error. Since the real issue is a connection timeout, a new code appears on every attempt. That's expected.
It fixed itself. Why? Most likely the DNS cache refreshed (this can take up to 24 hours), or the internet provider fixed a temporary routing issue.
Could it be a permissions issue? No. A permissions problem shows a consistent message, such as Access denied, and doesn't come and go. A status 0 timeout points to the network.
Our support team is happy to help. Open a request in our support portal and, if you can, attach a HAR file (see Collecting a HAR file for support).