Login issues via dyndns while local adresses are working

Configuration
1

When logging in to my home assistant instance via a duckdns url (https://myurl.duckdns.org:8123), it works for 8 out of 10 logins. The other 2 times it stuck to the loading screen (see screenshot) - Some times up to 5 minutes.
image
In the same moment I am able to login to home assistant via http://homeassistant.loclal:8123 or http://192.168.178.XXX.

Since I am able to connect to the dyndns and log lucks fine, I believe the duckdns addon within home assistant works correctly.
Since local addresses work properly and I am able to connect to the dyndns, I think the network config is set up correct too. But feel free to make yourself a mind.

http:
base_url: https://XXX.duckdns.org
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem
ip_ban_enabled: true
login_attempts_threshold: 5

Any ideas what casuses this strange connection issue?

2

Next time it gets stuck - try CTRL + SHIFT + R to force a full refresh of the browser. Typically I find that the issue happens to me, when Home Assistant has been updated and there is a new frontend waiting to be installed in the browser cache.

3

Thanks Andrew, that fix would be amazing. Sadly today its running into that issue more than usual so I am already able to tell you its not working. :frowning_face:

4

As a quick test to see if it is a browser issue - which is often the case - try opening a private / incognito window and see if it will let you log in with that.

5

@all the issue still occures and is defenitly not up to browser (tried different once), cookies (deleted and went for incognito), nor the app.
I assume that the forwarding to the dyndns is not working propperly. Any idea how to identify if there is an issue with a) the configuration of the duckdns add-on or b) the forwarding on my fritzbox beforehand?

Or c) any other ideas at all? :smiley: