• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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