Log onto Hub 3 - another user logged in.

[eddie00001]

I’m trying to login to the Hub 3 but keep getting an error saying someone else is logged in.
I’ve rebooted the Hub, but still get the same error message.

[jbrennand]

Try a different browser.
Also, if on a wifi connection, try an ethernet cable connected device - and vica versa.

[eddie00001]

Just tried on a different laptop, browser and with a wired connection. Same error message about someone else logged in.

[jbrennand · Accepted solution]

You could reset it to factory settings. Note if you do that - any changes you have made in there previously will be removed and have to be put in again. e.g. if you changed the wifi password then all devices will need to use the default one until you change it again.

-------------------------
With the Hub "on" push in the pin on the back/side/bottom of the Hub with the end of a paperclip/thin nail or similar (bigger items like ball point pen ends may not press it in far enough) until you feel it at the “stop point” and hold it there firmly for a "timed" minimum of 60 seconds do NOT restart the Hub after that. Leave it 5' or so to stabilise and then your passwords/passphrase for both the Hub settings and the Wifi networks will revert to the two printed on the Hub sticker on its base/side/card. Make sure you use the wifi one for devices connecting to the wifi and the settings one to access the Hub.

[eddie00001]

That did the trick, thank you 

[TMD10]

Did that still got the same problem 

[gary_dexter]

Don’t use the connect app

[PedroMac]

Why not? Surely the point of the connect app is to directly access hub settings. Not very user friendly if this issue keeps repeating and the only option is to restore to factory settings.

[gary_dexter]

Just go to 192.168.0.1 in a browser to get to the (more intuitive) hub settings. 

[Lcarru]

I get this error repeatedly either through the connect app or through web gui, even in incognito mode.  The only way I’ve found to resolve it is a factory reset but I have to do this every single time, then 24 hours later, same error.  This is really frustrating, surely VM should have fixed this by now as there seems to be a lot of posts with the same error