BUG: Broken image error occurs periodically.

[Przemysław Dominik Gacia]

Broken image error occurs periodically.

Often the file disappears from the page attachments.

Sometimes, when the broken image reappears in the attachments.

The error gets very intense when there are more than 10 images on the page.

[Kevin Cox]

I am experiencing the same issue.

Feels to be for older articles?

[Diego]

Hello @Przemysław Dominik Gacia !

As I understand, images that were previously attached are broken and, from time to time, are not listed under the attachments list.

With this behavior in mind, I would like to ask you a few questions. Here we go:

1. Is this happening in recently created pages?
2. Is this affecting pages that already exist for a long time?
3. Is this happening with multiple image formats, such as PNG or JPG?
4. Is this affecting other types of file?
5. Is there any kind of error present when images are broken?
6. Are the affected images name using special characters?
7. Would it be possible for you to share screenshots of the situation that you are facing?

Just a disclaimer about the screenshots we asked you to take. It is important not to disclose any sensitive information with them because our community is an open space. Everyone can see everything that is posted here.

Let us hear from you!

[Peter Bengov]

Hi @Przemysław Dominik Gacia can you please share screenshots? Is it always the same pages and other pages are looking OK? 

Please hover over the attachments to see what are their path/link, if they have any. 

[Krzysztof Kot]

Not the original poster but we're also seeing this in long pages with lots of images. This page has 17 attachments, not all of which are used on the page:

When editing this page, the image shows successfully:

The noted file exists in the attachments list and is viewable:

Clicking on the link of the image from attachments successfully shows the image. If I cut/paste the image in edit mode and re-publish this does not fix the issue. If I remove the image in edit mode and re-upload *the same exact copy that I get from attachments* it starts to show again.

This is a major issue for two reasons:

1. There is no way to tell where/on which pages this is happening

2. The fix appears to be quite laborious

[Krzysztof Kot]

To be clear, this is happening to **some** images on **some** pages. Even on a single page it seems random as to which images will be affected and which won't.

[Owen Wallis]

Hi @Krzysztof Kot is this Confluence Cloud or Server? I work on the Cloud team and don't recall seeing the 'Broken image' tag before on the new Editor. Normally it shows as 'Failed to load'.

If you are on Cloud where are you copying and pasting the file from? Is at external source, a page with restrictions?

[Krzysztof Kot]

We are on a cloud instance. The page noted above is in the legacy editor too.

[Owen Wallis]

Understood, unfortunately my team only supports the new editor experience.

Do you have the same issue in the new editor with the same page?

Although I'm assuming there are reasons why you've not converted the page to the new editor.

One option might be to download the files and re-upload (rather than copy and paste). I know the old editor allows referencing files from restricted pages - so that could be what is happening here.

[Krzysztof Kot]

Haven't noticed this in the new editor as the majority of these pages are in the legacy editor. Conversion has not been undertaken at this stage due to the sheer amount of work this would involve so it's a little disheartening to hear it's our only option.

Good thought on referencing files in restricted spaces and we have seen that previously too but it has been ruled out as a cause in this instance.

[Owen Wallis]

Hmm, perhaps something to do with the copy and paste action then?

Where are you copying the files from?

Not a great workflow solution (sorry) but might be download then re-upload is your best bet.

[ofer rozenberg]

We just upgrade to the DC and we have the same issue !!!!   us there a fix for that?

[Krzysztof Kot]

We haven't found one outside of converting affected pages to the new editor as this comes up :(