openVPN not responding after upgrade to 23.05 from 23.01

Draco

I last connected to my OpenVPN servers using the iOS client on my iPhone 13 on May 20. As part of my post-upgrade testing, I just tried again.

No joy. I am not even seeing the initial packets hitting my WAN firewall rule that lets them through the filewall. I've changed nothing except for:

upgrade to 23.05 on SG-5100
Run Update/Reload for pfBlockerNG
Install (but did not enable) UDP Broadcast Relay package (was waiting for testing finished).

I have a fairly complex configuration overall, but VPN is pretty straightforward. 2 RA servers on 2 TUN networks on 2 different ports. I have the latest version of OpenVPN on my iPhone.

I checked the DDNS address and it matches the outside IP for my WAN port.

Any thoughts/ideas?

tman222

Hi @Draco - which version of iOS are you running? Looks like there might be some issues with the OpenVPN app in iOS 16.5:

https://forums.openvpn.net/viewtopic.php?p=111445

Hope this helps.

Draco

@tman222 Yes that does, thanks. I was continuing to test and found I could connect just fine through Windows OpenVPN.

I'll focus on the iOS side of things now.

[UPDATE] - The post you noted has a workaround. That will keep me working until OpenVPN releases a updated iOS client.

Gertjan

@Draco said in openVPN not responding after upgrade to 23.05 from 23.01:

Any thoughts/ideas?

Connect, and look at the logs of the iOS OpenVPN app : nothing ...
Disconnect with the app.

Now, goto Settings, tap the bleu 'VPN' (it should say 'not connected', check that the OpenVPN is checked, and now connect there.
Now it works.

Definitely an iOS OpenVPN app bug.

NeVaR

Did you try disable the openvpn server for couple second and the enable it again? It works for me after upgrade to 23.05. Then I was able to connect on my iOS

Draco

@Gertjan Yup, tried that, both by disabling the servers and saving (then re-enabling) and by restarting from the Services widget on the Dashboard.

If you read through the replies above, you'll see it turns out it is an iOS bug (with a workaround if you are willing to save your pw with the profile).

Draco

@Gertjan Yes, using iOS Settings/VPN to activate is the workaround noted in the article @tman222 pointed me at. OpenVPN says they are working on a fix...