Certificate error when loging into Technicolor TG582n

[#1]

Firstly I would like to say hi, as this is my first post on the forum. unfortunately it is due to an issue early on in my FTTC career'
I had my FTTC fitted on Friday and other than some early teething issues with wifi speed, which turned out to be a slow wifi card in my laptop, its been great.
Today I wanted to log into the plusnet router to get some information I needed to try and set up a dgn2200 as a wifi bridge for a couple of non wifi pc's upstairs. When trying to log in, I was met with an error message regarding the certificate from the router being unrecognised and recommended going no further. I tried on my laptop and had the same error message. I suspect the certificate has some how become corrupt.
For now I have reconfigured the DGN2200 to work as the main router and taken the TG582N out of the system. However this router is not as fast on the wifi side, and wifi connection has dropped from 66Mbps to 45Mbps. I get 74-76Mbps hard wired to the router so quite a loss bearing In mind I am only 5M away from the router in the same room.
I rang the technical desk today but they told me they had never heard of this before and as the router was still connecting to the internet, to not worry about it. I'm not happy to do that as I don't understand what has caused it and if it remains secure.
Anyone have any ideas on how to rectify the TG582N or will it get replaced for a new one.
Thanks in advance for your help.

[#2]

Hi elsinor5,
Sorry the delayed response.
Just a quick thought, have you tried completing a Factory Reset on the affected router to see if this resolves the potentially corrupted certificate?

[#3]

If the 582n serves up SSL certificates, presumably it needs a valid time or date to generate them ?
Just a thought but worth a double check (as is the time / date on whatever you are using to view them).
Is there a "more info" button on the certificate rejection that you can use to copy and paste here ?

[#4]

Are you entering:-
https://192.168.1.254 ? as this not necessary. Try just typing 192.168.1.254
DaN

[#5]

Yes, this is the issue.
https://192.168.1.254 will encrypt your connection and your browser will attempt to verify the identity of the router via its SSL certificate. The device doesn't have an SSL certificate so your browser will complain.
http://192.168.1.254 won't encrypt your connection and your browser won't attempt to verify the identity of the router, shouldn't be any complaints from the browser
Matt

[#6]

Hi all, Thanks for the reply.
I had been logging into the PN router for a few days from both machines without issue. I tend to always use http://192.168.1.254 and hadn't had an issue.
All of a sudden both machines returned the same cert error.
I have currently removed the PN router from the system and replaced it with my old netgear dgn2200 which I reconfigured.
when I get time I will plug the PN router back in and try again. If the same issue arises I will copy and paste the text.
I

[#7]

Thanks again for the replies guys,
I see today someone else has had the same issue.
The wife is working from home today and using the network so I wont get an opportunity to plug the PN router back in and try again. error messages are exactly the same as the ones in the other post.
I was unaware of the difference between http:// ; and https:// I normally open a google home page in IE then delete everything in the address bar back to the // then enter the 192.168.1.254. I can only assume if this is the case that at some point something has happened and changed http:// to https:// . certainly nothing I have knowingly done.
Thanks
I

[#8]

That's what these forums are for

[#9]

I an on ADSL
However
My bad as I inadvertently typed HTTPS as opposed to plain HTTP

[#10]

Well I have today plugged in the Pn router and as you quite rightly said when I pull a google page it is an https page. I had never noticed it and have no idea of the difference. First time I have ever come across this. Well as said when you remove the 's' it logs straight in without issue. You learn something every day.
Now to research this https vs http.
Thanks for the help.
I

[#11]

Right, normally you should prefer a HTTPS connection over a HTTP one as the data is then encrypted over the network.
HTTP = Hyper Text Transfer Protocol
HTTPS = Hyper Text Transfer Protocol + SSL,
SSL = Secure Socket Layer

Never ever enter payment details or sensitive stuff like internet banking unless you are using a HTTPS connection as the connection is not secure, in fact personally I would not even enter my name and address unless I was using a secure connection. When using HTTPS you will see a padlock appear by the address bar to confirm that the connection is secure.
This webpage from Microsoft gives a quick 2 second explanation of the difference: http://blogs.msdn.com/b/securitytipstalk/archive/2014/01/21/what-is-https.aspx
A simple but slightly longer explanation is here:
http://www.tomsguide.com/us/use-https-safer-browsing,review-1885.html
As a demonstration these two links will take you to the same page, with the first being the insecure connection and the later the secure one:-
HTTP
http://en.wikipedia.org/wiki/HTTPS
HTTPS
https://en.wikipedia.org/wiki/HTTPS
Another thing I do is ensure that all my emails are sent over SSL/ TLS to ensure that they are reasonably secure as like most people I do send an amount of personal and confidental information by email.
If your really paranoid like me you can use a tool called HTTPS everywhere to enforce HTTPS where possible on sites you visit, but most would likely say that's being over the top unless you live in China or North Korea
https://www.eff.org/https-everywhere
I get concerned when I hear of people who don't about HTTPS as it's something very important to be aware off as without it's akin to sending postal mail in transparent envelopes or consulting with the doctor in the waiting room!

[#12]

Thanks Wintonian.
Very informative. I was intrigued why using https when trying to access the router was initially ok then returned a certificate error after about 3 days of use.
Interesting stuff but at least I now know the reason for the certificate error even if not why.
I