Thread Info
  • State Verified Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 15 replies
  • Answers 3 answers
  • Subscribers 8 subscribers
  • Views 49657 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

can not log into Webadmin, REST API disabled

Fred Heller

Hi,

When is start the browser and try to log into https://ip_of_utm:4444/ the UTM responds with: REST API Disabled. Enable in WebAdmin Settings > REST API.

How can i circumvent this? The WebAdmin is not acessible for me anymore.

Is there a possibility to do this from CLI?

 



This thread was automatically locked due to age.
Parents
  • 0

    Same issue here. Had to hard reboot.

    Also if related (not the first time this other issue occurred with Sophos UTM). I had a continuous ping running both to my ISPs gateway and 8.8.8.8, both responding. After hard reboot of Sophos UTM these are showing from my PC Request Timed Out. Other times where the UTM has broken in someway or needed a hard reboot this has also occurred. Does anyone know why? I support a whole heap of other firewalls at work such as Watchguard & Cisco ASAs and I don't see anything like this ever. I have checked the Firewall Live Log and IPS Live Log and nothing being blocked. I had a quick look at the "all logs" type section - do people really expect me to look through like 50 different logs? Like on a Watchguard I open one window and see every single thing being logged, is there not the same thing on Sophos?

  • 0 in reply to Allister Wade

    I found that the issue was a corrupted file system.  I logged in at the console and ran fsck and then rebooted.  I had to repeat this once to clear all the errors.  It's been running fine for several days now.

    If you're going to try this, back up your configuration first, so that worst-case you can re-install from scratch.  I've had issues running FSCK on a mounted root file system in the past.

Reply
  • 0 in reply to Allister Wade

    I found that the issue was a corrupted file system.  I logged in at the console and ran fsck and then rebooted.  I had to repeat this once to clear all the errors.  It's been running fine for several days now.

    If you're going to try this, back up your configuration first, so that worst-case you can re-install from scratch.  I've had issues running FSCK on a mounted root file system in the past.

Children
No Data