Hello, I have been trying to access my new hub to change some settings but for the life of me, I cannot read what a certain character is on the bottom of the router. I have tried 8, e, and an a, all with no success. Each time I get the password wrong, it gets longer before I can enter another. Here’s hoping someone can help because this is very frustrating now.
Try a zero ?
Yes, not 0 either
or a e or o
also case sensitive
I have tried the following without success:
a, e, 0, A, E, O and 8
Maybe it is actually one of those but another character is in fact something else.
....and this is why default passwords like 1234 existed
maybe you have to post the full password or ask VM for another hub 5
A mangled g or a 9 ?
Just ask for a replacement Hub as the password is illegible ? Or, on the very small chance the password is still from the past owner, try a 60 second pinhole reset back to factory settings.
Tried a factory reset in case it had been changed but not getting anywhere with it. I’m just going to have to ask for another one as this password is clearly unreadable and hub needs to be binned. Quality control is **bleep**e these days it seems
Forum TeamHi, I'm very sorry to hear about the issues you're having with the hub settings password. That character looks like it could only be an e or a zero so if that hasn't worked, and a factory reset hasn't worked, we'll need to get an engineer out to you. I'll send you a private message now. Please look out for the envelope in the top right of the page and pop back to me when you can.
Looks like the same issue i had when i first got my router, but mine was actually an e
New Hub 5 Settings Password Not Recognised | Virgin Media Community - 5364588
Doesn't the card also have the settings password?
Nope the card bit only has wifi
Only for wifi
Forum TeamHi Reddragonzz
If you could respond to the PM my colleague has sent :) we'll be able to assist you.
I doubt they use the Greek alphabet but it could be a theta: θ
I suspect the password has been corrupted internally. I have seen the same on a hub at work.
Factory reset and a forced firmware downgrade & upgrade cycle will probably fix it. Needs to go back to their repair centre, so get it logged as faulty.
