I have been having this issue too, plus some more. For some reason, other than the first user, I am unable to get any other user that I have created certificates for to connect to the pfsense OpenVPN server. Is there a well detailed link that someone can provide me with that I may reference to? After hours of reading MANY outdated post and finding nothing helpful. I found and used a youtube video that wasn't really much informative about creating multiple users and creating certs so the other users may connect to the OpenVPN server. I am not new to OpenVPN, i just don't recall having this problem with previous setups. When creating a certificate for the other users, I am unsure of the method I am suppose to use. I believe it should be "Create an internal Certificate". Under internal Certificate i see, "Certificate authority" with the name of the previous  CA's name that i created for the first user that can connect from anywhere. Am i suppose to create a new CA and certificate for every user i want to connect? Shouldn't I be able to use that same one, Certificate authority? Also for Certificate type I am selecting "User Certificate"…that should be correct, right? My options were User Certificate, Server Certificate, and Certificate authority. Thanks in advance for anyone willing to shed some light on what I may be doing wrong. I am willing to create a more up-to-date how-to once I figure out what is going on.

Use the IP address of the computer that has the web interface - e.g. if the server-en computer is 10.11.1.42 then in the browser go to: \10.11.1.42 If you want to access by name, then add the computer name and IP address to DNS Forwarder, Host Overrides at the home end. Then yyou can use the name in the browser and DNS will find it.

For other readers: push "route 10.2.0.0 255.255.0.0" That is actually trying to tell siteB that the OpenVPN link is a route to 10.2.0.0/16 - but siteB actually has the local LAN 10.2.0.0/16. SiteB will be smart enough to effective ignore that, and talk directly to its local LAN. The  line should be able to be deleted. route 10.2.0.0 255.255.0.0 This route put in the advanced box on the server side is OK. But it should already work like this by putting 10.2.0.0/16 inn the "Remote Networks: box. I can't say why the advanced box entry was really needed. iroute 10.2.0.0 255.255.0.0 Client-specific overrides: This is a good thing, and specifically tells the server which connecting client has the 10.2.0.0/16 network at the client end. IMHO this is the thing that really makes it work.

SUCCESS !! thank you thermo ! worked perfectly . . . all i had to do was move the firewall rule to the top and everything just fell into place. thanks again for taking the time.

That was it!  Thank you!  Didn't even notice it was set to Peer-to-Peer…  Switched to Remote Access (SSL/TLS) and it worked! :)

@darkcrucible: It might also be the outbound NAT. Do you use automatic outbound nat or manual? If it's manual then you'll need to add a rule for the other network to go through NAT. If it's automatic then you might need to switch to manual. Not too sure since I've never really used automatic. Aha! Thank you so much for that suggestions! I just enabled manual outbound NAT on the remote server (the one I would like to route all of my youtube traffic through, and added a rule to pass all traffic from 192.168.1.0/24). Thank you!

Solved my own issue with a little accidental help from marvosa In the client file on ubuntu, near bottom placed: route 10.0.0.0 255.255.255.0  (substituted my LAN Subnet) I haven't ever seen a good fix for this anywhere, but this is so simple.  Why didn't I do earlier (pfsense needs a facepalm icon) :-[ keywords added for web searches: ubuntu linux mint pfsense openvpn can't access LAN TUN client

Assuming you've setup the HQ as the server and the Satellite as the client, you need to add a route(s) to the HQ config to define the client subnet(s) ie: route 10.0.0.0 255.255.255.0 route 10.0.1.0 255.255.255.0       ….. etc.  Need to be added to the server config. The 'push "route....' lines on the server side send the appropriate routes for the client to understand the server's subnets. You don't need any 'push "route...' lines on the client side. If you post a screenshot of your server and client configs, you may get more specific help on your setup

I thought this was going to be more difficult.  Turned out I had my SIP client settings field populated with the wrong authorization number, that would do it.  It also required the SIP client "force address" setting match the PfSense LanGW IP given the OpenVpn tunnel via Wan. Happy days…

https://forum.openwrt.org/viewtopic.php?id=33678 Its not pfsense but it is seeming to sort of be what you want to know.

If you are going to run a SIP server, remember to forward port 5060 OK?  I read some places it helps.

Reinstalling the package worked. I have no idea why it didn't grab the package during the upgrade. anyway thanks guys! life savers. :)

I provide the IP of my DNS forwarder (The LAN IP in my case) because I force all traffic through the client.

Ok my fault. I was talking about 800kb/s throughput when running openvpn on the dd-wrt router. I tought this was clear due to the advice in the previous post. Thats why i want to use the ubuntu-server.

i installed certificates, but there are some config lines , namely nobind auth-retry nointeract tls-client ns-cert-type server keepalive 10 30 tls-cipher TLSv1:!ADH:!SSLv2:!NULL:!EXPORT:!DES:!LOW:!MEDIUM:@STRENGTH persist-key persist-tun tun-mtu 1500 mssfix passtos verb 3 which i paste in "Advanced" section in https://192.168.1.1/vpn_openvpn_client.php?act=new but it still dont work, any ideas? why i cannot just upload .conf to config directly?