PiVPN configuration not directly usable in SFOS OpenVPN GUI [answered]

"I recommend to write a basic configuration file for your service, and to import that into the Sailfish GUI, if you have to use that GUI."

That is exactly what I did. In SecureFishNet I have to add the Key Password. I couldnt find a similar entry possibility in the GUI.

@dirksche Why does it then use TCP as connection protocol? As I wrote, OpenVPN Jolla style does not allow keys to be protected by a passphrase (yet). But this is the first time I read that a proto udp is not honored by the client.

But I have to admit that I have never used that GUI myself, so I should probably just remove this answer if it is of no help.

I just remembered that there is another PiVPN related question on TJC that contains information on how to remove the passphrase from the key to make it usable in Jolla's CLI. If it's only this that breaks your configuration, this question may be a dupe.

Thank you @Maus for this information. I have no idea why the GUI always try to use TCP. I will try to erase the passphrase, otherwise I will use SerureFishNet.

Hi, are you saying that Settings > VPN > Add new VPN > OpenVPN > Skip > Advanced > Protocol Type has options: Default, UDP and TCP, doesn't work for you?

Does the /var/lib/connman/provider*/settings file contain right OpenVPN.Proto information?

Since SecureFishNet works like a charm I don't care about the native VPN solution. And if, like Maus mentioned, the Gui can't handle passphrase protected key files, it is obsolet for me. But thanks for your comment.