Temporary error while accessing Sophos Central, please try again

Hi Big_Buck 

Could you please confirm if you are still receiving this error? It might be possible that it was just a temporary timeout error. I have just checked and can access Sophos central dashboard. You can also check the status of Sophos Central service updates here. 

I ran into this issue last night trying to re-connect to a firewall in Sophos Central, it occurred right after I upgraded to the most recent firmware - SFOS 17.5.7 MR-7 (everything was fine before) - I was on 17.5.4 MR-4-1 previously. After quite a bit of trying, and thinking it might be a late night maintenance window issue, I attempted this morning to find it was still going on. I would roll back to my previous firmware to determine if this would fix it, but my customers are in production. I hope this helps.

Thanks!

I've opened a ticket on the issue with support and have given them additional details. It appears to have happened immediately after my attempt to update the firmware to the latest version, and that (initial?) attempt either failed or the OS wouldn't load, so after the install the system loaded the old OS. I then told it to load the new OS - which was listed but not active. Upon reboot and activation of the new OS (17.5.7 MR-7) - that's when I lost Central access. I also noticed two services were reported as STOPPED on the main screen - heartbeat & enhancedappctrl. I attempted with support to start these services using SSH & "service heartbeat:restart -ds nosync" and "service enhancedappctrl:restart -ds nosync" - and received errors both times - "250 Unregistered". Support said this was because the device was not registered - I believe these were running already with registration and just stopped when I lost registration and are not causal.

I attempted a reboot and no dice.

I was going to boot my old firmware but realized my APs have been upgraded to a firmware that requires(?) this new firmware.

Therefore I'm going to have to rollback everything. I've downloaded the AP pattern, but I've never attempted a manual firmware on these devices and have no experience with success/failure rate of that transaction, can't really afford the failure on this gig.

Can anyone test a rollback to previous firmware to see if that resolves their issue and/or comment on whether I should be good to go with the rollback to a more compatible AP firmware before rolling back the FW firmware myself?

Cheers! 

As far as I am concerned, I received a replacement XG210 rev3 from Sophos.  I upgraded that unit from an uploaded firmware file I already have downloaded.  And not from the appliance's GUI.  I un-registered the blown-up appliance.  Next logical step was to register the replacement one.

I could not register from Sophos Central using the serial number either.

Paul Jr

I forgot to mention that on Sophos Central, "System Load" is "Unknown" for all remaining firewalls.  "Model" is blank.

Paul Jr

I forgot to mention that on Sophos Central, "System Load" is "Unknown" for all remaining firewalls.  "Model" is blank.

Paul Jr