Netonix Forums

In all of the excitement from upgrading I have one particular unit that has developed a bit of a strange problem relating to logging in.

WS-26-400-IDC running 1.5.22 and we find ourselves unable to login via the web. When I enter the user/pass into the form it waits 5 seconds and then reloads the page. If I supply the wrong login then it will give me the "Invalid username or password" message as expected. I can login via SSH with the same credentials. I have tried doing a web config check which passes, I have also tried changing the password but no difference. RADIUS is enabled but not functional.

Is there anything I can do via SSH to solve this? Would prefer to not have to reboot or upgrade if I can help it.

login via SSH use the command to set credentials = username and password
Don't forget to hit enter a couple times in SSH to confirm changes
Then try UI login

Some rare occasions I have seen this reported where people can login via SSH not UI. Some rpeorted if they refreshed their browser or used another browser UI login worked as if it was caching the old login page?

Current version is v1.5.23

v1.5.24 should be out soon with a fix for SMTP an odd issue that effects very few people with NTP and an issue with a mono fiber SFP to media converter.

There are a "few" people with PPPoE and or multicast with SFP ports but other like me have no issue?

These are the last remaining issues we are aware of. MOST people have no issues with v1.5.23 but a few do and we are trying to figure out why and if it is us fix it.

oeyre wrote:In all of the excitement from upgrading I have one particular unit that has developed a bit of a strange problem relating to logging in.

WS-26-400-IDC running 1.5.22 and we find ourselves unable to login via the web. When I enter the user/pass into the form it waits 5 seconds and then reloads the page. If I supply the wrong login then it will give me the "Invalid username or password" message as expected. I can login via SSH with the same credentials. I have tried doing a web config check which passes, I have also tried changing the password but no difference. RADIUS is enabled but not functional.

Is there anything I can do via SSH to solve this? Would prefer to not have to reboot or upgrade if I can help it.

You should be able to clear it without rebooting over ssh via the following command from the linux shell:

Code: Select all

/etc/init.d/lighttpd restart


Then, try logging in again

Stephen wrote:You should be able to clear it without rebooting over ssh via the following command from the linux shell:

Code: Select all

 /etc/init.d/lighttpd restart

Then, try logging in again

Thanks Stephen,

For the time being we will make do with CLI & SNMP. Will advise how it goes after our change freeze ends (or sooner if the need arises).

The need finally arose... This is the second unit we're aware of this problem happening (1.5.22).

Using the lighttpd restart I was able to regain web access. I'm not sure if the second restart was needed however it no longer errored after that.

Code: Select all

switch# cmdline
admin@switch:/www# /etc/init.d/lighttpd restart
2024-12-31 13:26:58: (network.c.310) can't bind to socket: 0.0.0.0:80 Address already in use
Segmentation fault
admin@switch:/www# /etc/init.d/lighttpd restart
admin@switch:/www#

Thanks Stephen!

I've just tried the lighttpd restart on my original unit, and no change/success. No error this time either.

Code: Select all

admin@switch:/www# ps ax | grep http
388 admin 2680 S grep http
 1480 admin 7764 S lighttpd -f /etc/lighttpd.conf
 1488 admin 8736 S lighttpd -f /etc/lighttpd.conf
 1489 admin 8424 S lighttpd -f /etc/lighttpd.conf
 1491 admin 8448 S lighttpd -f /etc/lighttpd.conf
admin@switch:/www# /etc/init.d/lighttpd restart
admin@switch:/www# ps ax | grep http
 522 admin 7764 S lighttpd -f /etc/lighttpd.conf
 530 admin 7784 S lighttpd -f /etc/lighttpd.conf
 531 admin 7784 S lighttpd -f /etc/lighttpd.conf
 532 admin 7784 S lighttpd -f /etc/lighttpd.conf
 538 admin 2680 S grep http

Any other troubleshooting suggestions?

Having upgraded to 1.5.25 this problem seems to have been resolved, I wonder if this was it:

- WebUI Sessions can now expire, but will remain open with the webui - 1.5.23