• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved nginx proxy and CORS problems

L. Hagen

Basic Pleskian
Hi,

this is my first post and I really hope that someone of you can help me, please.

Since two days I'm trying to get running CORS via a HTTPS connection. The beakcground:

  • nginx as a proxy for apache (OS is Ubuntu) on a virtual root server
  • CDN at Amazon CloudFront where the fonts are stored (there is also a working certificate running - tested with JPEGs, JS files etc.)
I also read and tried nearly everything I could find via Google, changed configurations etc. Nothing seems to work. The fonts will be loaded from the CDN but are not shown (No 'Access-Control-Allow-Origin' header is present on the requested resource.)

I would be very glad if someone of you could give me an advice how to get this CORS to be enabled.

Thank you in advance and best regards,
Lars
 
If I remember correctly, the CORS header must be sent from the source server, not from your own web server, so probably you must add the header to the data delivered from your Amazon CloudFront.
 
Hi Peter,

thank you for your hint. Well I tried now to insert this in the header, but I guess it does not work as well.

Do you have any other ideas?
 
Well, now it is working. I've made a complete "invalidate" at the CDN and removed all additional headers (before "Access-Control-Allow-Origin" and "Orign" were set). After the CDN had been enabled again it is working now... (for what reason ever) :)

Thanks for your help
 
Back
Top