This thread collects community reports about losing access to the WebApp after the controller IP or the Access IP setting was changed.
Status
Known answer. In the reported cases, access came back through one of the steps below. If the robot never finishes booting, see this thread about power-up problems.
Symptoms
- The browser shows "refused to connect" or "took too long to respond".
- Ping to 192.168.58.2 fails, often with 100% packet loss.
- The IP reset button seems to do nothing.
- The problem started right after someone changed the IP or swapped the WebApp and Web Recovery ports.
Recovery steps, in order
- Wait until the controller has fully started and the cobot end status light is solid green. The IP reset only works after that.
- Press and hold the IP reset button on the button box for at least 15 seconds, until the cobot end light blinks. Reports suggest this may not work on old software versions, and that some old versions do not blink at all.
- Try the other network port. The port on the E-stop box and the port on the control box use different addresses. 192.168.57.2 on the control box usually answers even when the WebApp does not.
- Connect an HDMI monitor to the control box and restart the controller. The boot log shows the network setup. Two users found their real controller IP this way and fixed it from a laptop. If the screen stays black, restart again or try another monitor.
- Open Web Recovery on port 8050. It can install software or run a factory reset, and it solved at least one case where the reset button did not help.
Related
- Unable to access WebApp covers a WebApp bound to the wrong network card.
- How to connect your laptop to Fairino WebApp covers the normal setup.
Please reply with
- Robot model and software version, if known
- Which port you are connected to
- Ping result for 192.168.57.2 and 192.168.58.2
- What the HDMI boot log shows
- Which step solved it