Hi @othman3265414,
When using a CDN, you need to set up a Cross Origin Resource Sharing configuration to permit the browser to access the documents from a different source. It looks like you might be using GoDaddy for your host—the cause of the issue is that GoDaddy will try to redirect the document loading through secureservercdn.net which will result in a “No Access-Control-Allow-Origin header” error (you should be able to see this in the browser’s Developer Tools > Console tab). The first step would be to set up a CORS rule for the CDN. The following documentation has the required information needed to permit access for the document to be loaded from a CDN: https://wp-pdf.com/kb/hosting-pdfs-on-other-services-such-as-amazon-s3/.
Once you have the CORS set up correctly, this should resolve the Failed to Fetch error depending on how the CDN for your account is set up. If not, you should next have GoDaddy support create a Post Processing rule to stop anything going to .pdf to remain with the domain and URI path.
Here is and example of the rule that has been added successfully on a WPEngine site (the same situation as you are seeing—I don’t have an example of GoDaddy’s rule unfortunately) to rectify the issue:
#https?://sitenamecdn-wpengine\.netdna-ssl\.com/(.*)\.pdf# => https://sitename.com/$1.pdf<https://sitename.com/$1.pdf>;;
This procedure has worked successfully for other users hosting with CDNs.
If you have any other questions, please feel free to send an email to contact@wp-pdf.com as we may not see messages posted here to respond in a timely fashion.
Emma
