Temporary error while accessing Sophos Central, please try again

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! 

One of the four units I was trying to get working I booted back to the 17.3 firmware and still had not luck registering it so it doesn't look like a firmware issue.

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

ooouuh yeah, and that´s one of the great advantages of "cloud cr*p" :)

i like....

Yeah.  Sounds like another pipe dream.  

Paul Jr

Hi guys,

Any solution for this?, i'm doing the Sophos certified engineer course lab and at the point 3.9 need to register Sophos XG to Sophos Central and i experiencing that!!!  

Temporary Error while Accessing Sophos Central.

A workaround, i did intent to register it from the sophos central and not works.... 

I have the lab until the next friday to close the course ...and it presented this issue :/ ....

Hello Folks,

Apologies for the inconvenience. We've found multiple instances where customers were not able to register with Sophos Central. As of now, this has been observed by some customers but no pattern or similarities have been found. I request you to create a case so that our Support team can identify more details on per user basis.

We have the same problem on several XG firewalls. The support instructed us to install firmware update to 17.5 MR7. But now I read in the previous postings that this is not the solution.
With the last updates, our customers were very sad about the things, which were going wrong with every update. Things are getting fixed but in the same sentence a lot of new problems will occure. Many customers say they dont want to upgrade to new versions anymore. Unfortunately one or the other is thinking about changing to another firewall manufacturer.