No internal access after DuckDNS/LetsEncrypt

Hi there,

I’ve successfully installed DuckDNS and LetsEncrypt. It is working from the external name of just fine.

My Internal and External URLs are set as follows on the General page:

But now, my internal name/url doesn’t work any longer.

This happened as soon as I restarted with this added to the configuration.yaml file.

  ssl_certificate: /ssl/fullchain.pem
  ssl_key: /ssl/privkey.pem

So by adding that, I no longer have internal access? I tried the following and none of them work from my internal network:

Could someone tell me if I’m missing something in my config or if this is the way it is now that I’ve added those certificates and this is part of the lockdown to make it secure?

I have the same issue and am equally interested in this answer!

1 Like

You need to use https


Ah ok… So my internal url is now https://(internal-ip):8123. The internal name is now

Since my port forward changes 443 -> 8123, it’s just easier to use the external URL everywhere I guess. If I go to the internal URL, the certificates don’t match, which is expected.

I guess I don’t see any harm in always using the external URL so that the certificates are always happy.

If you run your own internal DNS server (like Pi-Hole) or your Internet router is providing DNS looks up for you and it has the ability to set static DNS entries in it, you can set up the same external host name internally but just have it point to the private IP.

IE => 192.168.x.x

Certs don’t care about IP’s they just care about the domain name being authenticated. That way you’re just using the same DNS name regardless if you’re internal or external to your network.