Netonix Forums

With Chrome's latest update 98.0.4758.8 it can no longer connect to the WebUI. Older ciphers (TLS1.0 & SSL3) are now blocked.

This also affects Edge. We need a build with TLS 1.2 in it ASAP.

Ditto. Having to switch between browsers to log in to my Netonix switches.

This needs to be addressed sooner rather than later.

Also hit this issue today, can we please have a fix soon other than 'enable http'.

Thanks.

Crickets.....

TLS 1.0/1.1 have been depreciated for years. Why is this even an issue today?

This has been a problem on Safari for a while now (a year or longer). Chrome was my backup option just for Netonix, and now that door's closed.

So now I'm on a third browser, Firefox. No telling how long Mozilla will allow users to enable TLS 1.0/1.1.

Some of the things we are working on:
Update UI for new browsers
Update mail service/client for email notifications
Work on WS3 SFP+ configuration
Upgrading WS line to deal with a new current sensor since we can not get old current sensor due to semiconductor shortages

When do we expect to have new firmware: "hopefully" this month (February)

sirbryan wrote:This has been a problem on Safari for a while now (a year or longer). Chrome was my backup option just for Netonix, and now that door's closed.

So now I'm on a third browser, Firefox. No telling how long Mozilla will allow users to enable TLS 1.0/1.1.

Just don't update Firefox or Edge (Yes, even Edge Version 98.0.1108.43 is unhappy)!
Samsung Internet on my Android phone is the only browser that still connects, but I feel uneasy logging into a live device on a touchscreen

I am hit by the same issue since this weekend... I see it's been worked on.
Any ideas when this issue gets solved? It's really annoying that all my shortcuts to Netonix devices that opened in my default browser (Chrome) and my backup browser (Edge) are nog allowing access to my Netonix.

I had to instal Firefox but even that one comes with the warning the certificate of this unsafe website will be no longer supported soon...

I noticed though that in setting the Netonix http access to port 8080 solved the issue and the browsers open normally given port 8080 is used. How come? Is the certificate only working on port 80? Don't understand...

I run Kali Linux in a virtual machine, with it's network interface in bridge mode.
This allows me to connect to the switches using it's version of Firefox without too much trouble, allows you to bypass all the errors.

Would be great to see a new release soon :)

Cheers
Dan