Difference between revisions of "OpenVPN troubleshooting"
m |
m (edited change-your-port instructions) |
||
| Line 23: | Line 23: | ||
== Blocked port 1194 == | == Blocked port 1194 == | ||
| − | Sometimes if you are behind a corporate firewall or | + | Sometimes port 1194 is blocked if you are behind a corporate firewall or someother firewall. The trick is then to use a port that is open. If you are not running https on your amahi, using port 443 is a good choice. |
You can move to port 443 by changing the line:<br> | You can move to port 443 by changing the line:<br> | ||
| Line 32: | Line 32: | ||
Of course you also need to tell the client side to use port 443! | Of course you also need to tell the client side to use port 443! | ||
| + | Add the following line to your client's config file | ||
| − | + | remote <hda_username>.yourhda.com 443 | |
If for some reason the DDNS (yourhda.com) is not working but your control panel is updating, then add this line at the top of the config file. | If for some reason the DDNS (yourhda.com) is not working but your control panel is updating, then add this line at the top of the config file. | ||
| − | remote YOUR_IP_HERE | + | remote YOUR_IP_HERE <port> |
Note: If you have a dynamic ip, then you will probably need to update this everyday. If you have a static ip then you are fine. | Note: If you have a dynamic ip, then you will probably need to update this everyday. If you have a static ip then you are fine. | ||
Revision as of 19:32, 11 April 2011
Typical problems with the VPN:
- You cannot VPN into your network from your very own network (kinda duh)
- You cannot login two users simultaneously
- You cannot login to your network from another network with the exact same settings. You can probably reach your own HDA, but not other systems in the network, due to routing (the HDA has direct connection via the VPN tunnel).
- Check that you have port forwarded 1194 udp.
Contents
Moving to TCP
If UDP is not working because of a shitty ISP (see list below). Then you will have to change from udp to tcp and change your port forwarding of 1194/udp to 1194/tcp.
Client side: (Windows)
Right click the red A, click edit settings. If you have a thing saying "HomeHDA > " then mouse over it and click edit settings. Change:
proto udp
to
proto tcp
Blocked port 1194
Sometimes port 1194 is blocked if you are behind a corporate firewall or someother firewall. The trick is then to use a port that is open. If you are not running https on your amahi, using port 443 is a good choice.
You can move to port 443 by changing the line:
port 1194
into
port 443
in your /etc/openvpn/amahi.conf file.
Of course you also need to tell the client side to use port 443! Add the following line to your client's config file
remote <hda_username>.yourhda.com 443
If for some reason the DDNS (yourhda.com) is not working but your control panel is updating, then add this line at the top of the config file.
remote YOUR_IP_HERE <port>
Note: If you have a dynamic ip, then you will probably need to update this everyday. If you have a static ip then you are fine.
Manually (Windows)
Edit this file manually or use:
Seven x64
C:\Program Files (x86)\HDAConnect\config\HomeHDA.opvn
Seven x86 or 32 bit (Also most other Windows versions)
C:\Program Files\HDAConnect\config\HomeHDA.opvn
Run notepad as admin and open the above file.
Client Side (Linux/Mac)
Similarly, locate the configuration file and change
proto udp
to
proto tcp
On the Server side
Edit this file:
/etc/openvpn/amahi.conf
Command:
sudo gedit /etc/openvpn/amahi.conf
or
sudo nano -w /etc/openvpn/amahi.conf
change "proto udp" to "proto tcp"
Restart both sides and you are now using openvpn over tcp. And add your isp below.
List of bad ISPs
Please add your isp if you need this work-around:
- Bell Canada
- Thames Valley Communications (Groton, CT)
Client Reports "TLS handshake failed" and Does Not Connect
This is usually caused by packet corruption that may happen for some users.
Follow the tutorial on "Prevent SSL Handshake Timeouts In OpenVPN" page to fix this.
