It's this why remote connection won't work?

Posted Jan 14, 2019, 5:49 AM UTC

Posted Jan 14, 2019, 5:49 AM UTC
I'm having real trouble getting Duckdns working. Just checked which ports my ISP is blocking and got the attached list. Will this be the problem?
That depends on what TCP port HA is using. Default is 8123. If you haven't changed that then the blocked ports you listed shouldn't be an issue.
Note, if you want to use LetsEncrypt, that does use port 80 as part of generating the certificate (though not for web access to the server itself) so you won't be able to do that with port 80 blocked.
I'm using Nginx so shouldn't be an issue?
Depends. If you wanna set up encryption (https) your gonna run into problems.
Oh right. So you recommend I use let's encrypt?
There is an option to use DNS with lets encrypt that doesn’t require inbound http to work (uses outbound DNS instead). You should be able to set it up like that.
DuckDNS can also use other ports, like 443
Are you with AussieBB? I just emailed them and they unblocked all ports on my service.
Just out of interest, do you have any problems upgrade your HA install when on Aussie Broadband?
I thought that image looked familiar. Yeah, OP is with AussieBB.
I ran into the same issue as you OP when I set up external access to HA over a year ago. I just called them, told them I wanted the ports unblocked and that's it.
EDIT:
Not OP but I don't remember ever having any issues.
EDIT (again):
Oh damn it's past 3 AM here. Gotta get some sleep!
I am with ABB and I raised a ticket. Thanks for your help.
Not issues upgrading for me on HASSOS.