I’m having a problem with my Remote 3: the Web Configurator keeps becoming unreachable. This happens for reasons I can’t quite figure out.
The Remote and the Dock have static IP addresses and are both on the same 2.4 GHz network. I connect to the Remote using its local IP address. Most of the time the connection works, but every now and then the browser reports a ‘Connection Timeout’.
Restarting the Remote doesn’t help. I can also just wait for a while and suddenly the Web Configurator is accessible again.
Has anyone else experienced this, and better still, does anyone have a solution?
Is your remote awake when you can’t reach the configurator? You can configure the sleep timeout in the engery saving settings. When doing longer configuration it’s best to put the remote in the Dock so it doesn’t enter sleep mode.
Also check if the Wifi connection has dropped when this happens.
Can you ping the remote ip when this happpens? Also check that you are using these recomed WiFi settings on your router:
Protected Management Frames (PMF) switched off or optional
WPA2-Personal (AES) or WPA2/WPA3-Personal (transition mode)
Group key rekey interval (GTK rekey): off, or as long as possible (for example 24 hours). Every renewal during standby wakes a Remote Two, and can occasionally drop a sleeping Remote 3 until it is picked up
Band steering: off
Minimum RSSI: off
Fast roaming: off
BSS transition: off
If you’re located in the EU there’s a new beta firmare 2.12.0 that you can try if you have beta update enabled. This includes a new WiFi driver with stability fixes that may cause this. The firmware should be available worldwide today or tomorrow.
in the meantime I found out some strange things. The problem occurs only if I try to connect from my pc with a browser. Even if the remote seems not to be reachable over my pc I can access the web configurater with my phone and tablet. Since the latest firmware beta update of the remote it’s completly inpossible to reach web configurator from pc (in the beginning I wrote that the connection is possible from time to time).
I can’t ping the remote but it’s shown as connected device in Unifi. PMF is deactivated, I use WPA2, GTK is off, Band steering is off, Minimum RSSI I dind’t find, fast roaming and BSS is off.
But I don’t understand, why the remote is reachable over my mobile devices while they are in the same WiFi network as my pc and are not reachable over the pc. Actually I would say that this is not a remote issue. On the other hand the latest beta frimware update had an impact of this behaviour so it seems that there is a context…
Since phones/tablets reach it and two PCs don’t, I’d compare the PC’s network path with the phone’s rather than only the Remote. Check that the PC is on the same SSID/VLAN/subnet and gateway, and look for a VPN, proxy, or firewall/security tool blocking local-subnet traffic. Also try ping and tracert to the Remote’s IP from the PC, and test the PC over Wi-Fi if it’s wired. If possible, boot a live USB or temporarily pause the firewall to separate OS/security blocking from router isolation.