I am hosting a couple of services on my server, instead of port forwarding I am a reverse proxy so I used caddy because of automated TLS, to the domain name, I have purchased a domain name let’s almanzel.eu, but I can not route that to my routers IP address, so I use DUCKDNS and let’s call it router.duckdns.org.
From the omar.eu domains I create subdomain and I change the DNS settings of example: code.omar.eu to have it’s CNAME point to router.duckdns.org, router.duckdns.org points to my router because my router supports it.
The problem is when I use any of the subdomains on omar.eu like code.omar.eu it works on my LAN only, I get the padlock in the browser but as soon as I am outside the network it does not, I suspect I am missing something, maybe the DUCKDNS does not have a certificate? I tried using CRTBOT to make certificates for the DUCKDNS domains, but that didn’t change anything
4. Error messages and/or full log output:
5. What I already tried:
Adding certificates from CERTBOT to DUCKDNS domains
From a cursory glance, your external DNS resolver, duckdns, doesn’t appear to be configured properly. Set up an A record to point your domain almanzel.eu to your public IP address and set up CNAME records for code, omar, etc. Next. make sure you forward your WAN HTTPS port to your Caddy instance.
duckdns points to my routers ip adress, there are no settings i can change there,
how ever the almanzel.eu can only point to an ipadress and i assume u want me to change it to my routersIP but that changes over time, and the cname records where do I need to point them at? The code, Omar etc, they are currently pointed at duckdns, and by Wan ports u mean porr 80, 443? They are both forwarded to the reverse proxy machine atm