Hello
same issue
We got this since the firmware upgrade to XGS2100 (SFOS 20.0.0 GA-Build222), from SFOS 19.5.3 MR-3-Build652
The file has some other problems too, it now adds the CA two times, and at the beginning the file had before a white space as beginning row.
(There is also a little a white space at end too, after the port number.)
But figuring all this out that the file name is misleading, took a long enough. Before the upgrade we did not had this kind of problem. (Strangely windows has no problem, so this mus be a android thing)
Is this so hard to test your config too on major client for system which you dont support but recommend to use inside the documentation? This is no excuse.
Is there a workaround? At least make some offical topic where you can find this quick ...
Hi Simplified Sam,
Thank you for reaching out to Sophos Community.
We regret to hear about your experience. Would it be possible to create a case for this? The Devs are already aware and are internally tracking under NC-130692(kindly include).
Also, kindly share the case ID for further monitoring, and we can input the additional feedback.
Erick Jan
Global Community Engineer, Support & Services
Are you a Sophos Partner? | Product Documentation | @SophosSupport | Sign up for SMS Alerts
If a post solves your question, please use the 'Verify Answer' button.
The award-winning home for Sophos Support videos! - Visit Sophos Techvids
Hi Simplified Sam , please replace %40 in the .ovpn file with @ symbol and load the file in OpenVPN Connect, it should work. Also multiple CA entries in the .ovpn file is harmless and should not have any functional impact, both the issues are known to us and we are working on the fix.