-
|
Hello, I've created multiple proxy hosts, and all of them work fine, but I get 502 Bad Gatewaywhen when I try to set up a proxy host for the npm page. I've used my internal network container's address mapped to port 81.
Here are my versions: Also, I'm not using any custom DB. This leads me to think there may be extra steps to stick a subdomain to this container. Has anyone bumped into this issue before? Best regards! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Solved: The issue was the redirect scheme, by default npm uses HTTP on port 81, and I was telling nginx to redirect it to https://container:81
Fixed it by changing the scheme from https to HTTP.
|
Beta Was this translation helpful? Give feedback.
Solved: The issue was the redirect scheme, by default npm uses HTTP on port 81, and I was telling nginx to redirect it to https://container:81
Fixed it by changing the scheme from https to HTTP.