I have a gl-inet router on which I have an nginx config to send traffic to Nginx Proxy Manager and DDNS with cloudflare.
I’m trying to get some kind of local dns set up so that if I’m on the local network, traffic stays within the network. The problem that I’m running in to is SSL certificates. NPM is handling those and I thought that what I could do is go into the AdGuard Home config and add a dns rewrite to point to the router and traffic would flow as it normally does.
This DOES work, technically. traceroute shows only one hop for any of my subdomains, ie files.mydomain.com.
But I cannot actually get access in a browser because the ssl certificates are not set up.
It seems like options are: manually copy certificates from the server to the router (not ideal), or don’t do it at all. I notice that if I go to the service by ip address, it’ll change the address to the domain name. Eg going to 192.168.8.111:30027 -> files.mydomain.com.
This isn’t a HUGE deal, but it’s not preferable. How have you all solved this?
CompactFlax@discuss.tchncs.de 3 weeks ago
If you are establishing a TLS connection to a server, the server will need a certificate. It sounds like you’re trying to have two instances of a reverse proxy - one on the server, and one on the router. It may be my ignorance of the particulars, but my immediate thought is that you should select one point in the network to do reverse proxying.
RagingHungryPanda@lemm.ee 3 weeks ago
I think you might be right on that. I was originally not wanting to do any port forwarding on the router, but I may have to
CompactFlax@discuss.tchncs.de 3 weeks ago
It’s possible but it’s an extra pain in the butt.
Internally, have you tried pointing the DNS directly to the ngnix server, not the router? There’s no reason to have that extra hop (I don’t think).