I’m trying to configure HTTPS certificates for my local development environment using Nginx Proxy Manager. However, I’m running into a frustrating issue where all my local services keep redirecting me back to my server’s authentication page instead of showing the actual service.
I suspect the problem might be related to my VPN setup that’s interfering with the DNS resolution. I’ve attempted to disable the VPN’s DNS settings but haven’t been successful in resolving the redirect issue.
Has anyone encountered similar problems when setting up local HTTPS domains? What configuration changes should I make to prevent these unwanted redirects to the login interface?
This sounds like a classic issue with your authentication middleware intercepting requests before they reach your intended services. I encountered something similar when my reverse proxy was configured with default authentication rules that applied globally rather than selectively. Check your NPM configuration to ensure you haven’t enabled ‘Force SSL’ or authentication requirements at the proxy host level when you only want them for specific services. Also verify that your local services are actually running and accessible directly via their internal ports before adding the proxy layer. Another common culprit is having your router or firewall redirecting all HTTPS traffic through a captive portal or authentication gateway. Try accessing your services using their internal IP addresses first to rule out DNS-related routing issues. If that works, then focus on your NPM host configuration rather than the VPN settings.
had this exact problem last month! turns out my npm was using the wrong upstream server address - was pointing to the auth service instead of my actual app. double check your proxy host settings and make sure the forward hostname/ip is correct for each service, not just copy-pasted from another entry.