• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

Search results

  1. K

    Issue Plesk NodeJS Server: CORS error upon every request

    Hello Ok, so we had temporary domain for node api and tried adding domain name we own. we added that on august 7 and that helped but today we're again seeing CORS error. Can someone help figure out that weird behaviour?
  2. K

    Issue Plesk NodeJS Server: CORS error upon every request

    Hello There's a node api and two NEXT js apps which make requests to it node api uses express cors middleware like so app.use(cors()); All of a sudden we started seeing cors errors in the console on each request however no changes were neither in code nor in plesk settings recently.
  3. K

    Issue Plesk NodeJS Server: CORS error upon every request

    Did someone experience same issue? I also created fresh instance of node api and cors error appeared immediately. setting headers like it described here https://support.plesk.com/hc/en-us/articles/12377597400087 didn't help.
  4. K

    Issue Plesk NodeJS Server: CORS error upon every request

    Hi I have node api and two next app connected to it. A couple of days ago customers claimed they can't login and turned out there's a cors error in the console. Access to XMLHttpRequest at '{node api}' from origin '{next app}' has been blocked by CORS policy: No 'Access-Control-Allow-Origin'...
Back
Top