Issue with the topic: Suddenly, I am unable to access the Main UI on 5G.
Today, Openhab 5.1.1 became inaccessible from 5G, while it works perfectly via Wi-Fi, noting nothing changed in the sense that no configuration was touched.
The message initially is that while the cloud is accessible, the instance itself is offline. I got home and found that it is working fine on wifi.
I rebooted the Docker container
I completely uninstalled and reinstalled OpenHAB. That did not fix the issue. The message this time, “An error occurred while loading Main UI” click on “Try Again” for a fraction of a second, shows “Unauthorized”
I checked my partner’s phone, and it works like a charm on both wifi and 5G.
I put my credentials on her phone, and they worked.
I put her credentials on my phone, same error “Unauthorized”
I consulted both Claude and Gemini, and they concluded that Webview is the culprit.
I have a Samsung S25 Ultra. On it, I found Android System Webview and uninstalled updates. The result was the same: “An error occurred while loading Main UI,” and refreshing shows “Unauthorized”, pointing to it might not be a webview.
I am at a loss for the root cause.
I am behind an ISP that has GNAT, so VPN solutions won’t work for me.
I think the only way would be to ping digitaldan who seems to look after the cloud connectivity? Or tag this post to refeclect that it relates to cloudj connector issues?
I don’t think it’s a problem with the cloud connectivity, because Sitemaps via 5G are ok.
And the Android app version is very new. May be was the problem there.
Agreed. I have downgraded to 3.19.8 and it is working now.
I had been running 3.20.5 fir a few days with no problem. So not sure why it chose today to break?
For anyone who is experiencing this problem, if you can go into the application settings (e.g. where you set the urls for local and remote settings. Further down in the list of options you’ll find some that refer to logs. Enable debug logging if it’s not already enabled and gather some logs during a failed connection. Those might hint at a work around and definitly will be needed in the issue that needs to be filed on the android app.