Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 27 subscribers
  • Views 965 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

XG Firewall - rebooted and now get a 503 error when attempting to log in

Susan Bradley

First the firewall wouldn't accept new exclusion rules, so I made it reboot.

When it rebooted I now get a 503 error when attempting to log in.

I am remote to the office and will need to go in and pull the power and force a reboot, but has anyone else seen this?  Firewall appears to be functional as I can remote into the office.

HTTP ERROR 503 Service Unavailable

URI: /webconsole/webpages/login.jsp
STATUS: 503
MESSAGE: Service Unavailable
SERVLET: -

Powered by Jetty:// 9.4.30.v20200611



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

    Hello Susan,

    Thank you for contacting the Sophos Community.

    Adding to what Dirk mentioned, I would recommend you to reach out to Support if you’re unable to access it after the reboot and also if you’re able to restart.

    It might be that the process that handles the service wasn’t up when you tried to start or got stuck, but it might be worthy it for Support to check for any errors that might indicate that the Hard Drive of your device might be failing.

    Feel free to share the Case ID with us, so we can follow up.

    Regards, 

     
    Emmanuel (EmmoSophos)
    Technical Team Lead, Global Community Support
    Sophos Support Videos | Product Documentation  |  @SophosSupport  | Sign up for SMS Alerts
    If a post solves your question use the 'Verify Answer' link.
Reply
  • 0

    Hello Susan,

    Thank you for contacting the Sophos Community.

    Adding to what Dirk mentioned, I would recommend you to reach out to Support if you’re unable to access it after the reboot and also if you’re able to restart.

    It might be that the process that handles the service wasn’t up when you tried to start or got stuck, but it might be worthy it for Support to check for any errors that might indicate that the Hard Drive of your device might be failing.

    Feel free to share the Case ID with us, so we can follow up.

    Regards, 

     
    Emmanuel (EmmoSophos)
    Technical Team Lead, Global Community Support
    Sophos Support Videos | Product Documentation  |  @SophosSupport  | Sign up for SMS Alerts
    If a post solves your question use the 'Verify Answer' link.
Children
No Data
Cookie Information Banner