• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Question How does location and proxy_pass work?

MartinH

New Pleskian
Hi,

for basic testing I have set up a simple node server listening on port 5100 and a nginx directive
Code:
location /api/ {
    proxy_pass http://127.0.0.1:5100/api/;
}

I am pretty new at this, but doesn't this directive mean, that a request like
Code:
https://myserver.com/api/xxxx
will be redirected to
Code:
http://127.0.0.1:5100/api/xxxx
I get an empty 200 response (was expecting a simple string).

A request to
Code:
location /api/ {
    proxy_pass http://127.0.0.1:5100/;
}
is working fine, but is not routed to /api/xxxx like I want it to.

What am I doing wrong? Thanks
 
Back
Top