Can log in by CLI, but not GUI

Richard,

when you try to access the Web Interface, what erro do you have? The page is not displayed?

Luk

Sorry, meant to post something sooner to say what the situation was, but it's been a long couple of days and it slipped my mind.

Apparently there is a bug in the HTTP patch where it can't be applied to MR1.1 systems. That's what caused the issue.

What I was getting was cli access, but the gui login page displayed, but kept on saying login denied when entering the credentials.

Try to reset the credential from CLI using option 2 and then 1.

Luk

I'm actually having the same problem, it worked fine yesterday from both CLI and GUI but today logging in to the GUI I get Login Failed. I tried resetting the default admin password several times and while the new password works for the CLI I still get Login Failed in the GUI. I'm using IE 11, Edge, and Chrome, all have the same problem.

I'm actually having the same problem, it worked fine yesterday from both CLI and GUI but today logging in to the GUI I get Login Failed. I tried resetting the default admin password several times and while the new password works for the CLI I still get Login Failed in the GUI. I'm using IE 11, Edge, and Chrome, all have the same problem.

Pete, this is very strange. Maybe you locked you out using a policy rule or wrong device access.

Type the following command from console:

system appliance_access enable

and then try to access the XG via GUI.

If it works, check device access and reset the password from GUi then reboot.

My issue was caused by running the HTTP proxy patch whilst running MR1.1. They are not compatible at the moment. The way round it was to boot the standard firmware from the cli whilst connected using a serial lead.

All system appliance_access enable seemed to do was shut down all traffic on my WAN interface without warning :( (thankfully a reboot fixed that), still not able to log into the GUI. I don't have any patches installed that i'm aware of, I just set this up yesterday and set up a few port forward rules so far, and those appear to all still be working.

Pete,

try this:

https://community.sophos.com/products/xg-firewall/f/136/p/75462/290380#290380

See if resetting the password using the SF loader does the trick.

No luck with that way either. It changed the password for the local console back to admin but still get Login Failed on the web GUI.

Ok, this is strange. On a whim I decided to shut it down completely and cold boot and now I can log back into the GUI with the default password. I changed it and the new password is working now - for now.

Ok, now after sitting all night I can't log in again. I tried resetting the password through the console and the SF loader, still can't log into the GUI this time. The first time I reset via SF loader I couldn't even log into the local console, I had to reboot it and reset the password again before it took. Very frustrating, i'm looking into other options for my firewall needs at this point because I don't know if I can trust this one even if I get the GUI working again.

Really strange behaviour Pete.

Is your clock synchronized correctl? Does the BIOS keep the configuration?

Try to reinstall the XG from scratch without importing the config and see how is going then import the config and test again.

It working with me but should reboot appliance after apply this command

and for Cyberoam I use this command line

cyberoam appliance_access enable

I have been having a similar issue. However, it might be that nothing more than patience is required.  After booting the sophos, the device CONSOLE/CLI is available pretty much immediately.  Some minutes later, the services start working and network connected devices can then access the internet. It is LATER STILL before the webgui goes live. And depending on your CPU (mine is an Atom D525) then this delay can be well over 5 minutes.  So, you can have the impression that the webgui is faulty/not working (giving dead pages) whereas the CLI is working, however, before you waste a lot of time trying to solve something that isn't actually broken, just go and have a coffee, come back 10 minutes later, and see if it is working.  This is very frustrating, because when you set up a sophos device, you want to access through the webgui, but it takes a very long time before it becomes responsive.

? Is there a setting somewhere so that the webgui boots earlier?