• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

Plesk 12.5 Nginx port forward to Node app

DavidBWieler

New Pleskian
Trying to proxy_pass Nginx to a node app, but nothing I do works.

I've tried to add my "location / {}" to
include "/var/www/vhosts/system/example.com/conf/vhost_nginx.conf";

but it gives me an error saying that it's a duplicate.

I've also tried adding the new routing to "Additional nginx directives", but it gives me the same error.

I also tried adding, "location ^~ /$ {}"

But that does nothing as well, but I get no errors with this one.

I need to force Nginx to port forward everything on port 80 and 443, (I have a working SSL Cert that DOES work if I go directly to my node app, https://example.com:3000).

How can I get Plesk's Nginx configs to proxy_pass everything to my node app? I've also tried installing JXCore's Node Extension. I get an error, and their support people dont respond to questions.
 
You should try and use something like...

Additional nginx directives
Code:
location = / {
return 301 https://domain.tld:3000;
}

I hope that helps
Regards

Lloyd
 
Is it possible to also forward parameters?


Additional nginx directives
Code:
location = / {
return 301 https://domain.tld:3000;
}

So far this works for me, I modified your example like this:

Code:
location = / {
    return 301 http://52.55.142.120:10080/api/download;
}

So externally I use a subdomain call, like https://mysub.domain.tlg which by this directive successfully routes to a webapp, listening on port 10080

Is it possible to forward parameters? Like in such external call: https://mysub.domain.tlg?param1=this&param2=that

Example?
 
Last edited:
Back
Top