March 10, 20233 yr I currently have both a DuckDNS (<mysubdomain>.duckdns.org) and Google Domains (ddns.<mydomain>.dev) DDNS services set up, and I've verified both point to my IP address. The Unraid VPN via the DuckDNS domain has been set up for a while and works fine, but I can't get the VPN to connect when using my Google Domains domain as the endpoint. The top-level domain for my Google DDNS is .dev, which enforces HSTS, so I suspect this may be the cause, though I really have no idea if Wireguard cares about this. Since HSTS requires SSL, I have tried a few things to associate a certificate with ddns.<mydomain>.dev: Created a Let's Encrypt certificate with my Asus router, which is handling DDNS updates for Google DDNS. This doesn't have any effect though because nothing redirects ddns.<mydomain>.dev to my router, nor would I want it to. Created a Let's Encrypt certificate with Nginx Proxy Manager with a 404 redirect. With this configured, ddns.<mydomain>.dev indeed redirects to a 404 page with the appropriate certificate. Used that same certificate with a proxy host for http://<myserver>:51821. This configuration yields a 502 bad gateway error for ddns.<mydomain>.dev. None of the above configurations allowed my clients to connect to Unraid's VPN using ddns.<mydomain>.dev. Does anyone know about Wireguard's compatibility with domains that enforce HSTS? Or more specifically, Unraid's implementation of Wireguard?
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.