Version 3.4 breaks config (option_error: sorry, unsupported options present in configuration: UNKNOWN/UNSUPPORTED OPTION

[MavhRik]

Hi,

We're thinking on switching from Sophos Connect client tot OpenVPN client (because of uniformity beteen (i)OS and supporting multiple profiles with same endpoint without overwriting).

Had 3.3.7 installed, imported config from Sophos firewall and was able to connect.
Colleague installed it to today, but since 3.4 was released yesterday he got that version...

When enabling the config this error appears:
option_error: sorry, unsupported options present in configuration: UNKNOWN/UNSUPPORTED OPTIONS



When I upgrade to this version (manual, app does not discover the new version yet (assume this is intentional)) I get the same error.

[openvpn_inc]

Hello MavhRik,

This is intended in OpenVPN Core 3.8 that comes with OpenVPN Connect 3.4. There are certain options that should not be used that are still being used by people. You should look in the log which options those are and then try removing them from the config or solving the underlying problem.

If you can look in the logs please and find those and fix those issues, the connection should be able to proceed normally again.

Kind regards,
Johan

[MavhRik]

Hello MavhRik,

This is intended in OpenVPN Core 3.8 that comes with OpenVPN Connect 3.4. There are certain options that should not be used that are still being used by people. You should look in the log which options those are and then try removing them from the config or solving the underlying problem.

If you can look in the logs please and find those and fix those issues, the connection should be able to proceed normally again.

Kind regards,
Johan

//edit

Sorry, I think I wasen't awake (enough) yet...
Will look into it.

[curtsen]

I having the same issue
but the log file dosent give much info
i'm using a synology as VPN server

[Jul 12, 2023, 09:22:05] OpenVPN core 3.8connect1 win x86_64 64-bit OVPN-DCO built on Jun 26 2023 16:08:41
⏎[Jul 12, 2023, 09:22:05] Frame=512/2112/512 mssfix-ctrl=1250
⏎[Jul 12, 2023, 09:22:05] NOTE: This configuration contains options that were not used:
⏎[Jul 12, 2023, 09:22:05] UNKNOWN/UNSUPPORTED OPTIONS
⏎[Jul 12, 2023, 09:22:05] 3 [pull]

[MavhRik]

I having the same issue
but the log file dosent give much info
i'm using a synology as VPN server

[Jul 12, 2023, 09:22:05] OpenVPN core 3.8connect1 win x86_64 64-bit OVPN-DCO built on Jun 26 2023 16:08:41
⏎[Jul 12, 2023, 09:22:05] Frame=512/2112/512 mssfix-ctrl=1250
⏎[Jul 12, 2023, 09:22:05] NOTE: This configuration contains options that were not used:
⏎[Jul 12, 2023, 09:22:05] UNKNOWN/UNSUPPORTED OPTIONS
⏎[Jul 12, 2023, 09:22:05] 3 [pull]

In your .ovpn file look for the line 3 pull and remove it, should work again.

[TheGreatbeesbal]

Hi

Also have the same issue, went through the log file and removed the options it complained about but still the issue continues.

[MavhRik]

Hi

Also have the same issue, went through the log file and removed the options it complained about but still the issue continues.

Did you remove and reimport your .ovpn after editing it?

[TheGreatbeesbal]

HI

Yes config file was reimported

[TheGreatbeesbal]

just to add if i test the same config with sophosconnect/forticlient and tunnelblick it works without any issues.

[RoiDesPerdants]

Hello,

Thx it work for me, i juste putted an # before the pull -> #pull.

And i deleted the profil, reimported the file .ovpn, recreated the profil and it worked.

Bye !

[SumanL]

removing the line that openvpn complained for, did the trick.
for me "ncp-disable" was complaining so removed from the .ovpn file.

Code: Select all

dev tun
persist-tun
persist-key
ncp-disable -removed this line
cipher AES-256-CBC
auth SHA256
tls-client
client

[openvpn_inc]

just to add if i test the same config with sophosconnect/forticlient and tunnelblick it works without any issues.

That can be explained because your profile is almost certainly still containing things that do not belong there or could be causing issues for you now or later, but those clients use OpenVPN2 and currently may be ignoring those options. I would not see this as a solution but as kind of ignoring the problem and working around it. You're of course welcome to do this, if you're happy with doing that, but I would advise instead to take a look at the log output that tells you what's wrong and try to fix it. If you are handed such a config that triggers this from a server administrator they might want to be made aware of this to try and solve things.

Kind regards,
Johan

[saengerp]

Hello OpenVPN Community,

we faced the same issues after updating to Version 3.4.
The most problems we are facing are connected to Sophos UTM Appliances.

In the OpenVPN Logs:

[Jul 14, 2023, 08:28:29] NOTE: This configuration contains options that were not used:
⏎[Jul 14, 2023, 08:28:29] Unsupported option (ignored)
⏎[Jul 14, 2023, 08:28:29] 0 [ip-win32] [dynamic]
⏎[Jul 14, 2023, 08:28:29] 7 [resolv-retry] [infinite]
⏎[Jul 14, 2023, 08:28:29] 9 [persist-key]
⏎[Jul 14, 2023, 08:28:29] 10 [persist-tun]
⏎[Jul 14, 2023, 08:28:29] UNKNOWN/UNSUPPORTED OPTIONS
⏎[Jul 14, 2023, 08:28:29] 15 [route-delay] [4]

After editing the .ovpn config and deleting the entry for "route-delay 4", the configs started to function again.

After some research it seems to be an automatic config from the sophos UTM ovpn template itself, that can be changed via ssh.
The problem is, that after every update on the appliance, the config needs to be changed manually again.

Here is a community thread regarding this topic:
https://community.sophos.com/utm-firewa ... by-updates

Hope this helps somebody.

Kind Regards
PS

[Marky_Shark_]

Hi everyone!

I'm sadly also facing the same issue on my laptop after updating the client to 3.4
My issue is that, i'm not so tech savy and have no clue how to fix the issue. I downloaded a new upload file from surfshark, but it shows up the same error.

Is there a manual or any reccomendations on how to fix this issue?

Thank you.

[lean2l]

@Marky_Skark_
When you get the error message, click cancel. Then you can click the symbol in the upper right corner (it depicts like a scripture or stuff, sorry, I'm not a native English speaker). This opens the logs and in the very last line there should be a word or command in [ ]-brackets.
Then you can right-click the .ovpn-profile with notepad on your computer. It opens a text file. Look for the word you found in those brackets in the last step. Delete it, save the file and import it into OpenVPN Connect again and you should be finde!

[Marky_Shark_]

Hi @lean2l
Sadly it doesn't help
After saving the file, it keeps giving other words in the Log. Deleted 3 diffenret words, and it still won't budge

[Marky_Shark_]

[Jul 14, 2023, 15:24:31] OpenVPN core 3.8connect1 win x86_64 64-bit OVPN-DCO built on Jun 26 2023 16:08:41
⏎[Jul 14, 2023, 15:24:31] Frame=512/2112/512 mssfix-ctrl=1250
⏎[Jul 14, 2023, 15:24:31] NOTE: This configuration contains options that were not used:
⏎[Jul 14, 2023, 15:24:31] Unsupported option (ignored)
⏎[Jul 14, 2023, 15:24:31] 4 [resolv-retry] [infinite]
⏎[Jul 14, 2023, 15:24:31] 10 [persist-key]
⏎[Jul 14, 2023, 15:24:31] 11 [persist-tun]
⏎[Jul 14, 2023, 15:24:31] UNKNOWN/UNSUPPORTED OPTIONS
⏎[Jul 14, 2023, 15:24:31] 8 [tun-mtu-extra] [32]
⏎[Jul 14, 2023, 15:24:31] 14 [ping-timer-rem]
⏎[Jul 14, 2023, 15:24:31] 19 [pull]
⏎

[Junkie2k]

Hello there,

@Marky_Shark_
I just fixed this problem. Open your .opvn file and remove lines 9 "tun-mtu-extra 32", line 15 "ing-timer-rem" (my log file also says line 14, but it's line 15...), line 24 "pull" and save the file. Then delete profile and create a new one with changed .opvn file and it should work again!

[KisukeCZE]

For me these options generates error:
ping-timer-rem
pull

But after removing them connection just does not work...

[openvpn_inc]

For me these options generates error:
ping-timer-rem
pull

But after removing them connection just does not work...

Would be good to post the log that shows the connection problem. It may be that it won't work because of some other things like not being able to reach the server due to firewall or such.

Kind regards,
Johan