Added DuckDNS and on config files made changes …
“true” for accept Let’s Encrypt license
email
“mydomain.duckdns.org”
Made portforwarders … though now understand may no longer be needed.
80…80
8123…8123
443…443 and later 443…8123
Started DuckDNS and verified the log shows all started as normal. Verified the 2 cert files are in the SSL folder.
Uncommented the “http” in configuration.yaml and placed various iterations of base URL …
mydomaindotduck
https://mydomaindotduck
It seems that regardless of what I do when I type in https-colonslashslash-mydomaindotduckdnsdotorg it doesn’t work.
Locally with an IP or duckdns name, with or without “:8123”, I still am unable to use https://. However, regular http (unencrypted) url works great. DuckDNS works locally, too, but without https.
Externally, same thing. I basically am getting unencrypted traffic. At my login page, it shows that I am being connected to “httpcolonslashslash-mydomain-or-myIP-colon-8123”.
I tried deleting some port-forwards and changing 443 to 8123 and tried externally with :8123 or without …same result.
I am not getting encrypted traffic. Have now deleted my port forwards and duckdns until I figure things out. Works great locally without encryption.
Am I missing something or did something break along the way?