Trouble Connecting to OpenVPN Access Server from External Network
Posted: Sat Mar 26, 2022 5:34 pm
I am having trouble connecting to my OpenVPN server from external networks. When on the same LAN as the OpenVPN server, I can connect immediately without issue. I have been working on this for a week with no success, so I'm hoping someone might have some new ideas.
The server is running on an Ubuntu 18.04 system with UFW (universal firewall). The server is set to run in multi-daemon mode, using both TCP and UDP. With TCP being on port 443 and UDP on port 1194. The admin panel is at port 943. The ufw firewall has exceptions to allow traffic through ports 443, 943, and 1194. I have tested with and without the ufw firewall enabled.
My router is an AT&T Router/Modem combo, a BGW210-700. I have set it up to forward the ports 443, 943, and 1194. When doing an open port check, 443 and 943 show open but 1194 shows closed. I have tried disabling all of the firewall settings and disabling packet filtering.
I have tried adding another router (TP-Link ER605), connected directly to the LAN port of the AT&T router. I set the AT&T router into IP passthrough mode and pass the IP address directly to my new TP-Link router. I can confirm that the second router now shows at the public IP address. I again forwarded 443, 943, and 1194. The result is the same: 443 and 943 show open, 1194 shows closed.
From an external network, I can access the admin panel at port 943 to download my user profile. When I try to connect to the VPN, it eventually times out. The server logs never show an incoming connection attempt, the client just times out when trying to connect. This result has been the same for both router configurations and with firewalls on/off for the server (ufw) and the AT&T Router. When in multi-daemon mode, the client seems to get stuck trying port 1194. When I set the server to use TCP only, it seems to get stuck trying port 443.
I am trying to connect remotely via Android app and the Verizon LTE network.
Any suggestions are much appreciated!
The server is running on an Ubuntu 18.04 system with UFW (universal firewall). The server is set to run in multi-daemon mode, using both TCP and UDP. With TCP being on port 443 and UDP on port 1194. The admin panel is at port 943. The ufw firewall has exceptions to allow traffic through ports 443, 943, and 1194. I have tested with and without the ufw firewall enabled.
My router is an AT&T Router/Modem combo, a BGW210-700. I have set it up to forward the ports 443, 943, and 1194. When doing an open port check, 443 and 943 show open but 1194 shows closed. I have tried disabling all of the firewall settings and disabling packet filtering.
I have tried adding another router (TP-Link ER605), connected directly to the LAN port of the AT&T router. I set the AT&T router into IP passthrough mode and pass the IP address directly to my new TP-Link router. I can confirm that the second router now shows at the public IP address. I again forwarded 443, 943, and 1194. The result is the same: 443 and 943 show open, 1194 shows closed.
From an external network, I can access the admin panel at port 943 to download my user profile. When I try to connect to the VPN, it eventually times out. The server logs never show an incoming connection attempt, the client just times out when trying to connect. This result has been the same for both router configurations and with firewalls on/off for the server (ufw) and the AT&T Router. When in multi-daemon mode, the client seems to get stuck trying port 1194. When I set the server to use TCP only, it seems to get stuck trying port 443.
I am trying to connect remotely via Android app and the Verizon LTE network.
Any suggestions are much appreciated!