Scheduled maintenance on Saturday, August 8th from 7am to 10am (UTC). Licensing registrations and key activations will be unavailable during this period. More info here.
We'd love to hear about it! Click here to go to the product suggestion community
when i try to configure the Sophos Connect feature i´m unable to enable it since i´m getting the error message:
Sophos Connect CLient could not be updated
What is this all about?
It is not clear to me where are you seeing this error? Please clarify.
In reply to rmk_2018:
i see this error when i´m enabling Sophos Connect via VPN-->Sophos Connect Client after i hit the Apply button.
In reply to Simon-Timothy Folaji:
Please check if there is any box (configuration item) on that page that is incorrect. Normally it should be highlighted. For example one thing I can think is the Name which has characters that are not allowed.
If everything is good above, then since you are setting up this policy for the first time try to Reset that policy and then reconfigure it. See if that works.
Please let us know the results.
a quick update: I´m using SSLVPN which i find more convenient. Thanks for the help.
Thank you Simon for the feedback. Can you please let me know what is more convenient with SSLVPN which you do not get with Sophos Connect? This way we can improve on things that will help the customers who are using Sophos Connect.
i´ve given up because i´m unable to resolve the above error msg that the FW gave me. The setup of SSLVPN is well documented and worked hassle free. That´s why i chose the latter.
We have just released Sophos Connect 1.3 and also SFOS 17.5 MR6 is released. Do you think you will be able to upgrade and try to use Sophos Connect? For the Sophos Connect Client policy you can Reset just this policy and see if that resolves the problem you had with MR3. Just a thought.
i try MR6 when there is an update windows for the FWs.
Thanks for the reply.
I have this error as well on the latest version of Sophos XG Firewall (SFOS 17.5.9 MR-9). And the only reason I can think of is because I'm running the firewall as a transparent bridge.
I don't appear to have an issue at least configuring SSL VPN - I've not tried to connect yet since I have a different firewall out in front at the moment.