If you have recreated the connections then the old config files won’t work as the private key for each connection is remade and will be different.
When you create a new connection, even if it is the same as one you had defined and then deleted you need to download the new configuration file for that connection.
Well, I tried with a newly made config file / connection… no go, same as before.
iptom - you were a big help to me earlier. After the new Stable 195 dropped, I moved my ipfire from that listed build (master/baa22ec7) to Stable since I thought it was the same (and have been told that it is indeed the same). However, there is no joy with the Core-Update 195.
But those were not my words ¯\_(ツ)_/¯ 
I specially did a test
I downloaded the CU195 version and installed it on a new virtual machine.
I can confirm the lack of connection to ProtonVPN
After switching to the Repository “Testing” and then using the trick with the file /opt/pakfire/db/core/mine
edit
Don’t give up 
Once again, thank you so much. I will return to the testing (baa) base. I need to work around my household for time to do so. I will report back with any and all news.
Well… It works. There is definitely a difference between the Stable 195 and the Testing 195 (baa) versions with something regarding Wireguard. Again, many thanks to iptom.
The content of the wireguard.cgi file for CU195 stable and CU195testing baa22ec7 is the same.
But I noticed the differences are in the /etc/init.d/wireguard file
I did a test
On a test VM with IPFire CU195 stable, in the /etc/init.d/wireguard file I put the content from the CU195testing baa22ec7 version
Then I did a reboot
The result can be seen below
Regards
There was a patch to remove “fwmarks” but that was included in the release of CU195.
Thanks,
A G
It seems not 
That change was one made in the next repo for CU196 but it looks like it got copied into the master repo but after CU195 was finalised.
https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=8e1a9a3699e7061405ae7ee49caf672558a1c792
That change will get officially into CU196.
Well, now it’s all clear
Thank you for checking , confirming , clarifying
Regards
Thanks for clarifying Adolf!
A mystery solved - nice.
Thanks for making that clear. It would be helpful to attached the correct file for /etc/init.d/wireguard — rather than go through the process of installing the test version, copy it there, reinstall the stable version, and install it again. Hint.
@ag
There is a new error when importing the ProtonVPN configuration file.
AllowedIPs = 0.0.0.0/0, ::/0
After deleting , ::/0 imports without error.
IPFire 2.29 (x86_64) - Core-Update 196 Development Build: master/4a12f983
IPFire 2.29 (x86_64) - Core-Update 196 Development Build: master/1f200cb1
Regards
So the ProtonVPN configuration file is allowing all IPv4 and all IPv6 IP’s but the IPFire WireGuard implementation is only for IPv4 so it doesn’t understand the IPv6 element.
It is likely that during our earlier tests this range in ProtonVPN files was not there so the error did not show up.
Is anyone able to test this, please?
I will later today
Thanks,
A G
