• 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.

Question nginx reverse proxy and password protected directory

CoffeeLover

New Pleskian
Server operating system version
Ubuntu 22.04
Plesk version and microupdate number
18.0.64 Update #1
Hey everyone,

I need some help with the following setup:
  • a docker container running my API
  • a website which is public
  • a 2nd website which is protected with password (via Protected Directories)
On the public website I set up following additional rule for nginx:

Code:
location /api/ {
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_pass http://172.17.0.2:8080;
}

This redirects all my calls to "api" to my docker container. This is working perfectly fine. But the same setup on my password protected website is not working. As soon as I turn on the password protection I get 404 or 403 for my API calls.

Can anyone direct me in the right direction how to setup something like that (without having to write my own auth)?
 
Ok I guess I found the solution for my problem. Posting it here in case someone else will have similar problems.

I needed ^~ right before /api/. But that is not enough. Then the API is not password protected anymore. The protection is back with the lines auth_basic and auth_basic_user_file.

Code:
location ^~ /api/ {
    auth_basic "Root";
    auth_basic_user_file "/var/www/vhosts/system/<domain>/pd/d..httpdocs";

    proxy_hide_header upgrade;
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_pass http://172.17.0.2:8080/;
}
 
Back
Top