[support] macesters's Docker Repository


Recommended Posts

OpenVPN container was working yesterday on the June 13 build.  At least it was working as far as being able to access the WebUI and poke around in the setup.  I had to remove the OpenVPN container today and reinstall it because of something I messed up and wanted to reset the whole thing from scratch.  Ever since the reinstall, the WebUI is also inaccessible for me.

 

Stop and restart container does not resolve problem.  I am not seeing the other errors being reported here, but, I can't access the WebUI, I get "cannot establish connection the server at [ipaddress]:943" error.  Nothing else is using ports 943 or 443.

 

 

 

Remove the container and image, and then clear the config directory (or choose another location). After that it should work and with the rewrite of the docker it should survive upgrades/rebuilds in the future.  :)

 

PS. Do an update in the Community Applications, it was rebuild and updated about an hour ago.

 

Removed container and image, removed entire openvpn folder and subfolders in docker appdata share, reinstalled OpenVPN from Community Applications, set environment variables, rechecked port forwarding in router.  Still cannot access WebUI.  :-\

 

Here are some things you can check

 

Can you reach the webui locally? ex, https://192.168.1.100:443 or https://192.168.1.100:943?

 

What does the log say? if you click the little notepad icon to the right in the docker tab.

 

Does the appdata/config/ folder pupulate with files/folders? should be two folders in there /config and /logs.

 

 

 

BTW i think managed to reproduce the error,

 

Are you useing something like "/mnt/user/appdata/openvpn/"?

 

Try the disk directly instead "/mnt/cache/appdata/openvpn/", does that work?

 

Host path is set to: "/mnt/cache/appdata/openvpn/" and has been on every install of container.

However, in the openvpn folder there is NOTHING.  It appears completely empty.  The log file contains the repeated message: "./run : line 3: /usr/local/openvpn_as/scripts/openvpnas: No such file or directory"

 

Cannot reach webui locally at https://[ipaddress]:443 or https://[ipaddress]:943 or htpps://[servername]:943?

Link to comment

 

PS. Do an update in the Community Applications, it was rebuild and updated about an hour ago.

Just as a clarification, the only time you need to update apps in CA is if an update to the template occurs.  And if an update occurred to the template, then dockerMan may or may not pick up the changes that CA saw.  In that situation, its best to delete the existing references on the flash drive (/boot/config/plugins/dockerMan/templates and templates-user)

 

Yea I figured, I added some text in the change notes and the "volume" line was changed.

 

(/boot/config/plugins/dockerMan/templates and templates-user)

 

Thinking this is the problem Hoopster is having, that his volume line is cached or something else or it´s somekind of permission issues.

 

 

Does it looks like this Hoopster?

 

WsELSkV.png

 

 

//mace

Link to comment

 

PS. Do an update in the Community Applications, it was rebuild and updated about an hour ago.

Just as a clarification, the only time you need to update apps in CA is if an update to the template occurs.  And if an update occurred to the template, then dockerMan may or may not pick up the changes that CA saw.  In that situation, its best to delete the existing references on the flash drive (/boot/config/plugins/dockerMan/templates and templates-user)

 

Yea I figured, I added some text in the change notes and the "volume" line was changed.

 

(/boot/config/plugins/dockerMan/templates and templates-user)

 

Thinking this is the problem Hoopster is having, that his volume line is cached or something else or it´s somekind of permission issues.

 

 

Does it looks like this Hoopster?

 

WsELSkV.png

 

 

//mace

There are some issues with dockerMan (completely out of my control).  Not 100% sure if it picks up changes with volumes correctly (unless you delete all existing traces of the templates out of templates and templates-user)  I know that dockerMan will NOT pick up changes to the webUI line.  There's a couple of feature requests / defect reports about this.

 

