Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 29 subscribers
  • Views 10431 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

Sophos XG v17 GA device was unresponsive until reboot?

waghelak

Hi,

I could not access my home network using VPN setup in Sophos XG since 9 this morning.

I just got home and realised non of the devices were getting any IP address and Sophos XG was unresponsive.

I have never experienced this issue before and wondering whether upgrading to GA has caused the issues.

Can someone help me identify what further logs i need to check on?

System logs don't help much with no logs after 9 this morning until i rebooted.

I am now worried not knowing what caused it as i am away from home a lot for work purposes and need to access files over the VPN.

Thanks

Edit: I enabled authentication OTP few days ago, wondering that has caused any issues?



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

    Hi,

    Thank you for the feedback.

    Sending you PM to look into the issue.

     

    Regards,

    Deepti

  • 0 in reply to deeptibhavsar

    It appears this has now happened to me too, on an XG210 appliance that was upgraded Monday a week ago.  Device won't respond to pings, no web console access, but strangely enough SSL VPN is still established with another XG (although no traffic flows from the one that is in trouble).  I will try and SSH and see if it the networkd service pegging the CPU.  But anyway I am going to roll back to the 16.5 firmware, can't have a firewall that randomly hangs like this.

Reply
  • 0 in reply to deeptibhavsar

    It appears this has now happened to me too, on an XG210 appliance that was upgraded Monday a week ago.  Device won't respond to pings, no web console access, but strangely enough SSL VPN is still established with another XG (although no traffic flows from the one that is in trouble).  I will try and SSH and see if it the networkd service pegging the CPU.  But anyway I am going to roll back to the 16.5 firmware, can't have a firewall that randomly hangs like this.

Children
No Data