Viewing 3 replies - 1 through 3 (of 3 total)
  • Thanks for posting. The PDF is currently showing for me, but it’s possible it depends on browser etc.

    If you still have an issue, please could you send an email to our support team on contact@wp-pdf.com, including these links again and how to reproduce the issue (browser versions on which there is a problem – screenshots also helpful).

    I will probably not pick up any replies posted here, so please do email and we will be happy to help!

    Regards,

    Dan

    Bink

    (@bink19th)

    @sock2me, I see this issue was resolved. I too am now having this issue.

    Are you able to provide the solution?

    Bink

    (@bink19th)

    For others coming here for the solution, it’s actually detailed in the PDF Embedder plugin knowledgebase here:

    https://wp-pdf.com/kb/

    You will usually see this error in your browser because your PDF does not sit on the same domain as the current page on your site.

    For example, if you access the page http://www.mycompany.com/ and see the error message:
    Failed to Fetch while retrieving PDF “http://mycompany.com/wp-content/uploads/mydoc.pdf”
    this is because the shortcode for the embedded document references the URL on mycompany.com whereas the page is sitting on http://www.mycompany.com.

    The “www” is important – it references a different domain to the PDF’s URL that does not contain “www”.

    For security reasons, browsers are not allowed to load the PDF from a different domain. This error will also occur if you try to embed a PDF from another 3rd party site.

    You will need to ensure all your [pdf-embedder] shortcodes refer to the PDF’s URL in the new preferred manner.

    Sometimes, the problem might be that WordPress is configured to upload PDFs to media.mycompany.com, or something similar, perhaps due to a content-delivery plugin that is attempting to speed up your site. It may still be possible to load PDFs hosted on a different domain, at least if you have the ability to set up the configuration of that domain – see Hosting PDFs on other services such as Amazon S3.

    It is also possible that a PDF URL is being prevented from loading by a browser Ad Blocker. In the browser console, this shows up as an error net::ERR_BLOCKED_BY_CLIENT. To fix this, be sure that the PDF file name does not contain any words such as advertisement, advert, ad, click, doubleclick which are trigger words for Ad Blockers.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Failed to fetch’ is closed to new replies.