Cannot access GUI

[Stephen]

There have been reported situation's for this going all the way back to v1.3.6:
viewtopic.php?f=17&t=1652

Although there has never been any quantifiable or reproducible circumstance that would point to something code-wise that we could fix.

It could possibly be a hacker/bot trying to break in. If any of your switches are publicly accessible. Don't forget to use access controls to mitigate security risks.
Also make sure you are running the latest (as of now 1.5.2rc5) as there have been a few security related patches done in 1.5.1 which could help.

Also any sudden power fluctuations might possibly have caused the flash to get corrupted.

If it is happening continuously and the unit could not possibly under attack then it might need to be RMA'd because of the flash going bad.

[marlow]

Hi,

I had the same happening to me today after a prolonged power outage. No web access, SSH worked fine.

/etc/lighttpd.conf was blank. Repopulated the file, cold booted the switch and everything is back to normal.

This is a WS-12-250-DC running 1.5.2

So it is not an isolated issue. There is something corrupting the lighttpd.conf file

Switch is not on public IP and is on an isolated management network requiring VPN access. So it can be ruled out, that this is caused by hackers.

/M

[marlow]

For what it's worth, I had this happen to one of my Netonix switches this morning. Device working fine, SSH as well, but the GUI fails to load. Disabling/enabling the GUI from the CLI is ineffective. I had the identical error as the original poster at the CLI.

Dropping to the command line revealed the problem, /etc/lighttpd.conf was blank. Apparently a full reset isn't totally necessary. In my case the switch is remote and in production. So putting on my old Unix sysadmin hat, I copied the /etc/lighttpd.conf file from another working Netonix (running the same firmware level) into /etc, and all was well. I've made subsequent configuration changes via the GUI to test everything, and 12 hours later everything seems fine. Remember your mileage may vary :)

Had the same issue again with two WS-12-150-DC switches on firmware 1.5.2 today, that came back online after a prolonged power outage (after Storm Eowyn) on a remote site, that isn't easily accessible.

lighttpd.conf file was empty. Repopulated from a known good switch with the same firmware, reboot, all good.
Thanks. Still a bit mad, that this even can happen.

/M

[sirhc]

For what it's worth, I had this happen to one of my Netonix switches this morning. Device working fine, SSH as well, but the GUI fails to load. Disabling/enabling the GUI from the CLI is ineffective. I had the identical error as the original poster at the CLI.

Dropping to the command line revealed the problem, /etc/lighttpd.conf was blank. Apparently a full reset isn't totally necessary. In my case the switch is remote and in production. So putting on my old Unix sysadmin hat, I copied the /etc/lighttpd.conf file from another working Netonix (running the same firmware level) into /etc, and all was well. I've made subsequent configuration changes via the GUI to test everything, and 12 hours later everything seems fine. Remember your mileage may vary :)

Had the same issue again with two WS-12-150-DC switches on firmware 1.5.2 today, that came back online after a prolonged power outage (after Storm Eowyn) on a remote site, that isn't easily accessible.

lighttpd.conf file was empty. Repopulated from a known good switch with the same firmware, reboot, all good.
Thanks. Still a bit mad, that this even can happen.

/M

v1.5.2 ???????


Do you mean v1.5.25 ? If not then upgrade as we are not going to debug issues with really OLD firmware.