• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue CORS Header does not apply to site

hello @TheDanniCraft ,

by default Plesk uses nginx as reverse proxy, so additional directives for apache may be not enough
and you need appropriate directives for nginx too (see the same article)
 
I added
Code: 
location ~* \.(eot|ttf|woff|woff2)$ {
    add_header Access-Control-Allow-Origin "https://api.thedannicraft.de";
}
to nginnx statements but it doesn't worl
 
@TheDanniCraft , I feel that you should add just custom directive, without location, like on screenshot below
1650506410595.png

on my test machine it looks like below:
$ curl -v heavy02.a10-52-61-134.qa.plesk.com
* Trying 10.52.61.134:80...
* Connected to heavy02.a10-52-61-134.qa.plesk.com (10.52.61.134) port 80 (#0)
> GET / HTTP/1.1
> Host: heavy02.a10-52-61-134.qa.plesk.com
> User-Agent: curl/7.74.0
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Server: nginx
< Date: Thu, 21 Apr 2022 02:01:18 GMT
< Content-Type: text/html
< Content-Length: 464
< Connection: keep-alive
< X-Accel-Version: 0.01
< Last-Modified: Fri, 15 Apr 2022 04:12:56 GMT
< ETag: "1d0-5dca9a011cd90"
< Accept-Ranges: bytes
< Access-Control-Allow-Origin: http://api.thedannicraft.de
< X-Powered-By: PleskLin
< Access-Control-Allow-Origin: http://api.thedannicraft.de
<
<!doctype html>
<html lang="en">
<head>
Click to expand...
 
did you set appropriate nginx additional directives at the bottom of the page:
1650513990524.png
?
 
you should use https://api.thedannicraft.de for the nginx additional directives,
because you have 301 redirect to https turned ON.

also, please check that you're using correct URL for API calls (https://api.thedannicraft.de)
the problem may be caused by setting preferred site setting:

Question - Missing Authorization Headers in FPM application served by Nginx

Hi All, I've been struggling with this issue for the last two days and I've concluded that this a server configuration issue. I have a Laravel application running on my server which serves a simple API. I'm trying to use a personal access token in postman to access the endpoint passing it as a...
talk.plesk.com talk.plesk.com

another one reason why web server configuration has not been yet applied may be that Plesk configured to reload web servers not right after some config was changed, but once per some time

manual nginx and apache restart should solve this.


if it does not help, well.. probably it would be better to reach technical support,
so our engineers will be able to investigate this problem more deeper.
 
I have that same problem. I tried restarting it didn't work.
Nik G said:
you should use https://api.thedannicraft.de for the nginx additional directives,
because you have 301 redirect to https turned ON.

also, please check that you're using correct URL for API calls (https://api.thedannicraft.de)
the problem may be caused by setting preferred site setting:

Question - Missing Authorization Headers in FPM application served by Nginx

Hi All, I've been struggling with this issue for the last two days and I've concluded that this a server configuration issue. I have a Laravel application running on my server which serves a simple API. I'm trying to use a personal access token in postman to access the endpoint passing it as a...
talk.plesk.com talk.plesk.com

another one reason why web server configuration has not been yet applied may be that Plesk configured to reload web servers not right after some config was changed, but once per some time

manual nginx and apache restart should solve this.


if it does not help, well.. probably it would be better to reach technical support,
so our engineers will be able to investigate this problem more deeper.
Click to expand...
I have that same problem. I tried restarting it didn't work.
 
You must log in or register to reply here.

Similar threads

Y
Question Issue Implementing Dynamic CORS Headers in Plesk’s Additional NGINX Directives
Replies
1
Views
399
yfain
Y
s-light
Question NINGX CORS for multiple sub.domains
Replies
1
Views
818
s-light
s-light
K
Resolved Request body not available using Node.js, Express on Plesk (Cors)
Replies
1
Views
3K
Kroptokin
K
K
Issue Plesk NodeJS Server: CORS error upon every request
Replies
4
Views
3K
keithchasen
K
S
Issue htaccess header missing
Replies
1
Views
1K
SKDamon
S
Back
Top