Forwarded to devs Error message for additional nginx directives are causing confusion when proxy mode is enabled

[Kaspar]

Username:

TITLE

Error message for additional nginx directives are causing confusion when proxy mode is enabled

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Plesk: any version
Os: any OS

PROBLEM DESCRIPTION

Adding additional nginx directives containing a location / { } block causes an nginx error when Proxy Mode is enabled (which it is by default). This is expected behavior from a technical point of view. But the error message shown doesn't fully indicate what's causing the error and how to possibly solve it. It's not a bug per see, but it looks like quite a few users are struggling with this. As it's not clear to users that "Proxy Mode" also uses a location / { } block that's preventing them from adding their own root location block.

Some threads from user on this forum with users struggling with this issue:

Resolved - Failure: Getting Flask (gunicorn) to work from Plesk web interface

I am not able to override ProxyPass to nginx from Gunicorn Flask application on port 5000. These are the errors I get, trying the stuff I searched for on this forum.

talk.plesk.com

Resolved - Nginx url rewriting not working

I am trying to get the following rule to work for a domain: try_files $uri $uri/ /index.php$is_args$query_string; When i add that rule in Additional nginx directives only the homepage works. The other pages gives me Plesk 404. But when I add the same code in...

talk.plesk.com

Question - How to overwrite existing nginxs configurations?

Hi, I'm trying to setup my private docker registry with the public port 5000 on my server running Plesk. In the internet I found several tutorials. They all need to extend the nginx configuration line this: server { listen 80; server_name SERVER_URL; access_log...

talk.plesk.com

Resolved - Websockets not working in Docker

Hey Plesk team, could you please create a tutorial about setting up a docker container with an app that uses WebSocket? It looks like a lot of people are requesting this. I am always reached by the community because nobody can. Here is another ticket just about this. Can you please install the...

talk.plesk.com

Resolved - CORS stop to working using HTTP 2 Plesk Plesk Obsidian Version 18.0.52

Username: TITLE CORS stop to working using HTTP 2 Plesk Plesk Obsidian Version 18.0.52 PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Plesk Obsidian Version 18.0.52 Ubuntu 22.04.2 LTS PROBLEM DESCRIPTION After updating Plesk Obsidian Version 18.0.51 to Plesk Obsidian Version...

talk.plesk.com

Perhaps the error message can be improved on to also suggest a solution (i.e: disable proxy mode or use another location syntax).

STEPS TO REPRODUCE

1. Add domain in Plesk
2. Add some additional nginx directives containing a within a location / { } block
3. See error

ACTUAL RESULT

Error message shown is technically correct, but not helpful in indicating what is causing the actual problem and offering a possible solution to users.

EXPECTED RESULT

A better, more clear, error indicating the issue and offering a solution.

ANY ADDITIONAL INFORMATION

(DID NOT ANSWER QUESTION)

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug

 

[Sebahat.hadzhi]

Thank you for the report, @Kaspar . I forwarded it to our team for further review and processing. I will follow-up with more details as soon as possible.