Web redirect

https://www.plus.net/view_my_broadband_usage/index.p... requests still being redirected to https://portal.plus.net/apps/paymentdetails/manage/

Was told this was down to IP, but as I have had several IPs (at least one "requested" by the reseting of my router) and the problem still persists, can someone please look into?

Hi there,

Believe this is under investigation, I'll get it chased up for you and update you shortly after lunch. Sorry it's still going on :/

Thanks.

Right, I've had a word with one of our developers and he's basically reset things on the kit that does the redirect. It might not change until you disconnect and reconnect though.

Really hope what he's done works, please let us know either way and I'll feed back/push further as required.

Righty-o.

Cheers.

https://portal.plus.net/view_my_broadband_usage/inde... OK.

https://portal.plus.net/view_my_broadband_usage/inde... goes to login.

then to https://portal.plus.net/apps/paymentdetails/manage/

Will let you know next time I disconnect router.

Is this what you were referring to? :-

"Subject: Broadband usage reporting (75889) - RESOLVED"

"Further, all accounts that were incorrectly restricted have now had those restrictions removed."

Just logged in and got re-directed to https://portal.plus.net/apps/paymentdetails/manage/ again, so you may want to add "after customers re-set their routers" if this indeed is the case?

Hi HK11,

Your service profile has reset, but as I said above:

In reply to a post by orbrey:

It might not change until you disconnect and reconnect though.

As your current connection has been ongoing for over 16 days I suspect that's why it hasn't actually taken effect yet, just drop the connection then reconnect and you should be fine.

Yes which is why I suggested you add a bit to the end.

I will advise if it works when I disconnect.

Your issue wasn't caused by the problem mentioned on the service status, that was just an unforunate coincidence! As far as I'm aware those affected by the problem shouldn't need to disconnect/reconnect.

In reply to a post by chrisparr:

those affected by the problem shouldn't need to disconnect/reconnect.

OK.