• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

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