aleksey.filippov, roland.vermeulen, are you able to please troubleshoot this issue with our support team at https://support.atlassian.com/contact? As we have been unable to reproduce this issue as described, as indicated by the comments above from our team, it's possible that the the problem with the export is related to another part of the page, rather than the images themselves. In order to properly replicate the issue, we may need some samples of Confluence pages that are having the problem.

So this issue seems marked as resolved and lowered in severity.

Could you tell or share what the solution is to have PDF export working when images cannot be retrieved.

My customer is running 6.1.4 and still experiencing this issue when export Confluence pages with Jira macro's inside.

Addition to suman.karamched comment:

2018-04-10 03:31:20,104 WARN [http-nio-8443-exec-99] [confluence.extra.flyingpdf.ConfluenceExportUserAgent] getImageResource Could not retrieve image resource https://hidden_URL/help/Content/Resources/Images/newmessag.png during Confluence export
 -- url: /spaces/flyingpdf/pdfpageexport.action | page: 21206447 | traceId: af4b80926c5ae3e1 | userName: first_name.last_name | referer: https://hidden_URL/display/ROS/TC%231%3A+SMC.+Receiving+Messages | action: pdfpageexport

 It is 6.7.0 version.

Why can't we export without some inaccessible resources?

Hello,

The replication steps are really simple.

We have 

• Powered by Atlassian Confluence 6.7.0

I go to a Confluence page, and click the ... and select Export to PDF from the menu.

I wait and wait and wait and wait some more.  I eventually see

Proxy Error

The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /spaces/flyingpdf/pdfpageexport.action.

Reason: Error reading from remote server

I can perform "Export to Word" on the same Confluence page, and was able to export the document.

With any modern version, the PDF generation will not fail and will complete successfully with a warning:

getImageResource Could not retrieve image resource http://www.site.com/image.gif during Confluence export

PDF will contain an empty line instead of the broken image.
This behaviour seems to be acceptable for this scenario.

Hi all, I have tested this issue on 6.5, 6.1 and 6.0. However it could not be replicated. Given that the warning message is printed, I believe the unaccessible image url is managed properly. So the exporting problem is likely to be caused by something else. I may close this ticket at this point. Feel free to reopen it or create a new ticket if you have further input. 

Dear aleksey.filippov,

Many thanks for your comment.

We intend to get this issue resolved, however, we are not able to reproduce it on 6.3.4 or 6.5.2. As you have mentioned that the problem still exists on 6.5.2, could you please shed light on the reproduce steps? Much appreciated if you could attach the storage format (https://confluence.atlassian.com/doc/confluence-storage-format-790796544.html) for the test page as well.

As of the warning message, it indicates that Confluence was not able to retrieve the image using the link, which is fair when the image is missing.

Regards,

Feng Xu

Confluence Server 

Same problem on 6.5.2

2017-10-18 04:24:24,800 WARN [http-nio-8090-exec-7] [confluence.extra.flyingpdf.ConfluenceExportUserAgent] getImageResource Could not retrieve image resource https://somehiddenURL.com/help/Content/Resources/Images/secure%20messageicon_22x18.png during Confluence export

I don't understand - problem is more then 3 years old and still not resolved. Is it so big problem? It is not very cheap product to delay such problems solving for a long time.

We have the same issue in Confluence 6.1.2

Our confluence is running behind firewall, which does not allow it to access an image from the web.

Users can see the image perfectly well (because the browser can load the image from the web), but when they try to export the page to PDF, it runs forever and does not produce anything.

In my opinion, the proper behavior is to produce the PDF without images and show a warning message, informing the user that PDF generation was not fully successful, because images from external sources could not be loaded. The warning should include which images were not loaded and from which addresses. Thus the user may decide to replace the web images with local ones or contact their administrator to resolve the connection problem (up to the user to decide). 

@Atlassian You can safely increase the Support Reference count to 23, as I was just about to open case for this problem.

Hit by this issue in Confluence 5.10.6