headstruck Posted July 16, 2021 Posted July 16, 2021 I just tried to log into the web interface to open a port, and got this: I've never seen this before, and I'm using an XR1000.
Netduma Liam Posted July 16, 2021 Posted July 16, 2021 Could you try accessing it from an incognito window, or clear your cache? Then try accessing the interface again and see if you're still getting the same error.
headstruck Posted July 16, 2021 Author Posted July 16, 2021 33 minutes ago, Netduma Liam said: Could you try accessing it from an incognito window, or clear your cache? Then try accessing the interface again and see if you're still getting the same error. Incognito window didn't do anything, and I don't feel like factory resetting again for the second time this month. I'll reboot it and see what happens, and of course report back here with the progress.
headstruck Posted July 16, 2021 Author Posted July 16, 2021 I rebooted and it just factory reset itself - this is the second time now in the past month
Netduma Liam Posted July 16, 2021 Posted July 16, 2021 How did you reboot, using the physical button on the router or through the web interface? I've seen a user experience this before and they didn't report back with any issues after re-installing the same firmware over the top, so you could try that!
headstruck Posted July 16, 2021 Author Posted July 16, 2021 1 hour ago, Netduma Liam said: How did you reboot, using the physical button on the router or through the web interface? I've seen a user experience this before and they didn't report back with any issues after re-installing the same firmware over the top, so you could try that! I simply turned it off by pressing the toggle button on the back of the router - the web interface was inaccessible due to the bug above. Anyway, I can't tell you what solved it since, like I said, it factory reset itself after I physically rebooted it, so it could have been either of the two.
Administrators Netduma Fraser Posted July 16, 2021 Administrators Posted July 16, 2021 Odd, at least it's resolved now. If it happens again let us know, we should have a new firmware relatively soon so hopefully you shouldn't get it again
Recommended Posts
Archived
This topic is now archived and is closed to further replies.