Page 1 of 2
Cannot access GUI
Posted: Mon Nov 05, 2018 6:06 pm
by vanilla
Hi Guys,
I have a 24 port AC switch running 1.5.0
I am unable to access the GUI. I do not even get a login, just ERR_Connection_Refused
Is there a way to restart the HTTP process? I have tried a reload cold and a reboot command, both of which didn't help.
Thank you!
Re: Cannot access GUI
Posted: Mon Nov 05, 2018 6:41 pm
by sirhc
So your able to login to the CLI or console?
Check to make sure you dd not disable the web interface from the CLI.
Use the in line help of the CLI to find where you enable it.
Either that or factory default it and set back up as this is not normal behavior, not sure what you did?
Re: Cannot access GUI
Posted: Tue Nov 06, 2018 3:52 am
by vanilla
We have SSH access. No changes were made, we just went to access it as we added a radio and found the GUI inaccessible.
I will try and power cycle the box before I default it. I was hoping there is a Command line command that would allow me to restart the HTTPS process.
Re: Cannot access GUI
Posted: Tue Nov 06, 2018 3:53 am
by vanilla
Is there a document that lists all the commands in the CLI?
Re: Cannot access GUI
Posted: Tue Nov 06, 2018 3:56 am
by vanilla
If I try the /etc/init.d/lighttpd restart command I get:
1970-01-01 10:56:55: (configfile.c.1390) server.upload-dirs doesn't exist: /var/tmp
1970-01-01 10:56:55: (configfile.c.1404) a default document-root has to be set
1970-01-01 10:56:55: (server.c.888) setting default values failed
Re: Cannot access GUI
Posted: Tue Nov 06, 2018 12:29 pm
by sirhc
The CLI has IN LINE HELP.
Press ? and ENTER anywhere for list of commands.
Modeled after Cisco
I would take out of service and do a power on FACTORY DEFAULT and manually set back up di not export and import config as it may be corrupted
Re: Cannot access GUI
Posted: Wed Feb 06, 2019 7:57 pm
by scott@airgrids.com
Sirhc,
I also just had a switch do this (this week) after a prolonged power failure at a tower. Its back up and seems to be functioning, but I can only access via SSH. Also, I've noticed that the httpd process constantly restarts (as the PID is constantly changing). I can order and replace it, but wondering if there is something else going on to fix it?
Scott
--------------
admin@Adams_Switch:/www# /etc/init.d/lighttpd restart
2019-02-06 16:53:12: (configfile.c.1390) server.upload-dirs doesn't exist: /var/tmp
2019-02-06 16:53:12: (configfile.c.1404) a default document-root has to be set
2019-02-06 16:53:12: (server.c.888) setting default values failed
admin@Adams_Switch:/www# (configfile.c.1390) server.upload-dirs doesn't exist: /var/tmp
Re: Cannot access GUI
Posted: Wed Mar 13, 2019 5:19 am
by alexsmith789
When I was trying to access the GUI then suddenly
lenovo screen flickering started but I tried hard to resolve the problem but could not fix the problem. Please help me to solve this problem as it is really disturbing me.
Re: Cannot access GUI
Posted: Wed Mar 13, 2019 12:55 pm
by sirhc
alexsmith789 wrote:When I was trying to access the GUI then suddenly
lenovo screen flickering started but I tried hard to resolve the problem but could not fix the problem. Please help me to solve this problem as it is really disturbing me.
How is this our issue, our web UI uses a browser and is a web page? Apparently from the link you provided this is a common issues with these laptops?
Did you try using a differnt browser with your Lenovo?
Re: Cannot access GUI
Posted: Mon Mar 18, 2019 1:58 pm
by bdowne01
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 :)