v1.5.5 Bug Reports and Comments

[Stephen]

Great! OK I will use the info you posted to try this out.

I have to replicate your environment exactly so the test will take some time. I'll let you know here if I see it or if I find a config problem. Obviously if there's a bug I'll work on it for the next release.

[Stephen]

mrmarria, it is definitely a bug. Watch for a new RC release.

[mrmarria]

Stephen-

Thanks for verification, I was blaming the power hungry Ubiquiti for most problems, for a while, but it became a head scratcher for sure.
This will be a really useful tool in winter with short solar charging hours.

Michael

[jason.brand@wanna.net.nz]

Hi Team, have just loaded 1.5.5 on ws-12-250-dc ,board rev F, power supply version 70 and power supply board rev C.
I cannot calibrate the input voltage. no matter how many times i input the correct voltage the switch just comes back with the same old voltage reading. i.e it always says 22.7 no matter if i calibrate at 23.5 or 23.2 or 23.0 for example it still says 22.7. i tried calibration change from the GUI.

I also tried telnet into the switch and ran command calibrate. inputted correct voltage reading and it set it correctly in the gui, however when i ran the command calibrate again and set the voltage i now have a NAN in the GUI.



Any ideas
Thanks
Jason

[Dave]

I will have Stephen to look at this today..thanks….

[RebusCom]

I'm running v1.5.5 on switches and with the latest version of Firefox v74.0 TLS 1.0 and 1.1 is automatically disabled. It won't connect to the GUI without a Error code: SSL_ERROR_UNSUPPORTED_VERSION. Re-enabling TLS 1.0 and 1.1 restores the ability to connect to the GUI, but Mozilla has posted that in a near future release the ability to support TLS 1.0 and 1.1 is being removed permanently.

[Stephen]

RebusCom thank you for the update, I've got it added to the list for the software.

jason, not sure exactly what could be causing that. Just tested it on the PS rev B and it's working OK. Can you tell me more about your setup? How are you powering the switch?

Also can yo take a screenshot of the "NaN" error? Might help me track it down.

Some more thoughts though, If you default the switch you might be able to get rid of the NaN error, and if you can get a number again. The switch has to take several samples of the input voltage over a brief time period. So when you set the calibration voltage next, try giving it some time, I'd say max 5 minutes, and see if the voltage has changed to what you're expecting.

[Banana Jack]

Just a quick report that I successfully upgraded 81 Netonix switches over the course of this week from 1.5.2 to 1.5.5 and everything went great! One switch seemed to go offline after the upgrade but when I rebooted the Station connected to it, it became accessible again. Another's SNMP voltage failed to be readable by PRTG but after a reboot it was fine.

A lot of switches showed on Netonix Manager as being stuck on "Rebooting" but when I deleted and re-added them, they showed up again no problem.

I'm especially pleased to see that stability is improved in this firmware, not that I'd ever found it to be an especially big problem on 1.5.2. Congratulations to the team on an excellent release. Keep up the good work!

[LBNL]

It seems we STILL have the problem of not being able to access the web gui with Invalid "username or password" being returned despite being able to ssh into the switch in question.

Do we have a fix for this at all please?

Thanks

[Banana Jack]

It seems we STILL have the problem of not being able to access the web gui with Invalid "username or password" being returned despite being able to ssh into the switch in question.

Thanks

I've never personally seen this but it could be that your browser session has expired but the screen hasn't updated. This sometimes happens whilst being in the GUI (after logon). Just press F5 or CTRL-R to refresh the screen and then you know that the logon page is "live" and not just a cached/expired version.

Also try a different browser. Also try browser private mode to ensure that no stale cookies or browser add-ons/extensions are causing any problems behind the scenes.