It seems some recent security update has changed something such that I can no longer log in to the web interface properly with safari on the mac.
The first error says the website has an outdated security configuration which may allow an attacker to steal ...
The further explanation says, Safari warns you when a website uses TLS 1.0 or 1.1 which are not secure.
It allows me to visit anyway after entering my computer password. Then after logging in to the wisp I get a blank page that reloads after a few seconds and that cycle seems to repeat over and over.
I can login fine with Firefox after going past the security warnings. Is this going to be fixed in an update soon? It is very annoying.
Thanks.
Problems logging in with Safari
-
Stephen - Employee
- Posts: 1033
- Joined: Sun Dec 24, 2017 8:56 pm
- Has thanked: 85 times
- Been thanked: 181 times
Re: Problems logging in with Safari
Noted, putting it on the list for the next major release.
Re: Problems logging in with Safari
Was this ever resolved? I can't log in to any of our Netonix using Safari 15 on OSX Big Sur. The login page loads (without logo) and logging in produces a blank page which endlessly reloads...
Older Safari and Google Chrome on OSX works as expected.
Older Safari and Google Chrome on OSX works as expected.
- nzjimmy
- Member
- Posts: 10
- Joined: Wed Feb 20, 2019 5:07 pm
- Has thanked: 0 time
- Been thanked: 0 time
Re: Problems logging in with Safari
I'm seeing this now on Mac OS Catalina - any solution available?
Thanks.
Thanks.
-
sakita - Experienced Member
- Posts: 206
- Joined: Mon Aug 17, 2015 2:44 pm
- Location: Arizona, USA
- Has thanked: 93 times
- Been thanked: 80 times
Re: Problems logging in with Safari
What changed on the computer end? New Safari version?
What version firmware is on the switch? I've had older firmware versions flat out not work with updated browsers (requiring alternate methods to update the firmware - e.g. Netonix manager or login with SSH and pull firmware with FTP).
Even with 1.5.14 the certificate it uses for https will be considered untrusted but Chrome works after complaining about it.
With Firefox you can allow TLS downgrade to make it work (although there are security implications).
What version firmware is on the switch? I've had older firmware versions flat out not work with updated browsers (requiring alternate methods to update the firmware - e.g. Netonix manager or login with SSH and pull firmware with FTP).
Even with 1.5.14 the certificate it uses for https will be considered untrusted but Chrome works after complaining about it.
With Firefox you can allow TLS downgrade to make it work (although there are security implications).
Today is an average day: Worse than yesterday, but better than tomorrow.
5 posts
Page 1 of 1
Who is online
Users browsing this forum: No registered users and 53 guests