New Sophos Support Phone Numbers in Effect July 1st, 2023

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

Configuration gone after upgrage SFOS 19.0.0 to 19.0.1

Hello everybody,

yesterday I updated two Firewalls (XGS 126 and XG 125) from Version 19.0.0 to 19.0.1. After the upgrade both Firewalls has SFOS 19.0.1 firmware installed but lost their configuration. The problem was both firewalls are on remote site and lost all external connections (Sophos Central und VPN), so I can't reach the firewalls. Today we connect on site via serial console to the Firewalls, and I saw that Firmware 19.0.1 was installed, but (at minimum) the network configuration was gone. I made some tests:

- Booting the 19.0.0 Firmware the Firewall runs as expected. 

- Booting the 19.0.1 Firmware via Bootloader or via WebAdmin Firewall has no configuration.

On the other hand, I made the upgrade on serval firewalls without any problem (2x XG 125, 1x XGS 5500 HA, a Virtual and a Software Firewall). 

How can I remove the 19.0.1 Firmware from the non-working firewalls to get a 2nd try to upload the firmware again and install the 19.0.1?



This thread was automatically locked due to age.
  • Thank you all for reporting this issue. 

    We have confirmed this is a bug, and we'll fix it in an upcoming new build for v19.0 MR1.

    This issue affects devices which has 'set vpn conn-remove-on-failover non-tcp' executed on the backend prior to the upgrade to MR1. Unfortunately the migration to MR1 does not handle this case properly, and would fall back to factory default settings. 

    If you cannot wait for the new MR1 build, and need to upgrade to MR1 right away, you can: 

    Log into Advanced shell in the CLI

    Execute psql -U nobody -d corporate -Atc "DELETE FROM tblclientservices WHERE servicekey = 'vpn_flush_conn_failover'

    Upgrade to MR1 as normal through UI

    After upgrading to MR1, you do not need to re-run 'set vpn conn-remove-on-failover non-tcp' as this parameter is already set to non-tcp by default in MR1. 

  • Hi!
    I tried to update my Sophos XG to SFOS 19.0.1 MR-1-Build365 and still config error. Is tere a plan to release proper update in near future?



  • V19.0 MR1 build 365 resolves the issue described above, and we have had no further report of migration issues. 

    can you describe the error/issue you’re seeing? What version are you upgrading from? 

  • Hello,

    I have partial the same issue. I came fron the latest 18.5 version and after the upgrade only the first two interfaces (from 4) came up. After I connected to the first interface with the standard Ip I saw that the other 2 ports are not anymore configured and it is disabled. Also the rules are gone.

    If you need more Information, ask me.

    Regards Kay-Uwe

  • What was the version of v18.5 you upgraded from? Did you upgrade directly to v19.0 MR1 build 365? Did all configuration disappear from your system (i.e. it got factory reset)? 

    Is there a support case open for this, if so what's the ID? 

Reply Children
  • It was the 18.5.4 Mr4 418. The config gone except the login data and the Rule Group.

    There is no support case opened, because it is the "home" version.

  • What version did you upgrade to? 


  • If you encounter the same issue as above, all of your config would be reset, not just some. Is it possible for you to enable remote support access, so we can log in and take a look at your device? 

    PM me the support access ID once you have it enabled. 


  • But at the moment I am back at version 18.5. So do you need still access or if I upgraded to  19?


  •  Do you have Sophos XG or XGS Series Appliances with HA or without HA? or do you have virtual with HA or without HA?

    "Sophos Partner: Infrassist Technologies Pvt Ltd".

    If a post solves your question please use the 'Verify Answer' button.

  • I have no Sophos Hardware and at the moment no HA.

  • Seems the issue is related to your hardware compatibility where Sophos XG is installed or some advanced setting is not enabled on the same hardware to run v19.0.

    Please share the output you have checked for the below command here from SSH option 5>3 :     
    # grep SSSE3 /var/log/sasi.log
    # grep flags -m1 /proc/cpuinfo

    "Sophos Partner: Infrassist Technologies Pvt Ltd".

    If a post solves your question please use the 'Verify Answer' button.

  • Hello,
    for the sasi.log there are no entry for SSSE3. The sasi.log path on my installation is /log/sasi.log.

    For the second command:

    flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid rdseed adx smap intel_pt xsaveopt dtherm ida arat pln pts

  • Hope you took backup from 18.5.4 Mr4 418 before upgrading the firmware to 19.0.1 MR-1-Build365?

    Please Go to System-->Admininstration --->Backup and Firmware -->Firmware and share the status of the firmware shown on GUI

    As there is a trick if you upgrade from 18.5.4 Mr4 418--> 19.0.0 then to 19.0.1-365 

    It would be great if you raise a ticket with Sophos Support Team as well.


    "Sophos Partner: Infrassist Technologies Pvt Ltd".

    If a post solves your question please use the 'Verify Answer' button.