No connection with Homeassistant app in the home network

Mobile Apps
1

Hello,

I currently have the following problem:
I have built a network with a FritzBox 6490.
On the LAN is the RaspPi with HA and a Windows PC.
I can reach the RaspPi HA from the PC.
It works https://192.xxx.xxx.xx:8123 and also
https://homeassistant.local:8123
WLAN network is an Android tablet and also a smartphone with Android.
On the tablet I have installed fullyKiosk and reach HA via the URL https://192.xxx.xxx.xxx:8123, no problem also via the browser Google Chrome I can reach HA with this URL.
With the smartphone I can also reach via the google browser via the
URL https://192.xxx.xxx.xxx:8123 to reach HA.
Smartphone and tablet are in the WLAN home network.

Now I have the following problem:
From the home network I can no longer reach HA with the Homeassistant app!
Only if I am no longer connected to the smartphone in the WLAN I can reach HA via https://xxx.duckdns.org.
I have also uninstalled and reinstalled the APP.

Does anyone here know why this is so?

Thanks a lot
Juergen

2
3

Hello,
Thanks for the info.

I found a hint and currently solved it like this:

# configuration.yaml entry  
#http:
# ssl_certificate: /ssl/fullchain.pem
# ssl_key: /ssl/privkey.pem
# ip_ban_enabled: true
# login_attempts_threshold: 5

But that can’t be the solution?

Greeting Juergen

4

What were these before?

5

So:

# configuration.yaml entry  
http:
 ssl_certificate: /ssl/fullchain.pem
 ssl_key: /ssl/privkey.pem
 ip_ban_enabled: true
 login_attempts_threshold: 5

:slightly_smiling_face:

6

What you did put everything back to defaults

Ip_ban_enabled default is false

Likely your internal ip was banned and caused your issues

EDIT
That or your local ip not resolving for https which might have been actual problem know that I look

7

ohh, thank you very much for this tip!

i will test that…

Juergen

8

Hello,
unfortunately this change did not bring success either.

What do you mean by that? What can I do?

“That or your local IP is not resolving for https, which could be the real problem, I know.”

By the way, I now have another problem with my
Change in Configuration.yaml
I can’t reach any ADD-ONs anymore! I get
the message: 401: Unauthorized

So there must be another way

9

In another post I found the following:

http:
base_url: xxxx.duckdns.org
server_port: 443
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem

that helped.
Now I can access my Homeassistant inside and outside WLAN.

But I don’t know exactly why it is like this…

Greetings Jürgen

10

base_url is deprecated in latest versions

not sure of your problem cause but certainly seems related to http section.

I was thinking HA was providing the ssl cert for your duckdns when you connect internal but honestly I not sure if that would create issue or just give browser warning.

11

Same Problem Here…any solutions?Seems that other Users have had the same problems in different ways.