January 29, 20197 yr I tried in bridge and host and the route will never be added to the network settings. But that was using 6.7.0rc2 i downgraded back. I'll test again and is stableSent from my Pixel 2 XL using Tapatalk
January 30, 20197 yr 3 hours ago, gacpac said: I tried in bridge and host and the route will never be added to the network settings. But that was using 6.7.0rc2 i downgraded back. I'll test again and is stable Sent from my Pixel 2 XL using Tapatalk What do you mean by route never got added to the network?
January 30, 20197 yr What do you mean by route never got added to the network?Well.When you go settings > network settingsThen you scroll down to routing table and you should be able to seeRoute (VPN server ipaddress). Gateway (tun0)Metric (1)If this information is not added then your VPN server won't know where to go. Sent from my Pixel 2 XL using Tapatalk
January 30, 20197 yr 3 hours ago, gacpac said: Well. When you go settings > network settings Then you scroll down to routing table and you should be able to see Route (VPN server ipaddress). Gateway (tun0) Metric (1) If this information is not added then your VPN server won't know where to go. Sent from my Pixel 2 XL using Tapatalk Do you mean in the unraid gui? No, you won't see the tun interface in the unraid gui because the interface is inside the container. Vpn knows where to go because you are mapping ports. It goes through the docker bridge network on the host. Did you actually try connecting or are you hypothesizing? Edited January 30, 20197 yr by aptalca
January 30, 20197 yr 2 minutes ago, aptalca said: Do you mean in the unraid gui? No, you won't see the tun interface in the unraid gui because the interface is inside the container. Vpn knows where to go because you are mapping ports. It goes through the docker bridge network on the host. Did you actually try connecting or are you hypothesizing? Actually, it's supposed to create a route automatically. Now in version 6.6.6 it's working perfectly And it has to show. If it doesn't show then the network is not created, meaning it won't connect.
January 31, 20197 yr On 1/27/2019 at 8:49 PM, gacpac said: Sorry. The docker starts and everything but it doesn't connect, and the route is also gone from the network settings. I literally rolled back and started working again. I also had this issue with 6.7.0. I was unable to connect after upgrading, but it works fine after downgrading back to 6.6.6
January 31, 20197 yr 41 minutes ago, Peanutman85 said: I also had this issue with 6.7.0. I was unable to connect after upgrading, but it works fine after downgrading back to 6.6.6 A fellow man who understands. I will wait until 6.7.0 stable to test
February 1, 20197 yr current version of unraid (rc2) and docker container, I can only access the unraid base ip, I can no longer access anything else on the local lan because of the missing routing information
February 2, 20197 yr For anyone who's having issues with openvpn on unraid 6.7 rc, switch it to run in bridge networking, remove the INTERFACE variable setting or set it to eth0 (default) and map the ports 943 and 9443 for tcp and 1194 for udp
February 3, 20197 yr Trying to add open vpn as docker, and there is not a download/install button, just a doate button. How do I install this docker?
February 3, 20197 yr 2 hours ago, icemounty said: Trying to add open vpn as docker, and there is not a download/install button, just a doate button. How do I install this docker? See you already got your answer on the CA thread. Everybody can just skip this.
February 8, 20197 yr On 2/1/2019 at 8:20 PM, aptalca said: For anyone who's having issues with openvpn on unraid 6.7 rc, switch it to run in bridge networking, remove the INTERFACE variable setting or set it to eth0 (default) and map the ports 943 and 9443 for tcp and 1194 for udp Thanks! This solved my problems. I left the INTERFACE variable alone (it was set to eth0 anyway) and changed the network type from Host to Bridge , saved the changes and openvpn-as started working perfectly again 🙂
February 11, 20197 yr On 2/2/2019 at 3:20 AM, aptalca said: For anyone who's having issues with openvpn on unraid 6.7 rc, switch it to run in bridge networking, remove the INTERFACE variable setting or set it to eth0 (default) and map the ports 943 and 9443 for tcp and 1194 for udp Perfect.. worked after deleting the interface variable and switching to BRIDGE...
February 13, 20197 yr Hey, bit of a noob here, thanks for the great work! I am curently running a Pi-Hole container with it's own IP address and its working great with all connected devices - locally and externally. The openvpn-AS server is also working great when not altering the client's DNS server settings. The issue I am querying is when I set custom DNS to Pi-Hole's internal IP address and connect from outside the network, I connect to the VPN, but i cannot then connect back out to the internet. The only change I have made is under "VPN settings" and "Have clients use specific DNS servers", from which I enter the local IP of my PI-Hole server. I am trying to connect with Android 8.1 and I am using OpenVPN for android app. I had also set the DNS in the settings within the config on android but that makes no difference. I can get logs if required. Any idea in what direction to move would be appreciated! Many thanks in advance! Edited February 13, 20197 yr by Brawbag spelling
February 13, 20197 yr On 1/30/2019 at 12:57 AM, gacpac said: Actually, it's supposed to create a route automatically. Now in version 6.6.6 it's working perfectly And it has to show. If it doesn't show then the network is not created, meaning it won't connect. Umm, that's a no. In bridge mode, connection goes from whatever network unraid uses, to the docker network, to the container through mapped ports, and inside the container it goes to the tun device. The tun device is not exposed to the host. I assure you my unraid knows nothing about a tun device and I have no problems connecting to vpn inside the container. Like I said before, you should test it instead of just hypothesizing.
February 13, 20197 yr Umm, that's a no. In bridge mode, connection goes from whatever network unraid uses, to the docker network, to the container through mapped ports, and inside the container it goes to the tun device. The tun device is not exposed to the host. I assure you my unraid knows nothing about a tun device and I have no problems connecting to vpn inside the container. Like I said before, you should test it instead of just hypothesizing.Well I looked at other users and it seemed to eb an issue when the docker is connected to the host network, which creates a tun route. I tried on bridge mode and it works. Same as the other usersSent from my Pixel 2 XL using Tapatalk
February 21, 20197 yr On 2/2/2019 at 3:20 AM, aptalca said: For anyone who's having issues with openvpn on unraid 6.7 rc, switch it to run in bridge networking, remove the INTERFACE variable setting or set it to eth0 (default) and map the ports 943 and 9443 for tcp and 1194 for udp Hi, I tried this with no luck (connection refused) but oddly I'm having the same problem with Plex (connection refused). I've tried different combinations of settings including other builds and can see port mappings and unlike other dockers on the machine (CA Advisor, emby, duplicati) which just seem to work I'm getting no where. The other strange thing was that Plex (which may be a red hearning) was working. I'm on 6.7.0-rc4 Thanks Terran Edit .... Plex aside I've got openvpn back but had to remove the docker and then the appdata folder then reinstall. Some thing must have gone screwy T Edited February 21, 20197 yr by ccsnet
February 23, 20197 yr I am trying to get this setup. I have logged into the OpenVPN however I am getting this error. Are there any suggestions for getting this to start? I am trying to get it working on my Android Phone Error: cannot locate HMAC in incoming packet from [AF_INET}] XXX.XXX.XXX.XXX:1194 Edited February 23, 20197 yr by mgranger
February 23, 20197 yr I read to disable tls authentication and when I do this error 10:29 PM TCP/UDP: Incoming packet rejected from [AF_INET]XXX.XXX.X.X:1194[2], expected peer addreSS: [AF_INET]XX.XXX.XXX.XXX:1194 (allow this incoming source address/port by removing --remote or adding --float)
February 23, 20197 yr Hi... Just updated as I could not get openvpn started with out errors even using the fix above and I've had to eat the image and folder again as I got connection refused after the update completed. Are there any logs I can share here that would be any help ? Thanks Terran
February 23, 20197 yr On 2/1/2019 at 10:20 PM, aptalca said: For anyone who's having issues with openvpn on unraid 6.7 rc, switch it to run in bridge networking, remove the INTERFACE variable setting or set it to eth0 (default) and map the ports 943 and 9443 for tcp and 1194 for udp Worked for me on 6.7.0rc4. thanks!
February 23, 20197 yr 1 hour ago, robd said: Worked for me on 6.7.0rc4. thanks! Hi. One of the first things I tried. Thanks Terran
February 28, 20197 yr Upgraded to 6.6.7 and now I'm getting a connection refused error... Tried reinstalling the container, a new appdata folder, bridge mode, eth0 instead of bond0, but nothing has worked... Any ideas? tower-diagnostics-20190228-0840.zip
February 28, 20197 yr 4 hours ago, thepawn713 said: Upgraded to 6.6.7 and now I'm getting a connection refused error... Tried reinstalling the container, a new appdata folder, bridge mode, eth0 instead of bond0, but nothing has worked... Any ideas? tower-diagnostics-20190228-0840.zip Did you map the ports?
February 28, 20197 yr 7 minutes ago, aptalca said: Did you map the ports? Yep! It's been working fine for months and has just recently stopped.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.