• 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 CORS: "Only One Origin Allowed"-Error - where does second origin * come from?

it78croix

New Pleskian
Server operating system version
Ubuntu 22.04.2 LTS
Plesk version and microupdate number
Plesk Obsidian Web Host Edition 18.0.53 Update #2
Having a Backend NodeJS-App on api.XXX.com and a Frontend React-App on XXX.com.

On the BackendNodeJS-App and in Plesk - Domains - the Apache & nginx Settings my 'Access-Control-Allow-Origin"-Header is set to the frontend url.

But, I get the message of

Access to XMLHttpRequest at [api] from origin [Frontend] has been blocked by CORS policy: Response to preflight request doesn't pass access control check: The 'Access-Control-Allow-Origin' header contains multiple values '*, [...], but only one is allowed.

I can't find where the 'Access-Control-Allow-Origin'-Header could be set to the asterisk ('*'). Any ideas?
 
Back
Top