Important note about SSL VPN compatibility for 20.0 MR1 with EoL SFOS versions and UTM9 OS. Learn more in the release notes.

Thread Info
  • State Suggested Answer
  • Replies 8 replies
  • Answers 1 answer
  • Subscribers 40 subscribers
  • Views 1999 views
  • Users 0 members are here
Options
Suggested

Sophos Firewall default Certificate Problem new deployment

Gerd Rehders1

Hi,

I'm facing a new issue:
After deploying new Firewall the fresh instance cannot be synchronized with Central.
Device keeps hanging on state connected

The default certificate seems to be invalid (Namibia???)
After editing the default authority and regenerating the appliance certificate everything works.
Tested with:
Sophos7: SFOS 20.0.0 (Update mandatory during setup) Problem occurred
Sophos8: SFOS 20.0.2 (new image) Problem did not occur, but certificate is also Namibia???



Added v20.0 MR2 TAG
[edited by: Erick Jan at 2:12 AM (GMT -7) on 17 Oct 2024]
Parents Reply Children
  • 0 in reply to LuCar Toni

    I have set up this firewall virtually (Hyper-V) for test purposes to simulate the error.
    But also as software on our hardware (there is a new USB problem with 20.0.2, which I will report separately).

    Yes, claimed in central

    The following steps helped:
    - Editing the default certificate authority
    - Regenerating the default certificate
    - Moving the firewall to a new group in Central
    - Then move the firewall to the group with our default template.

    After this steps it worked

Unfiltered HTML