The best course of action on template changes (excluding descriptions) is to have the users delete the references to the template in /boot/config/plugins/dockerMan/template-user (the my* template).  Then delete the container (shouldn't have to delete the image) then re-add the container.

 

Not really following this thread (no interest in these containers), but saw something that caught my eye and figured I'd pipe in.

 

See here:

 

http://lime-technology.com/forum/index.php?topic=41106.0

http://lime-technology.com/forum/index.php?topic=40262.msg380740#msg380740

Link to comment

There are some issues with dockerMan (completely out of my control).  Not 100% sure if it picks up changes with volumes correctly (unless you delete all existing traces of the templates out of templates and templates-user)  I know that dockerMan will NOT pick up changes to the webUI line.  There's a couple of feature requests / defect reports about this.

 

The best course of action on template changes (excluding descriptions) is to have the users delete the references to the template in /boot/config/plugins/dockerMan/template-user (the my* template).  Then delete the container (shouldn't have to delete the image) then re-add the container.

 

Not really following this thread (no interest in these containers), but saw something that caught my eye and figured I'd pipe in.

 

See here:

 

http://lime-technology.com/forum/index.php?topic=41106.0

http://lime-technology.com/forum/index.php?topic=40262.msg380740#msg380740

 

Deleted the template in /boot/config/plugins/dockerMan/template-user/my-OpenVPN-AS.xml; removed container (not image); added container again; problem persists and openvpn folder in appdata remains empty.  As Macester said, permission issue in creating folder?  Funny thing is I had no such issues with his June 13 build of the container.  Issues just began with yesterday's build.

Link to comment

Funny thing is I had no such issues with his June 13 build of the container.  Issues just began with yesterday's build.

 

The yesterday´s build is a complete rewrite of the docker, and the main thing that change in user perspective is that the volume mappings are diffrent.

 

 

Map it like my screenshoot

 

remove the line /usr/local/openvpn_as and change it to /config.

 

//mace

Link to comment

Rewrote it completely...

 

Either create a folder on lets say a samba share, then in omv check the acl for the share/subfolder that the group users have full R/W/E perms and click Apply permissions to files and subfolders.

 

Or,

 

mkdir -p /docker_configs/openvpn_config
chmod 775 -R /dockerdata
chown 99:users -R /dockerdata

 

and after that, run:

 

docker run -d --net="host" --privileged --name=openvpnas -v /docker_configs/openvpn_config:/config -v /etc/localtime:/etc/localtime:ro -e ADMIN_PASS=myadminpassword -e VPN_USER1=vpnuser1 -e VPN_PASS1=mypassword1 -e VPN_USER2=vpnuser2 -e VPN_PASS2=mypassword2 mace/openvpn-as

 

Tested both ways on an OMV 2.1 and an Ubuntu 14.04  install, and works without a hitch.

 

Or just say Frack it! and "chmod 777"  :P

 

//mace

 

Awesome!!

 

I tried the new re-write build and everything is working!

 

Thanks a lot!

Link to comment

Funny thing is I had no such issues with his June 13 build of the container.  Issues just began with yesterday's build.

 

The yesterday´s build is a complete rewrite of the docker, and the main thing that change in user perspective is that the volume mappings are diffrent.

 

 

Map it like my screenshoot

 

remove the line /usr/local/openvpn_as and change it to /config.

 

//mace

 

 

Sorry, I misunderstood your prior post and thought /config was the mistake and that mapping should have been as in previous build.  I have now changed container volume mapping to /config and the WebUI is again accessible.  :)  Thank you!!

 

Now on to figuring out the server configuration.

Link to comment

Nice to here  :D

 

For a fully working vpn server that can reach recources on your home LAN it´s pretty simple.

 

 

Configuration section:

 

Server Network Settings (tab)

 

Hostname or IP Address:

(external ip or dnas name ex, myunraid.dyndns.org).

 

 

VPN Settings                  (tab)

   

Routing - "Specify the private subnets to which all clients should be given access":

(add your home LAN ex, 192.168.1.0/24 bellow the line 172.17.0.0/16)

 

DNS Settings - Have clients use these DNS servers:

(primary dns 8.8.8.8 secondary dns 8.8.4.4)

 

User Management section:

 

User Permissions           (tab)

(add the two vpn users matching the exact name from the docker "Variable Value")

 

 

Then on your client surf to https://myunraid.dyndns.org:943 and login with the vpnuser details.

 

A side note is that in the .ovpn file for your client you might want to remove the line that says myunraid.dyndns.org:443 and just keep the lines with myunraid.dyndns.org:1194 for a big speed improvment.

Or disable tcp/443 connections in the webui (no need to forward port tcp/443 in your router)

 

//mace

Link to comment

OpenVPN is not working for me. I attached the log file. Does not appear anyone else has had this issue. Log is referring to eth0 not found. Any ideas?

 

 

Wierd my log looks identical to yours when i select, "Network type:  none"

 

If you ssh to your unraid box what is the output of?

 

docker exec -i -t OpenVPN-AS bash

then

ifconfig

Link to comment

OpenVPN is not working for me. I attached the log file. Does not appear anyone else has had this issue. Log is referring to eth0 not found. Any ideas?

 

 

Wierd my log looks identical to yours when i select, "Network type:  none"

 

If you ssh to your unraid box what is the output of?

 

docker exec -i -t OpenVPN-AS bash

then

ifconfig

 

root@Tower:/# ifconfig

br0      Link encap:Ethernet  HWaddr 00:25:90:57:72:84 

          inet addr:192.168.1.201  Bcast:192.168.1.255  Mask:255.255.255.0

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:1627557 errors:0 dropped:15806 overruns:0 frame:0

          TX packets:1490082 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:392983612 (392.9 MB)  TX bytes:447470543 (447.4 MB)

 

docker0  Link encap:Ethernet  HWaddr 56:78:61:52:55:48 

          inet addr:172.17.42.1  Bcast:0.0.0.0  Mask:255.255.0.0

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:224540 errors:0 dropped:0 overruns:0 frame:0

          TX packets:331504 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:16998955 (16.9 MB)  TX bytes:88270226 (88.2 MB)

 

eth0      Link encap:Ethernet  HWaddr 00:25:90:57:72:85 

          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1

          RX packets:1650807 errors:0 dropped:11924 overruns:0 frame:0

          TX packets:1776824 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:436989590 (436.9 MB)  TX bytes:473260582 (473.2 MB)

          Interrupt:20 Memory:f7a00000-f7a20000

 

eth1      Link encap:Ethernet  HWaddr 00:25:90:57:72:84 

          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1

          RX packets:483071 errors:0 dropped:0 overruns:0 frame:0

          TX packets:14155 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:51937412 (51.9 MB)  TX bytes:1602044 (1.6 MB)

          Interrupt:16 Memory:f7900000-f7920000

 

lo        Link encap:Local Loopback 

          inet addr:127.0.0.1  Mask:255.0.0.0

          UP LOOPBACK RUNNING  MTU:65536  Metric:1

          RX packets:572755 errors:0 dropped:0 overruns:0 frame:0

          TX packets:572755 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:93414046 (93.4 MB)  TX bytes:93414046 (93.4 MB)

 

vetheb215f8 Link encap:Ethernet  HWaddr 56:78:61:52:55:48 

          UP BROADCAST RUNNING  MTU:1500  Metric:1

          RX packets:19945 errors:0 dropped:0 overruns:0 frame:0

          TX packets:186076 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:2044671 (2.0 MB)  TX bytes:22393722 (22.3 MB)

 

vethf2a0f38 Link encap:Ethernet  HWaddr 7e:5a:11:5c:e5:59 

          UP BROADCAST RUNNING  MTU:1500  Metric:1

          RX packets:0 errors:0 dropped:0 overruns:0 frame:0

          TX packets:109559 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:0 (0.0 B)  TX bytes:8952168 (8.9 MB)

 

vethffc98e8 Link encap:Ethernet  HWaddr 8a:a4:80:2d:a9:16 

          UP BROADCAST RUNNING  MTU:1500  Metric:1

          RX packets:204595 errors:0 dropped:0 overruns:0 frame:0

          TX packets:310904 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:18097844 (18.0 MB)  TX bytes:79402619 (79.4 MB)

 

virbr0    Link encap:Ethernet  HWaddr 52:54:00:be:b4:04 

          inet addr:192.168.122.1  Bcast:192.168.122.255  Mask:255.255.255.0

          UP BROADCAST MULTICAST  MTU:1500  Metric:1

          RX packets:0 errors:0 dropped:0 overruns:0 frame:0

          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

 

Link to comment

OpenVPN is not working for me. I attached the log file. Does not appear anyone else has had this issue. Log is referring to eth0 not found. Any ideas?

 

 

Wierd my log looks identical to yours when i select, "Network type:  none"

 

If you ssh to your unraid box what is the output of?

 

docker exec -i -t OpenVPN-AS bash

then

ifconfig

 

root@Tower:/# ifconfig

br0      Link encap:Ethernet  HWaddr 00:25:90:57:72:84 

          inet addr:192.168.1.201  Bcast:192.168.1.255  Mask:255.255.255.0

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:1627557 errors:0 dropped:15806 overruns:0 frame:0

          TX packets:1490082 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:392983612 (392.9 MB)  TX bytes:447470543 (447.4 MB)

 

docker0  Link encap:Ethernet  HWaddr 56:78:61:52:55:48 

          inet addr:172.17.42.1  Bcast:0.0.0.0  Mask:255.255.0.0

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:224540 errors:0 dropped:0 overruns:0 frame:0

          TX packets:331504 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:16998955 (16.9 MB)  TX bytes:88270226 (88.2 MB)

 

eth0      Link encap:Ethernet  HWaddr 00:25:90:57:72:85 

          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1

          RX packets:1650807 errors:0 dropped:11924 overruns:0 frame:0

          TX packets:1776824 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:436989590 (436.9 MB)  TX bytes:473260582 (473.2 MB)

          Interrupt:20 Memory:f7a00000-f7a20000

 

eth1      Link encap:Ethernet  HWaddr 00:25:90:57:72:84 

          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1

          RX packets:483071 errors:0 dropped:0 overruns:0 frame:0

          TX packets:14155 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:51937412 (51.9 MB)  TX bytes:1602044 (1.6 MB)

          Interrupt:16 Memory:f7900000-f7920000

 

lo        Link encap:Local Loopback 

          inet addr:127.0.0.1  Mask:255.0.0.0

          UP LOOPBACK RUNNING  MTU:65536  Metric:1

          RX packets:572755 errors:0 dropped:0 overruns:0 frame:0

          TX packets:572755 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:93414046 (93.4 MB)  TX bytes:93414046 (93.4 MB)

 

vetheb215f8 Link encap:Ethernet  HWaddr 56:78:61:52:55:48 

          UP BROADCAST RUNNING  MTU:1500  Metric:1

          RX packets:19945 errors:0 dropped:0 overruns:0 frame:0

          TX packets:186076 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:2044671 (2.0 MB)  TX bytes:22393722 (22.3 MB)

 

vethf2a0f38 Link encap:Ethernet  HWaddr 7e:5a:11:5c:e5:59 

          UP BROADCAST RUNNING  MTU:1500  Metric:1

          RX packets:0 errors:0 dropped:0 overruns:0 frame:0

          TX packets:109559 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:0 (0.0 B)  TX bytes:8952168 (8.9 MB)

 

vethffc98e8 Link encap:Ethernet  HWaddr 8a:a4:80:2d:a9:16 

          UP BROADCAST RUNNING  MTU:1500  Metric:1

          RX packets:204595 errors:0 dropped:0 overruns:0 frame:0

          TX packets:310904 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:18097844 (18.0 MB)  TX bytes:79402619 (79.4 MB)

 

virbr0    Link encap:Ethernet  HWaddr 52:54:00:be:b4:04 

          inet addr:192.168.122.1  Bcast:192.168.122.255  Mask:255.255.255.0

          UP BROADCAST MULTICAST  MTU:1500  Metric:1

          RX packets:0 errors:0 dropped:0 overruns:0 frame:0

          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

 

Ok, I figured it out. Under Network Settings in unRaid I had setup bridge set to yes and when I turned that off it works just fine.

Link to comment

Call me stupid but I don't see the default password for the webui (username is listed as openvpn) anywhere?

 

You can see it in the variables on the Advanced View page (upper right corner) when editing the docker config.  It's something like webUI_changme (I can't remember as I changed it  :))

