reflector connection test failed: unable to connect to serve

Neither of those URLs worked.

I stopped and started the Indigo server while the browser was trying to connect. It never did.

As I said... that port is not listening. Ever.

Here is the log:

Jul 26, 2023 at 11:03:26 AM
Error reflector connection test failed: local server unreachable
Warning reflector reconnection scheduled in 5 seconds
Error failed to create reflector connection: local server unreachable
Error check your Firewall and Network configurations and try restarting the server
Warning reflector reconnection scheduled in 15 minutes

[matt (support)]

Earlier you said:

UPDATE: It works for about 10-15 seconds after restarting the server, then gives up and I lose the connection.

What did you mean by that? I'm trying to reconcile that with the fact you said that port is never listening. And as I said before, I need to see your entire Event Log after an Indigo Server restart (after it runs for a couple of minutes).

So when I start the server and use the iOS app... (using Celluar, not WiFi) - I can see my stuff - - for just a bit... then it stops. So not sure if "never" listening on the port is accurate. Let me experiment with that.

Here are my Indigo servers settings. I am overriding some ports. But this has been this was for a few years.

This is the LOG after restarting Indigo - - showing me connecting and controlling a device for a while before it bombs out:

Web Server Indigo Touch client connected from 107.122.157.94
Sent INSTEON "Family Room Table Lamp" on to 43
Sent INSTEON "Family Room Table Lamp" on to 100
Sent INSTEON "Family Room Table Lamp" off

Jul 28, 2023 at 1:05:12 PM
Error reflector connection test failed: local server unreachable
Warning reflector reconnection scheduled in 5 seconds
Error failed to create reflector connection: local server unreachable
Error check your Firewall and Network configurations and try restarting the server
Warning reflector reconnection scheduled in 15 minutes

[matt (support)]

First thing to note is you have overridden the default port for Indigo's internal Web server to 8080, so that is what you need to be checking for a listening port instead of 8176. Likewise, these are the URLs you should be refreshing (every couple of seconds) on after an Indigo Server restart:

http://localhost:8080/prismstatus
http://127.0.0.1:8080/prismstatus

I'm fairly confident that if you refresh those URLs both every few seconds after an Indigo Server restart that the second one (127.0.0.1) will work for a few seconds and the first one (localhost) will never work. This tells us that something is misconfigured or corrupt on your macOS and not resolving localhost to the Mac as it should. Normally this is because the /etc/hosts file has been modified or corrupted. If that isn't the case in your scenario, and it isn't a firewall blocking it (like Little Snitch), then I'm not sure what is wrong.

And have you tried completely turning off your firewall (macOS and/or third party)?

And as mentioned in the other thread, do you have multiple network connections (WiFi + ethernet) enabled? If so, try disabling one of them.

That was it.

My /etc/host file had this:

Code: Select all

##
# Host Database
#
# localhost is used to configure the loopback interface
# when the system is booting.  Do not change this entry.
##
127.0.0.1   localhost
255.255.255.255   broadcasthost
::1                  localhost


At first glance - it looked fine to me as the 127 was in there.

But something must have tried to add an IP6 localhost reference.

I deleted that last line... and it's all good now. Not sure what (other than MacOS update) could have added that.

Thanks. Working fine now!

And just to summarize , I had 1 network connection (Just Ethernet, WiFi is off), MacOS firewall on or off, didn't matter. No other software that blocks anything.,

I did do the test with port 8080 and you were correct... 127 said "connected" and localhost did not. Ok... so that's what put me back to the /etc/hosts.

Good call, thanks again !!!

[matt (support)]

My hosts file has the ::1 line as well (I think it is in hosts by default). The Indigo Web server binds to localhost, so if your Mac is using ipv6 I'd expect it to bind to ::1 instead of 127.0.0.1, but I don't believe we've done testing of that. It is possible that it (or Python) is actually binding to 127.0.0.1 in all cases (despite us using localhost when setting up the Web server) and if your Mac is preferring ipv6 then it fails since it then resolves to ::1.