NOTE: This bug report is for Confluence Server. Using Confluence Cloud? See the corresponding bug report.

      If you are using version 5.8.16 or 5.8.17, or have used those versions in the past without running a script to fix the affected attachments, then you are likely affected by CONF-39975. Please see that ticket instead.

      In some cases, it is legitimate for the message "Unknown attachment" to appear. For example:

      • If you upload an attachment to a page and then delete it from the attachments list without removing the macro which references it, the macro will show "Unknown attachment".
      • If you upload an attachment on Page-A and then reference it in a macro on Page-B, then delete the original Page-A, then the attachment will also be deleted. This causes the Page-B macro to display "Unknown attachment"

      If you observed "unknown attachment" after one of these scenarios, this is not a bug, but rather expected behaviour.

      If you observed "unknown attachment" by any other scenario, it is likely a bug. If you find a way to reproduce this issue, please let us know by commenting below, with details of how to reproduce the issue and your version of confluence. If you observe something different than an "unknown attachment" message but attachments do fail to download, please let us know exactly what you see. If you observe this issue but are not on and have never been on Confluence 5.8.16 or 5.8.17, please let us know below.

      If you observe this issue you may try resolving the broken attachments using the same instructions outlined in CONF-39975 - let us know if it works or not for you.

          Form Name

            [CONFSERVER-41067] "unknown attachment" on confluence pages

            Thanks James.  I noticed the other ticket right after making my last comment.  This issue is very impactful to us, and the fix/remediation is not great.

            Richard Lange added a comment - Thanks James.  I noticed the other ticket right after making my last comment.  This issue is very impactful to us, and the fix/remediation is not great.

            Hi 90e31c90f6b6,

            I was reviewing this ticket for an unrelated issue and saw your comment.

            Given your version and description of the issue, it's very possible you're impacted by CONFSERVER-55928: Attachments become 'Unknown Attachment' in the page editor with Collaborative Editing turned on (fixed in Confluence Server and Data Center 7.13.0, 7.4.9, 7.12.1, 7.11.3).

            If that's the case, then the workaround detailed at CONFSERVER-63615: Provide workaround for fixing broken unknown attachment placeholder in storage format (fixed in Confluence Server and Data Center 7.13.0) (Reconcile Unknown Attachments) is likely to help.

            I'd recommend reviewing both issues in full. Hopefully they can shed some light on, and resolve the issue you're seeing.

            If you do continue to encounter issues, I'd recommend opening a ticket with support via https://support.atlassian.com.

            Thanks,
            James Ponting
            Premier Support Engineer

            James Ponting added a comment - Hi 90e31c90f6b6 , I was reviewing this ticket for an unrelated issue and saw your comment. Given your version and description of the issue, it's very possible you're impacted by CONFSERVER-55928: Attachments become 'Unknown Attachment' in the page editor with Collaborative Editing turned on (fixed in Confluence Server and Data Center 7.13.0, 7.4.9, 7.12.1, 7.11.3) . If that's the case, then the workaround detailed at CONFSERVER-63615: Provide workaround for fixing broken unknown attachment placeholder in storage format (fixed in Confluence Server and Data Center 7.13.0) (Reconcile Unknown Attachments) is likely to help. I'd recommend reviewing both issues in full. Hopefully they can shed some light on, and resolve the issue you're seeing. If you do continue to encounter issues, I'd recommend opening a ticket with support via https://support.atlassian.com . Thanks, James Ponting Premier Support Engineer

            Seeing this behavior in version 7.4.1

            Richard Lange added a comment - Seeing this behavior in version 7.4.1

            Patrizia added a comment -

            We are using the confluence server, version 7.4.7. and our attachments like screenshots or jpeg-images turn suddenly on one page all into "unknown attachment". We didn't do anything with the site. It happens suddenly. We had about 30 images on the site, and they are gone. I fixed it already a few month ago and added them all again. And now they are gone again! And not just this page. Also on other pages, with just maybe two images on one site - the images disappear. It is a lot of work, to renew all these pages. And the worst thing is, that we don't know why it happens and where it happens. We can't see which pages are also affected by it.

            What do I have to do? Here are so many tickets with "unknown attachments", that I lose track. Do I have to download the app "Reconcile unknown attachments" ? Will this help?

            Patrizia added a comment - We are using the confluence server, version 7.4.7. and our attachments like screenshots or jpeg-images turn suddenly on one page all into "unknown attachment". We didn't do anything with the site. It happens suddenly. We had about 30 images on the site, and they are gone. I fixed it already a few month ago and added them all again. And now they are gone again! And not just this page. Also on other pages, with just maybe two images on one site - the images disappear. It is a lot of work, to renew all these pages. And the worst thing is, that we don't know why it happens and where it happens. We can't see which pages are also affected by it. What do I have to do? Here are so many tickets with "unknown attachments", that I lose track. Do I have to download the app "Reconcile unknown attachments" ? Will this help?

            Hi, we have a problem when displaying the report with Macro "report table" when we try to get the Report Info Macro key "page: body", all the images are displayed as Unknown Attachment, this bug appeared after updating confluence to 6.3.1 reporting plugin 6.8.0

            rermakov@lanit.ru added a comment - Hi, we have a problem when displaying the report with Macro "report table" when we try to get the Report Info Macro key "page: body", all the images are displayed as Unknown Attachment, this bug appeared after updating confluence to 6.3.1 reporting plugin 6.8.0

            I've found this issue happening on a large legacy instance at version 5.7.4. This instance is still being tuned but in the past was performing very slowly. I find directories named <attachmentid>_moved_out_of_the_way when grepping for the appropriate attachment ID's, indicated by this KB article as a page tree move timing out.

            I'll be investigating this python script and I hope it applies to my situation.

            Steven Behnke added a comment - I've found this issue happening on a large legacy instance at version 5.7.4. This instance is still being tuned but in the past was performing very slowly. I find directories named <attachmentid>_moved_out_of_the_way when grepping for the appropriate attachment ID's, indicated by this KB article as a page tree move timing out. I'll be investigating this python script and I hope it applies to my situation.

            mark.berry

            We resolved the other issue because we fixed a few bugs around this and no longer have evidence that there is an outstanding bug here.

            If you are experiencing this issue, please let us know. Also you can use the script outlined in CONF-39975 to resolve the attachments.

            jonah (Inactive) added a comment - mark.berry We resolved the other issue because we fixed a few bugs around this and no longer have evidence that there is an outstanding bug here. If you are experiencing this issue, please let us know. Also you can use the script outlined in CONF-39975 to resolve the attachments.

            Mark Berry added a comment -

            I see that this new issue duplicates CONF-36497 which has been 'resolved' in favour of this issue.

            CONF-36497 had 44 votes; this new issue has just 2 votes, so when issues are 'resolved' in favour of a new or duplicate issue, clearly the votes are not carried across. Does this mean that the priority for fixing a bug is reduced whenever this happens?

            Mark Berry added a comment - I see that this new issue duplicates CONF-36497 which has been 'resolved' in favour of this issue. CONF-36497 had 44 votes; this new issue has just 2 votes, so when issues are 'resolved' in favour of a new or duplicate issue, clearly the votes are not carried across. Does this mean that the priority for fixing a bug is reduced whenever this happens?

              Unassigned Unassigned
              jturnquist jonah (Inactive)
              Affected customers:
              33 This affects my team
              Watchers:
              37 Start watching this issue

                Created:
                Updated: