• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

Recent content by keithchasen

  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'...
See more
Back
Top