Plusnet Hub 2 new firmware forcing https

[#1]

I am using the pink and white Plusnet Hub 2.

Firmware version:

v0.11.01.11071-PN

Firmware updated:

17-Jun-2026

[#2]

So, @doug1  - are you now sorted?

[#3]

I have an adequate workaround.

Normally the https SSL would be validated by certificates, so I am still confused why t need to login using the Admin password.

Being able to read the device IP addresses was a useful addition to the Hub1.

I can now ping my Raspberry Pi by hostname.

I really like the way the dhcp allocated IP address remain constant, based on the mac address.

I got in a muddle if I move the Raspberry Pi card from hardware to another Pi as the MAC address changes.

Another fact to add to my "Unknown Theorems" - The Great Unknown and Little Known Theorems.

[#4]

Needing to enter username and password and ssl inc certs are 2 separate things

They could have still used http when asking for the login details but they would be sent clear text

[#5]

Connecting to Hub 2 (via WiFi) with http://192.168.1.254 now opens: http://192.168.1.254/forced_https.htm which forces use of https via button (see screenshot X.png).  Note My firmware was updated to New Firmware: v0.11.01.11071-PN a few weeks ago.

Trouble is that when I click the button to open https://192.168.1.254 I get this page (see screenshot Y.png).  This shows an ERR_SSL_PROTOCOL_ERROR error message with no option to proceed / Advance / Continue.  I can find no workaround.  This happens with Chrome, Edge and Firefox.  Completely snookered. 

Plusnet - what can I do?

[#6]

Have you tried powering the Hub down? I only managed to get into mine after a cold boot.

[#7]

@Barbarian 

I tried  https://hub instead of http://192.168.1.254. 

certificates seem to need domain names, not ip addresses.

I also did a power cycle of the hub to restart it, as that did not need the Admin password!

nslookup does not return a hostname for 192.168.1.254

ping -a does not return a hostname for 192.168.1.254,

So how do you find out https://hub or https://bthomehub?

[#8]

@doug1 

For http://hub or http://192.168.1.254 using chrome on a raspberry pi 3b

What if you click Advanced, do you see

Then click on Proceed to hub (unsafe)

Do you get to the Hub two home screen?

See https://www.plus.net/help/hubgui/hub-warning/ 

[#9]

---

@doug1 wrote:

Normally the https SSL would be validated by certificates, so I am still confused why t need to login using the Admin password.

This has all been adressed previously.

Security warning when accessing the Hub Manager

https://www.plus.net/help/hubgui/hub-warning/

[#10]

Why does the Plusnet Hub 2 have a little padlock on each of the panels.

Why do I need the ADMIN passwork to view my devices? 

This is different to the https://192.168.1.254 issue, but rolled out in the same firmware update.

Self signed certificated warnings used to really bother me, so now I just "cycle through red lights" ! 

[#11]

@njay I agree.

The hub now has a little padlock on six of the panels, only the help does not has the padlock and you do not need the admin password.

[#12]

The reason the hub settings and similar pages now sit behind a login is almost certainly down to the updated EU CE rules under RED Article 3(3)(e).

That clause requires radio equipment to “incorporate safeguards to ensure that the personal data and privacy of the user and subscriber are protected.” In practice, that means anything showing device info, MACs, hostnames, IPs, logs, or user‑related data has to be protected by an admin password to meet the current compliance requirements.

[#13]

Most admin or management portals normally require a login before you can see anything.

The Plusnet (and BT/EE) routers were always a bit unusual in that some pages were viewable without signing in. With the newer compliance requirements, it looks like they’ve taken the safer route and put everything behind the admin password. It avoids any risk of falling foul of the rules around protecting user‑related information and device data.

[#14]

what I don't understand, and have said before - unless someone is actively spying on your network - which is highly unlikely, the fact that you have to be on your home LAN to access your Hub, and need to enter credentials anyway, in the form of your Hub password, makes the requirement for HTTPS a little 'overkill' - IMO.

[#15]

Agreed, but when have the bodies and governments writing these regulations ever shown a clear understanding of what they’re actually trying to achieve? Half the time it feels like they fire off a rule, hope it lands somewhere sensible, and leave everyone else to figure out the practical reality. Manufacturers then play it safe and lock everything down just to avoid tripping over the latest requirement.