OpenVPN in 23.1.7_3

Started by Carve7447, May 06, 2023, 11:17:12 AM

Previous topic - Next topic
Since the last update I lost functionality with OpenVPN. I get the following error message:    

Error   openvpn_client1   write UDPv4: No route to host (fd=7,code=65)

Before the update (23.1.6) everything was working fine. Does anyone have the same problem or maybe a resolution?

Thanks!

Hi,I have the same problem. I try to get 2 vpn server under openvpn to happen and make a loadbalance between them, but I get together error like you.

May 06, 2023, 06:59:57 PM #2 Last Edit: May 06, 2023, 07:02:29 PM by benyamin
I'm not seeing this with the few client instances I run. Perhaps it's a server instance only issue?

Is it fair to say it's more likely a generic networking issue? ¯\_(ツ)_/¯

I am only runnig one VPN client and no server, so I think (at least for me) it's not a server issue.

@Carve7447: very quick reply there. I added a comment in my post...

Can you ping the remote server or probe it's listening port from OPNsense?

@Carve7447, I'm not sure of your expertise, so you can find relevant diagnostics in the GUI under Interfaces: Diagnostics.

If your remote server is listening on a UDP port, you will likely need to use nc from a shell instead.

May 06, 2023, 07:26:25 PM #6 Last Edit: May 06, 2023, 07:33:32 PM by Carve7447
I tried to ping the IP from the host, but it didn't work:

ping: sendto: No route to host

For other hosts it worked. So I tried to ping an IP of a different VPN-Server and it worked. So I am just using this server now (OpenVPN worked with this other server). It seems probable that this single server just doesn't work.

But it's very strange that it worked before the update and the website of the VPN provider says that the server is up and running.

But, as I said, I will just use the other server now. Thank you!

Edit: I found the problem now. The IP of the VPN was put on a blocklist in Unbound. That's why it behaved so strangely.

There you go! Glad you got it sorted.  :)