IPSEC Remote Access .scx file invalid

Hi Craig Glaser: Based on provided error it seems it is getting matched with a known issue NC-85383 and fixed for the same has been taken in V18.5 MR-4 and V19.0.1 MR-1. This is mostly getting observed when cert or cert chain is containing german umlaut characters and translation of same details fetching in SCX is creating a problem.

Hi Craig Glaser: Based on provided error it seems it is getting matched with a known issue NC-85383 and fixed for the same has been taken in V18.5 MR-4 and V19.0.1 MR-1. This is mostly getting observed when cert or cert chain is containing german umlaut characters and translation of same details fetching in SCX is creating a problem.

When will the fix be pushed to the GA/stable channel?

Hi Michael Sugar III As per the info in my last comment fix for the above ID taken in version V18.5 MR-4 and V19.0.1 MR-1. So once this firmware is released, upgrading to those versions will fix the error.

Hello,

i have the same problem. When i try to import the .scx or .tgb file into sophos connect there comes "Connection could not be parsed". When i open the .scx file in editor i see "cannot open file /tmp/root_cert.txt at /scripts/vpn/ipsec/generateJSONVPNClientConf.pl line 331."

I try everything to fix these issue. ApplianceCertificate (used for local cert in ipsec vpn config) and remote certificate (localy signied from xg) has no german umlaut characters or spaces. 

Is there any workaround in the mean time? I am on 19.0.0 GA-Build317 and I've heard 19.0.1 won't be released until the end of July.

Hi,
I have the same problem.
Updating to SFOS 19.0.1 MR-1-Build350 did not help.
Trying to create a new local certificate and remote certificate didn't change anything either.
When exporting the VPN configuration, there is still an error in client_ipsec.tgb:
......
-----END CERTIFICATE-----

[client_ipsec-Public-RootCA-Key]
unable to load certificate
4154918656:error:0909006C:PEM routines:get_name:no start line:crypto/pem/pem_lib.c:745:Expecting: TRUSTED CERTIFICATE

[client_ipsec-secret-client-key]
-----BEGIN RSA PRIVATE KEY-----
...

and in the client_ipsec.scx:
cannot open file /tmp/root_cert.txt at /scripts/vpn/ipsec/generateJSONVPNClientConf.pl line 331.

Hi Holger Krieg1 In recent cases it has been observed that apart from german umlaut characters "Spaces in the cert" also creates a problem and results in the above error. The Fix will be included in the SFOS v19.0MR2 release and the ID is NC-95633.

Hi,
I fixed the problem.
It is the space in the company name in the default certificate.