Cant access Home Assistant from any Apple iphone or ipad

Installation
1

I’m running HA on Virtualbox on Mac. I was recently forced to move to new SSID and IP Range. I managed to update the IP address of HA via GUI and reflashed devices to new Wifi.

I can now access via an PC or Mac by Safari, Edge or Chrome with no issues however I cant access from any iPhone or iPad ( tried several) on same local network either through browser or companion app (this times out with 1001 error) I can’t see the Host IP with FING on iphone but can see other sensors etc.

I’ve cleared web data from iPhone but am out of ideas.

Any help appreciated.

2

Are you on a flat network with the same IP range for all of your devices? If they are in the same range, do you have your apple devices on the same subnet as well?

3

yes, same IP range for all devices and Apple devices on same subnet.

4

Hi, what is the address you use to access HA?

5

192.168.5.155:8123

6

That’s exactly what you type in all your apps?
Are you using SSL?
Do you have access to your HA from outside of your LAN?

7

Yes that or Homeassistant.local:8123. I’m not using SSL and don’t have external access.

8

What do you mean by ‘sensors’?
Can you open anything else on your LAN that has a webUI with these 2 different devices?
Is everything else regarding network/internet access working fine with those same devices?
Are you using the same HA userid’s all around?

9

FING sees Printer, ESP32 boards and smart plugs etc but don’t currently have anything I can test with a webUI.
The log when attempting via iOS companion app is:

2023-09-09 13:14:03.635 [Verbose] [main] [OnboardingManualURLViewController.swift:153] connectTapped(_:) > Connect button tapped
2023-09-09 13:14:03.642 [Info] [main] [OnboardingAuth.swift:80] performPreSteps(checkPoint:authDetails:sender:) > beforeAuth
2023-09-09 13:14:03.642 [Verbose] [main] [OnboardingAuthStepConnectivity.swift:25] perform(point:) > 
2023-09-09 13:15:03.888 [Info] [main] [OnboardingAuth.swift:70] perform(checkPoint:checks:) > OnboardingAuthStepConnectivity: rejected(HomeAssistant.OnboardingAuthError(kind: HomeAssistant.OnboardingAuthError.ErrorKind.other(Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo={_kCFStreamErrorCodeKey=-2102, NSUnderlyingError=0x280d28c00 {Error Domain=kCFErrorDomainCFNetwork Code=-1001 "(null)" UserInfo={_kCFStreamErrorCodeKey=-2102, _kCFStreamErrorDomainKey=4}}, _NSURLErrorFailingURLSessionTaskErrorKey=LocalDataTask <9CE3AE16-A6C3-4F9B-9988-E6DD3D5FBAC1>.<1>, _NSURLErrorRelatedURLSessionTaskErrorKey=(
    "LocalDataTask <9CE3AE16-A6C3-4F9B-9988-E6DD3D5FBAC1>.<1>"
), NSLocalizedDescription=The request timed out., NSErrorFailingURLStringKey=http://182.168.5.155:8123/auth/authorize?response_type=code&client_id=https://home-assistant.io/iOS&redirect_uri=homeassistant://auth-callback, NSErrorFailingURLKey=http://182.168.5.155:8123/auth/authorize?response_type=code&client_id=https://home-assistant.io/iOS&redirect_uri=homeassistant://auth-callback, _kCFStreamErrorDomainKey=4}), data: nil))
10

Update: I am also unable to connect to a new HA instance on same network with any Apple mobile device ( iMac works ok)

11

So with the companion app?

12

with the companion app or web browser.

I have added an ESP32 Camera to my wifi and can see this correctly from iPhone no problem

13

If you aren’t using SSL, then try http://192.168.5.155:8123 instead of just the IP and port.

14

I’ve tried that and it doesn’t work. Funny thing is I rebooted router earlier and I was able to connect via iPhone for a few minutes via app but then it lost the connection and despite many more reboots I’ve not been able to reconnect

15

Your OP is in the ‘Installation’ category whereas your problem seems to be more related to the companion app.
Maybe change it to ’ Mobile Apps’ / ’ Home Assistant Companion for Apple

Apart from that I can’t help you. :angry:

16

Thanks but I can’t connect via browser either so unlikely to be issue specific to app

17

:crazy_face:
You’re right, I’m sorry!

18

I had the same problem and I solved it disabling the Web Browser Protection in my anti virus Avast!