Hello,
my ISP only allows me to forward the same port. So I can forward 8123 internally to 8123 externally but I can’t forward 8123 to 443 for example. Is there a way around this issue? Can i configure Hassio to run on 443 internally too instead of 8123?
Thanks
Kind regards
Chris
If you use caddy, you only have to forward 443->443 and 80->80
So I’ll just need caddy and deinstall the duckdns addon?
Well you can do that. I use both;
I use duckdns for the dynamic dns without the ssl
And use caddy as a reverse proxy and ssl.
So i can use myduckdns.duckdns.org (without the :8123) for HA, and for example terminal.myduckdns.duckdns.org for my ssh terminal addon.
Or configurator.myduckdns.duckdns.org for the configurator addon.
How is this an ISP restriction? You generally do port forwarding on your home router.
Why not just forward 8123 to 8123?
Hassio and the duckdns addon work perfectly fine this way.
Yeah, this is done on your router and you should have full control. If you are using an ISP router, buy your own router and hand back the one your ISP provided. They shouldn’t be handling your routing anyways, you never know what they are doing if they have full control of your router.
Why not just forward 8123 to 8123?
Hassio and the duckdns addon work perfectly fine this way.
Cool that works? Thought Let’s encrypt needs 443 and 80 to get their ssl certificate.
I don’t have 80 or 443 open and have never had issues.
The DuckDNS addon uses DNS-01 authentication
Where do I change the duckdns port? Can’t find anything in the addon
The duckdns port for the Internet is set on your router. Mine works fine on 8123 to duckdns. I changed nothing.
It only appears to check (ping?) to find your current ip address.