• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Issue plesk cors policy, either no header or multiple headers

Mrdtch

New Pleskian
Server operating system version
ubuntu
Plesk version and microupdate number
obsidian
I needed to enable cors, so i followed this guide:

I am adding the additional apache directives to the 'additional directives for HTTPS' as Header set Access-Control-Allow-Origin "Example Domain"
and Nginx proxy mode is ticked/on.

When I do this (and only this) I get the error "The 'Access-Control-Allow-Origin' header contains multiple values '*, Example Domain', but only one is allowed."

But when I delete the line from "Additional directives for HTTPS" i get the error:
has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.


When I try the opposite:
Disable proxy mode and add the directive "add_header 'Access-Control-Allow-Origin' 'Example Domain':" to the 'additional nginx directives' box (after clearing the previous directives in the Apache section).
I get the error:
has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.

I have followed the guide:

however there is no value in any of the other locations specified.

I am unsure what to do now.

I am uncertain why without a single directive there is a no header error but with just one single directive, i am getting an error. If there is a directive somewhere allowing '*' access, then where is it and why does it not work?
 
Back
Top