Can't access the Hub Home page

[#1]

Hi

It's been a while since I looked at the Hub Home page in my browser, but thought I'd have a look today. when I click on the favourite with the IP address, I get a 400 error Bad Request message (If I try it on  Edge, it tells me it's insecure and won't let me access it.

I generally use a small Atria Mesh set up to access wifi, could that be the problem? (it never has been before).

John

[#2 · Accepted solution]

Following a recent Hub firmware update Edge may be grumbling about the Hub using a Self Signed Certificate.

There is usually an option to tell Edge or any other browser to continue regardless.

[#3]

Thanks. I can get in, although there are red flags all over the place saying it's insecure.

[#4]

Ignore the 'red flags' - it is only accessible on your LAN, so there is no danger.

[#5]

Welcome to the stupid world of IT Security !

Some bright spark came with the idea that home internet hubs and routers should use encryption to protect the credentials, so to appease these people that publish reports naming ISPs and claiming their kit is insecure, the firmware has been updated on millions of hub & routers to require HTTPS

This slams us into the next problem the use of Self Signed Certificates at which all web browsers throw their toys out of the pram, and home internet customers are picking up the phone to support in the thousands per day, and all to protect your Hub's admin password on you own in house network.

You might well think this is an ugly solution; I couldn't possibly comment.

[#6]

Some manufacturers haven't bothered about this - my FritzBox is still 'insecure' according to my browser - but am i bothered? Not in the slightest!

[#7]

Excuse me for jumping in, but I think there's something else going on. I recently had a replacement Plusnet Hub Two. I have been refilling the IP address name table so I can identify nodes.

Anyway, over the weekend, I stopped being able to log in. I can get to one screen, whether that's the "Switch to HTTPS:" or a preview of the Manager home screen or a login prompt. If I click anything, the browser times out. That's after ignoring any not trusted or insecure warnings.

OK, I tried another PC: Windows 11, mostly up to date, directly wired to the router as opposed to WiFi or powerline. Same result with Chrome, Edge and Firefox.

What's going on? Or more importantly, how can I fix it?

[#8]

Today's Update: I have now tried using the oldest browser/computer combinations that I have readily and not so readily available. Firstly, Silk browsers on Amazon Fire TV and Amazon Fire Tablet, then Firefox v106.0 on Windows 10 (32-bits), although that will update when I close it). Silk gets no further than reported above, with timeout errors after clicking on any of the buttons or trying to log in if asked for the router password. 

Firefox on Windows 10 allows me to view the certificate and offers downloads for PEM (cert) and PEM (chain). Are either of those useful to load into another browser?

I don't understand why there is a timeout? Previously, like last week, the router would respond quick as you like. Now it is slow to too slow. I'm not aware of any firmware updates unless they are automatic? I am a Windows Insider and update according to the Release Channel, but that doesn't affect the Fire platforms.

[#9]

Another update: I called Plusnet (aka Force 9) Tech Support and was told that a fix was being worked on but was not available as yet. However, while I resisted the suggestion of factory resetting the router, I did switch it and the fibre ONT off for a couple of minutes and then on again, ONT first.

When they came back up (pretty much straight away), I was able to log in to the router again!

So, that's a workaround with minimal disruption. It probably isn't necessary to switch off the ONT or leave them off for that long.

Maybe the home page, Restart the hub might work, although that will ask for the admin password?

Edit: I've just checked the Advanced settings page, Technical log, and that shows the Firmware version as v0.11.01.11071-PN, but more significantly, the Firmware updated says 6-Sep-2026, so a couple of weeks ago now. Looks like that's why it's happening now.