What's new

OpenVPN Synology Server Poll Time out

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Windsbee

Occasional Visitor
So I followed this guide to the T: https://www.wundertech.net/synology-nas-openvpn-server-setup-configuration/

As well as watched the video, and 2 others just like it, several times over.

After all is said and done on step 6, I email the config file to my iPhone, put it into the app, and after loading for about a minute I get ''There was an error attempting to connect to the selected server.''

It works just fine when I'm on my home network, just not on my cell network.

The log the first couple of times said:

''Connecting to (My Synology's static IP adress):1194 (My Synology's static IP adress) via UDPv4''

''Can't assign requested adress''

Okay..

After a phone reboot, the log now says: (See below)

So I tried hotspotting an Android phone to my PC, and putting the config file into the OpenVPN desktop app there, and got the same problem - ''Server poll timeout, trying next remote entry...''

Again, works fine on WiFi, just not on any other network.

I've spent 3 days on this. Anyone got any ideas?

Code:
2022-02-27 20:09:45 1

2022-02-27 20:09:45 ----- OpenVPN Start -----
OpenVPN core 3.git::58b92569 ios arm64 64-bit

2022-02-27 20:09:45 OpenVPN core 3.git::58b92569 ios arm64 64-bit

2022-02-27 20:09:45 Frame=512/2048/512 mssfix-ctrl=1250

2022-02-27 20:09:45 UNUSED OPTIONS
1 [tls-client]
3 [pull]
5 [script-security] [2]

2022-02-27 20:09:45 EVENT: RESOLVE

2022-02-27 20:09:45 Contacting [192.168.1.250]:1194/UDP via UDP

2022-02-27 20:09:45 EVENT: WAIT

2022-02-27 20:09:45 Connecting to [192.168.1.250]:1194 (192.168.1.250) via UDPv4

2022-02-27 20:09:55 Server poll timeout, trying next remote entry...

2022-02-27 20:09:55 EVENT: RECONNECTING

2022-02-27 20:09:55 EVENT: RESOLVE

2022-02-27 20:09:55 Contacting [192.168.1.250]:1194/UDP via UDP

2022-02-27 20:09:55 EVENT: WAIT

2022-02-27 20:09:55 Connecting to [192.168.1.250]:1194 (192.168.1.250) via UDPv4

2022-02-27 20:10:06 Server poll timeout, trying next remote entry...

2022-02-27 20:10:06 EVENT: RECONNECTING

2022-02-27 20:10:06 EVENT: RESOLVE

2022-02-27 20:10:06 Contacting [192.168.1.250]:1194/UDP via UDP

2022-02-27 20:10:06 EVENT: WAIT

2022-02-27 20:10:06 Connecting to [192.168.1.250]:1194 (192.168.1.250) via UDPv4

2022-02-27 20:10:16 Server poll timeout, trying next remote entry...

2022-02-27 20:10:16 EVENT: RECONNECTING

2022-02-27 20:10:16 EVENT: RESOLVE

2022-02-27 20:10:16 Contacting [192.168.1.250]:1194/UDP via UDP

2022-02-27 20:10:16 EVENT: WAIT

2022-02-27 20:10:16 Connecting to [192.168.1.250]:1194 (192.168.1.250) via UDPv4

2022-02-27 20:10:27 Server poll timeout, trying next remote entry...

2022-02-27 20:10:27 EVENT: RECONNECTING

2022-02-27 20:10:27 EVENT: RESOLVE

2022-02-27 20:10:27 Contacting [192.168.1.250]:1194/UDP via UDP

2022-02-27 20:10:27 EVENT: WAIT

2022-02-27 20:10:27 Connecting to [192.168.1.250]:1194 (192.168.1.250) via UDPv4

2022-02-27 20:10:37 Server poll timeout, trying next remote entry...

2022-02-27 20:10:37 EVENT: RECONNECTING

2022-02-27 20:10:37 EVENT: RESOLVE

2022-02-27 20:10:37 Contacting [192.168.1.250]:1194/UDP via UDP

2022-02-27 20:10:37 EVENT: WAIT

2022-02-27 20:10:37 Connecting to [192.168.1.250]:1194 (192.168.1.250) via UDPv4

2022-02-27 20:10:45 EVENT: CONNECTION_TIMEOUT [ERR]

2022-02-27 20:10:45 Raw stats on disconnect:
  BYTES_OUT : 812
  PACKETS_OUT : 58
  CONNECTION_TIMEOUT : 1
  N_RECONNECT : 5

2022-02-27 20:10:45 Performance stats on disconnect:
  CPU usage (microseconds): 119945
  Network bytes per CPU second: 6769
  Tunnel bytes per CPU second: 0

