nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Is there a new problem with rendering images in Confluence pages?

Abhay Patil

UPDATE: With latest Microsoft Edge browser update (build# 140) the Confluence pages are failing to display images. Clearing cookies, cache, history doesn't help. Problem exists in InPrivate browsing also.

OS: Windows 11
Edge: Version 140.0.3485.54 (Official build) (64-bit)

Chrome shows pages and images alright.

Today I am seeing pages with small images showing "preview unavailable" message. When I check attachments, they are good. This is a serious issue. Is this a new problem?

Attaching the message displayed when the page is rendered.

Accepted answers

Abhay Patil

Alas, someone from Atlassian could have shared the following recommended workaround for Edge - or at least pointed us to this status page. I added the exception for our site, and it worked.

Switch your tracking prevention settings from 'Strict' to the 'Balanced (Recommended)' mode in Edge.
Alternatively, add an 'Exception' for the URL you use to access Atlassian products.

All comments

Mia Tamm _Simpleasyty_

Hi @Abhay Patil,

This usually happens if the images were pasted directly from somewhere else instead of uploaded as attachments in Confluence. When that happens, the link to the image can break and you’ll see the “Preview unavailable” message.

A couple of things you can try:

Clear your browser cache or do a hard refresh – sometimes that fixes it.
Re-upload the image using the Attachment option in Confluence (instead of pasting), which makes it more reliable.

If others can see the images but you can’t, it’s very likely a cache/browser issue on your side.

Hope this helps!

— Mia Tamm

Abhay Patil

Actually this appears to be a problem with the latest upgrade of Edge browser.
The images are indeed attachments, and I confirmed that they render alright in Chrome. I will now try to go back to an older version of Edge and retry.

Florian Riegler

We can confirm this problem with Edge version 140.0.3485.54 and Atlassian Jira Cloud.

Abhay Patil

Windows 11 latest Edge browser not rendering images in Confluence has been posted. Waiting for the resolution.

Barbara Szczesniak

@Abhay Patil This is an active incident that Atlassian is working to resolve (hopefully before my Edge gets updated to this version).

If you check the Atlassian Status page, you can monitor the progress (or subscribe to get updates by email).

Greg Lipschitz

I am seeing the same on OS X Running Chrome

Version 139.0.7258.157 (Official Build) (arm64)

Abhay Patil

Alas, someone from Atlassian could have shared the following recommended workaround for Edge - or at least pointed us to this status page. I added the exception for our site, and it worked.

Switch your tracking prevention settings from 'Strict' to the 'Balanced (Recommended)' mode in Edge.
Alternatively, add an 'Exception' for the URL you use to access Atlassian products.

Florian Riegler

This workaround works for me. After adding an exception for our Atlassian URL, Edge no longer has any problems rendering images. But this is not a permanent solution for me.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence

cloud

confluence-cloud