Link to comment

Call me stupid but I don't see the default password for the webui (username is listed as openvpn) anywhere?

 

You can see it in the variables on the Advanced View page (upper right corner) when editing the docker config.  It's something like webUI_changme (I can't remember as I changed it  :))

 

Never noticed that advanced view button (it's pretty small).  Thanks!

Link to comment

Ah so you can only use the OpenVPN-AS docker as a VPN server not as a client to create a tunnel for your entire server to a VPN service?  I was hoping to use it as a client to create an always on tunnel to AirVPN so I don't have to configure pfSense for that.  That way my unRAID server (and any of the additional dockers) would transmit through that tunnel while all other traffic on my network goes out my regular WAN.  Can this be done or should I just leave that type of config to my pfSense box?

Link to comment

Ah so you can only use the OpenVPN-AS docker as a VPN server not as a client to create a tunnel for your entire server to a VPN service?  I was hoping to use it as a client to create an always on tunnel to AirVPN so I don't have to configure pfSense for that.  That way my unRAID server (and any of the additional dockers) would transmit through that tunnel while all other traffic on my network goes out my regular WAN.  Can this be done or should I just leave that type of config to my pfSense box?

 

Nope not possible, OpenVPN-AS, AS as in Access server  :P

 

Binhex have a fwee dockers with vpn support, other that that i dont know.

 

I run pfsense for that myself, just NAT the ips that i want through the vpn(no NAT rules for them over my regular wan interface) and block them with outgoing firewall rules through the regular wan interface for no dns leakeage.

(use dns servers that keeps no logs).

 

//mace

Link to comment

Ah so you can only use the OpenVPN-AS docker as a VPN server not as a client to create a tunnel for your entire server to a VPN service?  I was hoping to use it as a client to create an always on tunnel to AirVPN so I don't have to configure pfSense for that.  That way my unRAID server (and any of the additional dockers) would transmit through that tunnel while all other traffic on my network goes out my regular WAN.  Can this be done or should I just leave that type of config to my pfSense box?

 

Nope not possible, OpenVPN-AS, AS as in Access server  :P

 

Binhex have a fwee dockers with vpn support, other that that i dont know.

 

I run pfsense for that myself, just NAT the ips that i want through the vpn(no NAT rules for them over my regular wan interface) and block them with outgoing firewall rules through the regular wan interface for no dns leakeage.

(use dns servers that keeps no logs).

 

//mace

 

What VPN service do you use?

Link to comment

Ah so you can only use the OpenVPN-AS docker as a VPN server not as a client to create a tunnel for your entire server to a VPN service?  I was hoping to use it as a client to create an always on tunnel to AirVPN so I don't have to configure pfSense for that.  That way my unRAID server (and any of the additional dockers) would transmit through that tunnel while all other traffic on my network goes out my regular WAN.  Can this be done or should I just leave that type of config to my pfSense box?

 

Nope not possible, OpenVPN-AS, AS as in Access server  :P

 

Binhex have a fwee dockers with vpn support, other that that i dont know.

 

I run pfsense for that myself, just NAT the ips that i want through the vpn(no NAT rules for them over my regular wan interface) and block them with outgoing firewall rules through the regular wan interface for no dns leakeage.

(use dns servers that keeps no logs).

 

//mace

 

What VPN service do you use?

 

Private Internet Access, been happy with them getting about 100-120 mbit throughput.

Gonna move from pfsense to sophos utm so hope they support ipsec tunnels.

Link to comment

Ah so you can only use the OpenVPN-AS docker as a VPN server not as a client to create a tunnel for your entire server to a VPN service?  I was hoping to use it as a client to create an always on tunnel to AirVPN so I don't have to configure pfSense for that.  That way my unRAID server (and any of the additional dockers) would transmit through that tunnel while all other traffic on my network goes out my regular WAN.  Can this be done or should I just leave that type of config to my pfSense box?

 

Nope not possible, OpenVPN-AS, AS as in Access server  :P

 

Binhex have a fwee dockers with vpn support, other that that i dont know.

 

I run pfsense for that myself, just NAT the ips that i want through the vpn(no NAT rules for them over my regular wan interface) and block them with outgoing firewall rules through the regular wan interface for no dns leakeage.

(use dns servers that keeps no logs).

 

//mace

 

What VPN service do you use?

 

Private Internet Access, been happy with them getting about 100-120 mbit throughput.

Gonna move from pfsense to sophos utm so hope they support ipsec tunnels.

 

They don't (unless that recently changed) which was why I went with pfSense instead of Sophos UTM myself even though I use Sophos at work.  I'm currently testing out AirVPN though since I can't port forward Plex statically through PIA.

Link to comment

Ah so you can only use the OpenVPN-AS docker as a VPN server not as a client to create a tunnel for your entire server to a VPN service?  I was hoping to use it as a client to create an always on tunnel to AirVPN so I don't have to configure pfSense for that.  That way my unRAID server (and any of the additional dockers) would transmit through that tunnel while all other traffic on my network goes out my regular WAN.  Can this be done or should I just leave that type of config to my pfSense box?

 

 

Have you been able to port forward Plex on air

 

Nope not possible, OpenVPN-AS, AS as in Access server  :P

 

Binhex have a fwee dockers with vpn support, other that that i dont know.

 

I run pfsense for that myself, just NAT the ips that i want through the vpn(no NAT rules for them over my regular wan interface) and block them with outgoing firewall rules through the regular wan interface for no dns leakeage.

(use dns servers that keeps no logs).

 

//mace

 

What VPN service do you use?

 

Private Internet Access, been happy with them getting about 100-120 mbit throughput.

Gonna move from pfsense to sophos utm so hope they support ipsec tunnels.

 

They don't (unless that recently changed) which was why I went with pfSense instead of Sophos UTM myself even though I use Sophos at work.  I'm currently testing out AirVPN though since I can't port forward Plex statically through PIA.

Link to comment

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.