User already logged in (when not) on hub
Recently, when I want to configure my hub 3.0 for port forwarding etc, I get this when I try to log in. No one is logged in, I even made sure to log out of my last session, but it still does this: "...
Forum Discussion
Using Firefox the Hub 3 works a charm in the Port Forwarding management screen.
Does the Hub 3 fail during Port forwarding in Chromium browsers Chrome & Edge ?
The port forwarding works fine but it's when editing the port forwarding rules that you tend to get locked out. The scenario is something like this:
1. Make a change to port forwarding
2. Go away and maybe test that, leaving the console open
3. Come back (say) 5 mins later and try making another change
4. You get locked out with other user logged in
My theory is that this happens most on port fowarding because that's a screen that you might hang around in. Most other changes to the router are done and finished in minutes.
So the fault is most likely the current session timing out without the user cleanly leaving thus when you attempt to logon on again, it thinks somebody else is in there.
1. Make a change to port forwarding
2. Go away and maybe test that, leaving the console open
3. Come back (say) 5 mins later and try making another change
4. You get locked out with other user logged in
My theory is that this happens most on port fowarding because that's a screen that you might hang around in. Most other changes to the router are done and finished in minutes.
So the fault is most likely the current session timing out without the user cleanly leaving thus when you attempt to logon on again, it thinks somebody else is in there.
If I get locked out of the Hub 3, I close the web browser, restart the web browser and visit the Hub 3 >>> Check router status pages
Now wait (a couple of minutes) for the browser to create the Hub 3's cookie "192.168.0.1"
Once the "192,168.0.1" cookie can be seen Remove it & now I can re-login to the Hub 3 menus.
Happened to configure a site with a Virgin Media business service yesterday using the Hitron router. That has an option to "Force logout" which is a much better solution IMO. Shame the home hub doesn't work in the same way.
I'm sure this is getting worse! I've just done this:
- Not logged to 192.168.0.1 for days
- Logon and delete port 80 and 443 port forwarding (as can't edit IP shame)
- Try to click add to add them back with different IP and bang - another user logged on
Not exactly a complicated operation!
Plus the SuperHub takes ages to restart. I'm used to Mikrotik ROUTEROS which takes about 30 seconds to reboot. The Superhub takes over 5 minutes before the link is stable and up.
This worked for me. Thanks.
