Problem loading switch interface in Chrome on Mac

[nelson05]

Here is the message I receive... can't seem to get past this warning and access the UI of the switch unlike other HTTPS sites with untrusted certificates (like ubiquiti equipment) where once you click Advanced there is a Proceed button, which lets you in.

Screenshot 2014-11-02 22.36.54.png (255.48 KiB) Viewed 8332 times

[sirhc]

Hi Nelson,

Is this Chrome on Windows or MAC?

What version of OS is your Windows or MAC?

What version of Chrome?

What version of the firmware are you using on the switch?

I have not run into this issue with Chrome on a windows 7 machine, ever.

[sirhc]

This is caused but the default Linux date being so OLD, 1969 to 1970.

You can fix it by setting the correct date on the switch via NTP service and then run this command at the Linux console

openssl req -new -x509 -keyout /etc/config/lighttpd.pem -out /etc/config/lighttpd.pem -days 3650 -nodes -subj "/"

Remember when you console into the switch you are first landed on our CLI not the Linux shell so you have to type "cmd" and press enter to drop to the linux shell.

After you are done type "exit" and press return to return to the CLI and then type "exit" and press enter again to exit the console.

This will be fixed in the next release of firmware later today.

Thanks for pointing it out.

[lligetfa]

I noticed that I cannot paste that command to the console. Is it just me or by design? If I copy text from the console, I then have the option to paste that so the copy and paste options are there.

[sirhc]

Not in our HTML console no, work in progress!

If you are using a shell program like PUTTY yes.

[nelson05]

Unfortunately the procedure still hasn't solved the issue on Chrome on the Mac. While the date of the certificate is correct now, with it expiring in 2024, I still receive a NET::ERR_CERT_INVALID error stating:

Screenshot 2014-11-05 14.24.25.png (185.09 KiB) Viewed 8313 times

I received this message after updating to the newest firmware and running the command posted in the thread, which seemed to successfully update the certificate since it now displays a new date.

Any ideas? Would really like to be able to use the Mac and Chrome to monitor the switches.

Thanks.

[lligetfa]

For Chrome on ubuntu I would normally create a custom shortcut with the following parms to ignore cert errors and start it in app mode so there is no URL bar to navigate away with.
/opt/google/chrome/google-chrome --test-type --ignore-certificate-errors --app=https://192.168.1.207

Unfortunately, something broke and I can no longer use Chrome on ubuntu to access the switch.

[Eric Stern]

Unfortunately the procedure still hasn't solved the issue on Chrome on the Mac. While the date of the certificate is correct now, with it expiring in 2024, I still receive a NET::ERR_CERT_INVALID error stating:


I received this message after updating to the newest firmware and running the command posted in the thread, which seemed to successfully update the certificate since it now displays a new date.

Any ideas? Would really like to be able to use the Mac and Chrome to monitor the switches.

Thanks.

Chrome on Mac OS is really fussy. Anyways, I was able to get it working by using this command (just a small change from the above one):

openssl req -new -x509 -keyout /etc/config/lighttpd.pem -out /etc/config/lighttpd.pem -days 3650 -nodes -subj "/C=US"

Of course make sure the time is correct on the switch before doing that.
After that you need to restart the web server (so it loads the new certificate) with this command:

/etc/init.d/lighttpd restart

Then reload the webpage in Chrome and it should allow you to continue.

[Eric Stern]

For Chrome on ubuntu I would normally create a custom shortcut with the following parms to ignore cert errors and start it in app mode so there is no URL bar to navigate away with.
/opt/google/chrome/google-chrome --test-type --ignore-certificate-errors --app=https://192.168.1.207

Unfortunately, something broke and I can no longer use Chrome on ubuntu to access the switch.

Seems to work fine for me using Chrome 38.0.2125.111 on Ubuntu 12.04.03 (32 bit). Maybe try the command I just posted above and see if that helps?

[lligetfa]

That was just what I needed. Working fine now on Chrome/ubuntu. Thanks Eric, you da man!