I have on my local network port forwarding with a few different servers behind that single router. I have a first layer nginx proxy that I use to route to the second nginx which is the app’s reverse proxy.

I have on my local network port forwarding with a few different servers behind that single router. I have a first layer nginx proxy that I use to route to the second nginx which is the app’s reverse proxy.

I have on my local network port forwarding with a few different servers behind that single router. I have a first layer nginx proxy that I use to route to the second nginx which is the app’s reverse proxy.

I have on my local network port forwarding with a few different servers behind that single router. I have a first layer nginx proxy that I use to route to the second nginx which is the app’s reverse proxy.

I’m currently configuring Nginx for path-based routing, and I’ve run into an issue where logging in to my application works when accessed via a specific URL, but fails when accessed through another URL with a different base path.

I have a requirement where i proxy pass the request coming on my server ip to nodejs server which is running on the same server at port 3000 so that when i access my application using browser i don’t have to give ip:port on the browser but instead i just hit on the browser ip and then nginx proxy pass the request to nodejs which is running on port 3000

I have two configs, one for each website. They work fine when used separately. When both are enabled then going to domainB serves content from domainA (it doesn’t redirect to it though).

I have two configs, one for each website. They work fine when used separately. When both are enabled then going to domainB serves content from domainA (it doesn’t redirect to it though).

Has anyone ever needed to use the auth_request module within Nginx Proxy Manager? Can you tell me if this configuration is correct?

I have a static IP and own a local national domain.