smaka510 Posted November 2, 2017 Share Posted November 2, 2017 (edited) Hello, I am new to unraid. I have tried installing various openVPN plug-ins and always get "refused to connect" when trying to access the web UI https://IPAddress:943/admin (I cannot access from any computer on my LAN) is unraid blocking these ports on the server side? ------------------------------- FIGURED IT OUT!!!! THE CAUSE: when you use multiple NICs, OpenVPN-AS does not know which NIC it needs to listen to HERE IS THE FIX: If you edit your docker, then go to 1. "Add another Path, Port or Variable" 2. "Config Type: => Variable", "Name: => INTERFACE", "Key: INTERFACE", "Value: bond0". 3. Hit Apply, done and restart docker. Maybe I didn't read far enough into the documentation and it says this somewhere. I nearly lost my mind over this! Posting for the next man. Edited November 3, 2017 by smaka510 Quote Link to comment
ijuarez Posted November 2, 2017 Share Posted November 2, 2017 what plugins are you using? there a whole thread on using a docker called OpenVpn-AS Quote Link to comment
Hoopster Posted November 2, 2017 Share Posted November 2, 2017 If you want to use the linuxserver.io OpenVPN-AS Docker see Spaceinvader's Youtube video on setting it up on unRAiD. As mentioned, there is a very detailed and helpful support thread as well for this docker in the Docker Containers forum. There are a few "gotchas" with configuration and recent versions. The database update issue documented in the last couple of pages of the forum has bitten almost everyone since the last container update, but, the TLS toggle trick seems to fix it for now. Nothing on unRAID blocks the ports needed for OpenVPN unless you have another docker or plugin configured to use them. Quote Link to comment
smaka510 Posted November 3, 2017 Author Share Posted November 3, 2017 FIGURED IT OUT!!!! THE CAUSE: when you use multiple NICs, OpenVPN-AS does not know which NIC it needs to listen to HERE IS THE FIX: If you edit your docker, then go to 1. "Add another Path, Port or Variable" 2. "Config Type: => Variable", "Name: => INTERFACE", "Key: INTERFACE", "Value: bond0". 3. Hit Apply, done and restart docker. Maybe I didn't read far enough into the documentation and it says this somewhere. I nearly lost my mind over this! Posting for the next man. 1 2 Quote Link to comment
falconexe Posted September 5, 2020 Share Posted September 5, 2020 On 11/2/2017 at 6:21 PM, smaka510 said: HERE IS THE FIX: @smaka510Thank you very much. This is still applicable in 2020 and I really appreciate it. I run dual NICS, 1GBe and 10Gbe. I was thinking it was some kind of Chrome security setting ha ha. Thanks again! Quote Link to comment
Recommended Posts
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.