2022-02-27 20:10:45 EVENT: DISCONNECTED

2022-02-27 20:10:45 Raw stats on disconnect:
  BYTES_OUT : 812
  PACKETS_OUT : 58
  CONNECTION_TIMEOUT : 1
  N_RECONNECT : 5

2022-02-27 20:10:45 Performance stats on disconnect:
  CPU usage (microseconds): 139994
  Network bytes per CPU second: 5800
  Tunnel bytes per CPU second: 0 [/CODE
 
I don't know if there's anything less meaningful than trying to access your OpenVPN server over wifi (which I assume means you're on the same LAN as the OpenVPN server itself). The VPN changes the routing tables for both the client and server. And if the both are sharing the same IP network, ambiguous routing is usually the result. If you're lucky, it may appear to work in the sense it gets connected, but the actual routing remains local. If you're unlucky, you won't even get connected.

The *only* valid connection to your OpenVPN server is when the client and server do NOT share the same IP network between them. That's why the only meaningful test when the internet lies between the client and server. Anything else is a waste of time and will either NOT work or produce misleading results.
 
I don't know if there's anything less meaningful than trying to access your OpenVPN server over wifi (which I assume means you're on the same LAN as the OpenVPN server itself). The VPN changes the routing tables for both the client and server. And if the both are sharing the same IP network, ambiguous routing is usually the result. If you're lucky, it may appear to work in the sense it gets connected, but the actual routing remains local. If you're unlucky, you won't even get connected.

The *only* valid connection to your OpenVPN server is when the client and server do NOT share the same IP network between them. That's why the only meaningful test when the internet lies between the client and server. Anything else is a waste of time and will either NOT work or produce misleading results.
Yeah this is my first attempt at anything VPN related and I just bought this NAS a week ago so I’m a beginner for sure. I just mentioned that it works over WiFi as me simply trying to fill in more details. The point here is to be able to connect to the server when outside the home network. Considering I’ve followed the linked guide, any ideas why I’m having problems?
 
2022-02-27 20:10:37 Connecting to [192.168.1.250]:1194 (192.168.1.250) via UDPv4
Well, one thing that stands out is connecting to a 192168.x.x IP from the outside will never work since it's not routable across the internet. Your config file seems to be using this instead of the WAN IP of the router.

Just google "whats my ip" from the LAN and it will give you your WAN IP. Swap that in the config file and you'll probably need to port forward / trigger to the internal IP from the external request.
 
Well, one thing that stands out is connecting to a 192168.x.x IP from the outside will never work since it's not routable across the internet. Your config file seems to be using this instead of the WAN IP of the router.

Just google "whats my ip" from the LAN and it will give you your WAN IP. Swap that in the config file and you'll probably need to port forward / trigger to the internal IP from the external request.
Every guide I’ve read on how to configure an OpenVPN in a Synology NAS uses a static internal 192.168.x.xxx IP address. If it works for them I don’t see how that could be the problem for me.
 
Every guide I’ve read on how to configure an OpenVPN in a Synology NAS uses a static internal 192.168.x.xxx IP address. If it works for them I don’t see how that could be the problem for me.
The 192.168 address is your nas's internal address inside your LAN. You need this to always the same (static) in order for the port forward from your router to your nas to work (and continue to work).

However, when you're outside your network your vpn client first need to find your router (so it can then port forward to your nas). This means you need either an static external ip (= your wan ip address), or if like me you don't have one of those you need to configure a ddns (essentially a web address that keeps pointing to your dynamic external ip even when it changes).

Step 5 of your instructions explains how to do it, but like @Tech Junky says, it looks from your error message that this part isn't working.
 
The 192.168 address is your nas's internal address inside your LAN. You need this to always the same (static) in order for the port forward from your router to your nas to work (and continue to work).

However, when you're outside your network your vpn client first need to find your router (so it can then port forward to your nas). This means you need either an static external ip (= your wan ip address), or if like me you don't have one of those you need to configure a ddns (essentially a web address that keeps pointing to your dynamic external ip even when it changes).

Step 5 of your instructions explains how to do it, but like @Tech Junky says, it looks from your error message that this part isn't working.
I have a DDNS setup via my NAS, and it says status normal. In the VPN config file, I've tried entering both my NAS static IP address and the DDNS hostname, none of them work.

I just went into portchecktool.com and entered port 1194, and got ''
Problem! I could not see your service on (my IP address) on port (1194).
Reason: Connection timed out.''

I have an ASUS router. I went into WAN - Virtual Server/ Port forwarding - Enable Port Forwarding (check) - Add Profile - entered port 1194 - The static IP of my NAS - UDP just like the VPN is set up as - Pressed OK.

I don't get why this won't work.
 
First you need to add this for the Iphone in the config of the Ovpn file redirect-gateway ipv6 . For the other thing you need to got to Synology>control panel>External access. Now see if the DDNS status is Normal. If that's ok go to router configuration and assuming you have your VPN service put there with 1194 press setup router and follow the text dialog after that it will do a port check see if the port is open(when you do the setup router thing your you must be logged out of the router). The problem you are describing usually means the port is closed , I had this issue with an Asus router after updating the firmware it wouldn't open any port so I had to reset the router and then it was all fine. If you have a laptop just have it connect to the internet via your phone and test like that. So check those if your port doesn't open reset the the router to factory defaults and start from scratch or roll back the firmware that worked for you.
 
First you need to add this for the Iphone in the config of the Ovpn file redirect-gateway ipv6 . For the other thing you need to got to Synology>control panel>External access. Now see if the DDNS status is Normal. If that's ok go to router configuration and assuming you have your VPN service put there with 1194 press setup router and follow the text dialog after that it will do a port check see if the port is open(when you do the setup router thing your you must be logged out of the router). The problem you are describing usually means the port is closed , I had this issue with an Asus router after updating the firmware it wouldn't open any port so I had to reset the router and then it was all fine. If you have a laptop just have it connect to the internet via your phone and test like that. So check those if your port doesn't open reset the the router to factory defaults and start from scratch or roll back the firmware that worked for you.
1. Got redirect-gateway ipv6 in the config file
2. DDNS is normal
3. I have forwarded 1194 via the Asus router settings, not in Synology DSM. When I press router configuration - set up router in DSM, it says my router is not compatible, even though my router (RT-AC68U) is compatible according to Synology's website.
4. The reason I updated my router firmware in the first place a couple of days ago was because this didn't work. I hadn't updated my router in like 5 years.

You mean I have to reset the router and do redo all the settings I've done over the years? Ugh.. Wish it didn't have to come to this.
 
Just add the OpenVPN service to the Synology firewall select built in app and select the 1194 port and then save it and test it. It won't work if the port it's not in the synology firewall. If you get that the port is open from the synology firewall it should work (Test connection button). But after adding a new port it should auto test all the ports if it doesn't you press it.
 
Just add the OpenVPN service to the Synology firewall select built in app and select the 1194 port and then save it and test it. It won't work if the port it's not in the synology firewall. If you get that the port is open from the synology firewall it should work (Test connection button). But after adding a new port it should auto test all the ports if it doesn't you press it.
OpenVPN port 1194 is already added in Synology firewall.
 
OpenVPN port 1194 is already added in Synology firewall.
Do you get a O.K status on the port? If not you should Hard/Factory reset the router and do it again. I've had the same problem after Asus idiotic firmware screwed up port opening for men. Last resort is to try and open another port and change the port for the openvpn server and for the synology firewall and router options. But for me port forwarding just didn't work and I had to hard reset the router and do all the config from scratch . Don't try to upload the router settings since they will mess it up again.
 
Do you get a O.K status on the port? If not you should Hard/Factory reset the router and do it again. I've had the same problem after Asus idiotic firmware screwed up port opening for men. Last resort is to try and open another port and change the port for the openvpn server and for the synology firewall and router options. But for me port forwarding just didn't work and I had to hard reset the router and do all the config from scratch . Don't try to upload the router settings since they will mess it up again.
Ok status on the port? How do I check that? Like I wrote a couple of replies back I went to portchecktool.com and typed in 1194 but it said it failed.
 
It can't be blank it doesn't matter if your router is supported or not just finish the process and test the connection otherwise it won't work. It should look like this if it doesn't you haven't set it up right.
 

Attachments

  • synology.jpg
    synology.jpg
    58.1 KB · Views: 267
All this reminded me why I moved my openvpn server from my syno nas to my Asus router...
 
It can't be blank it doesn't matter if your router is supported or not just finish the process and test the connection otherwise it won't work. It should look like this if it doesn't you haven't set it up right.
All the guides I’ve read have said to not use the router setup in DSM and instead port forward within the router. Nevertheless, I just tried it and it says “Failed” on connection test result.
 
All this reminded me why I moved my openvpn server from my syno nas to my Asus router...
It’s better? I’ve thought about it but wouldn’t that slow down all other devices on the network, or just the one connected to the VPN? Also, is it possible to have an OpenVPN and a VPN client like NordVPN on the same router?
 

Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top