OpenVPN isn't working after the update "IPFire 2.29 - Core Update 183"

[casabenedetti (Carlo)]

Hello,
I have a big problem. After updating to ‘IPFire 2.29 - Core Update 183,’ I receive the following error message when I connect to OpenVPN remotely with Android. I’m not sure how long I’ve been dealing with this issue. I just noticed it now and would like to know if it’s a bug in the latest version of IPFire. Everything was working fine last time.
Has anyone else experienced the same issue?
Thank you as always.

[sec-con]

I think it sadly may be related to this.

Vpn host-certifikat

There is a bug in Core Update 183 regarding the openssl commands for creating a new root/host x509 certificate set. This was due to an OpenSSL bug fix that was implemented in version 3.2.0 There have already been a couple of posts on this topic in the forum. Please see the bug report https://bugzilla.ipfire.org/show_bug.cgi?id=13595 for more details. A patch to fix this has been submitted and will hopefully get into Core Update 184.

Seems there is a bug

[casabenedetti (Carlo)]

I sincerely thank you for the report. I strongly suspected it was a bug. So I will wait for the next update and follow the reported post. Good continuation.

[bonnietwin (Adolf Belka)]

@sec-con

I think it sadly may be related to this.

No it is not related to that bug. That bug only occurs if you are creating a new x509 root/host certificate set for the OpenVPN Server in CU183, ie a first install of OpenVPN or the wiping away of all existing client connection certificates and the existing x509 root/host certificate set.

The image shown is for a client and it does not like some of the options provided in the .ovpn. Those have been present for a long time.

There have been some other posts about openvpn clients of a certain newer version no longer liking the auth-token and/or the auth-token-user entries. Have a search through for them.

These are used for the OTP option if that has been selected.

If you are not using OTP then try remove\ing those auth-token* entries from your clients .ovpn file.

[casabenedetti (Carlo)]

@bonnietwin

If you are not using OTP then try remove\ing those auth-token* entries from your clients .ovpn file.

I’ll try it right away and update you…

[casabenedetti (Carlo)]

Yes. These were the cause of the problem, I commented on them:
;auth-token-user USER
;auth-token TOTP
Thanks for the valuable suggestion!!!

[sec-con]

I apologize for having mislead you, glad you was able to figure it out.

[casabenedetti (Carlo)]

But no, there is no reason to apologize: we had the same ideas. I had the problems after the upgrade. We couldn’t possibly think it was a client-side problem.

[sec-con]

I am pretty sure I somehow triggered this VPN bug, the last few days I have been reading up on how to finally create a VPN, so I am sure them “higher-ups” felt it was not a good time for me to do that…