Typical problems with the VPNOpenVPN setup:

* You cannot It's not possible VPN into your network from your very own network . This is not possible and it will fail (kinda duh)* You cannot login two users simultaneously. The OpenVPN setup is single-user.* You cannot login to your network from another network with the exact same settings. This is not possible due to routing. 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 udpUDP.

== Moving to tcp By: dizzy1 Diagnose ==* Is the Amahi [http://www.amahi.org/apps/openvpn OpenVPN] application installed in your HDA? (this is not required if you are on Amahi Fedora 14, but required on all later releases)

If udp * Make sure your HDA's network IP range is not working because different than that of shitty isps the remote network. (see list below)e.g. if your HDA's IP address is 192.168.1. Also X, you will have cannot connect to change the port forward to tcp or tcp and udp instead of udpit on a remote network also using 192.168.1. Edit these two files:X)

Client side* If you are running your HDA from a Verizon FiOS connection, you may experience strange disconnections. This may be due to the Actiontec router's small NAT table. Please see guides [http: (Windows)//www.verizonfioswiki.com/index.php/Using_Your_Own_Router here] for instructions on how to use your own router.

* If you have a Vonage V- CPortal (or perhaps other voip adapters as well), plug your router into your modem, then the v-portal into your router. Vonage tells you to put the v-portal between the modem and the router, but I was unable to connect to vpn until I moved the adapter behind the router. == Moving to TCP == If UDP is not working because of your 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:\Program Files (x86Windows)\HDAConnect\config\HomeHDA.opvn==

If you have a thing saying "HomeHDA > " then mouse over it and click edit settings.Change:  proto udpto proto tcp == Blocked port 1194 ==Sometimes port 1194 is blocked if you are behind a corporate firewall or some other 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. To move to port 443, edit this file: <blockquote><u>Fedora</u></blockquote> gedit /etc/openvpn/amahi.confor sudo nano -w /etc/openvpn/amahi.conf <blockquote><u>Fedora</u></blockquote> gedit /etc/openvpn/openvpn.confor sudo nano -w /etc/openvpn/openvpn.conf change the line:<br> port 1194into port 443<br>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> <b>NOTE:</b> If you have a dynamic IP address, then you will probably need to update this everyday. If you have a static IP address 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 udpto proto tcp == On the Server side ==Edit this file: <blockquote><u>Fedora</u></blockquote> gedit /etc/openvpn/amahi.confor sudo nano -w /etc/openvpn/amahi.conf <blockquote><u>Ubuntu</u></blockquote> gedit /etc/openvpn/openvpn.confor sudo nano -w /etc/openvpn/openvpn.conf change proto udpto proto tcp

If for some reason the DDNS (yourhda.com) is not working but your control panel is updatingRestart both sides and you are now using OpenVPN over tcp, the and add this line at the top of the config fileyour [http://en.wikipedia.org/wiki/Internet_service_provider ISP] below.

HDA sidePlease add your isp if you need this work-around:

change ==Client reports "proto udpTLS handshake failed" to and doesn't Connect==This is usually caused by packet corruption that may happen for some users.<br>Follow the tutorial on "proto tcp[[Prevent_SSL_Handshake_Timeouts_In_OpenVPN|Prevent SSL Handshake Timeouts In OpenVPN]]"page to fix this.