Trouble with https access

[Kirke Holmes]

Hello,
I have an ASUS RT-N66U and an RT-AC66U and using merlin 380.57. I'd like to strictly use https to get into them, but I've been having trouble. As a halfway measure I used the "Both" setting for the Authentication Method. Just to make sure I could get in using https://xxx.xxx.xxx.xxx:8443, but no luck. Chrome gives me a page not found error. When I click on the hyperlink next to the place where I could change the port number it chrome complains that there is a certificate issue. But I have no problem getting in with http://xxx.xxx.xxx.xxx

Any advice would be appreciated.

 

[buddyp]

Chrome complains about the certificate because it is self-signed, which means the connection is encrypted but not authenticated.

Click on "advanced", and then click on "proceed anyway"

 

[Kirke Holmes]

When I do that it displays https crossed out in red. Doesn't that mean I'm not connecting using https?

 

[martinr]

When I do that it displays https crossed out in red. Doesn't that mean I'm not connecting using https?

Just to clarfy: are you talking about internal or remote access?

If you check your browser' address bar I'm sure you'll see you are connected to the https address. But what it means is, yes, the connection is encrypted but anyone can log in via https, just as with http, if they know the username/password combination.

If you search the forum you may well find more information.

However, if you are talking about remote WAN access, you should ask yourself do you really need remote login and if you do it is safer to do so using ssh with public- key infrastructure (key pairs and passphrases) or vpn access, and to close down the WAN access option.

If it's just internal access and you've blocked WAN access, then https access would help only if you aim to prevent internal interception of your login details, but I doubt you are worried about that inside your network, especially if it's a home network.

Did you try another browser eg Firefox? Obviously, it's not going to connect differently, but sometimes you'll get a more explicit (understandable) message, and sometimes the other browser will refuse to let you carry on unless it sees trusted certificates.