[jay ray]

A few days ago I set up a WAP from scratch. The last step I took was to tick the option for https access. After that I was unable to access the GUI because firefox changed the way they handle certificates.



This page used to have an advanced option where users could establish an exception for the site. But Mozilla is apparently taking a harder line on certificates recently and just refuses to go any further.

Microsoft Edge also blocks access due to "outdated or unsafe TLS security settings".

Chrome simply times out and suggests I check my internet connection.

It seems like all the browsers decided to do this at once. This will be a huge problem if I want to update firmware on my primary router or, dog forbid, need to revert to factory for any reason.

Is https access no longer viable for everyone of us? Am I maybe missing some kind of certificate configuration? What can I do to access the gui?

[Alozaros]

https GUI access to the router is broken, you have to click here and there to allow this connection look for any available click spots and agree to permit this connection..
You can also update https certificate if its so important for you http://www.dd-wrt.com/phpBB2/viewtopic.php?t=27979
https://www.dd-wrt.com/phpBB2/viewtopic.php?t=154874&sid=94f621914b4eeddc88a4bf49e87e9bd3

otherwise use http access to GUI

[TheMercenary]

Use chrome. You can tell it to ignore the error and just continue

[Per Yngve Berg]

Do you have telnet/ssh access to the router?

nvram set http_enable="1"
nvram set https_enable="0"
nvram commit

[jay ray]

Thank you everybody for your suggestions. And no, Per, I didn't have ssh/telnet. Setting those up are always the last step once everything else is in place. The second to last step is https.

In the end it was simpler to reset and reconfigure, this time without https. Which concerns me a little. Is this going to happen when next I upgrade the firmware on my main router as well? I admit to being out of the loop where certs are concerned.

[statikeffeck]

Hi all. Apologies for the thread resurrection from the dead, but came here from a Google search and I wanted to post my solution since I did not want to reset my router settings from scratch. First of all, it was dumb of me to enable HTTPS and DISABLE HTTP in the SAME settings change event, before testing if HTTPS actually worked on this thing

To get back into my router (I didn't have Telnet or SSH enabled) I opened my Ubuntu 18.04 in VirtualBox and downloaded Firefox 7.0.1 from https://ftp.mozilla.org/pub/firefox/releases/7.0.1/ -- great that they have every release ever! I unzipped it, and simply ran `./firefox` from the terminal. I entered https://192.168.1.1, confirmed the security exception, and sure enough I was back in!

Enjoy

Edit: P.S. after seeing my posts on this forum, looks like I did this same mistake in 2015 and fixed it with a similar solution of using an old version of Firefox. LOL! My memory is fading in these years.

[ptreadaway]

My heart sank when I thought I had to launch into another skein of tasks to get back into my DD-WRT as I had done the exact same thing.

Anyway, turns out you can launch Chrome and tell it to ignore SSH warnings. This worked for me, I switched off HTTPS and turned HTTP back on!

On Windows

"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --ignore-certificate-errors

On Mac OS

/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --ignore-certificate-errors --ignore-urlfetcher-cert-requests &> /dev/null

Original Post:
https://medium.com/idomongodb/chrome-bypassing-ssl-certificate-check-18b35d2a19fd

[the-joker]

@ptreadaway

Welcome to our lively community.

Your workarounds are great, only if you use the methods above only for DD-WRT, but not recommend for normal usage.

Its far easier to add a certificate exception to browser for DD-WRT and ignore the dumb its not safe site nonsense.

[jwieland]

I see this with Firefox after I load an update on my router. All I have to do is to have Firefox reload the page (control F5 for instance), and then Firefox will display the page that lets you go on to accept the new certificate.

[kernel-panic69]

Private Browsing Mode. Specifically from experience as I use it most of the time, Pale Moon Portable in Private Browsing Mode does not have this problem.