MCU

That'd be exciting and welcome. I'm moving in November, so I might not get around to starting setting up my Pi stack until late December anyway.

OK, this is a bit of a stretch given its an unraid forum (and I don't actually run unraid), but I'm thinking about moving my stack to a Raspberry Pi, and thus an ARM processor. The RtorrentVPN Docker image is pretty key to my setup, and it's (reasonably) only available on amd64. Not experienced with building docker images, but from poking around on DockerHub/GitHub it looks like I could theoretically build one myself; all the source code is available. I *like* how easy the docker image is to manage and configure, but it looks like a lot of work to try to rebuild it for a different architecture. Looking at the source for things like root/install.sh, it appears that ARM support is there, the images just aren't ending up in DockerHub. So I guess this is a question for @binhex - is ARM supported? Since I'm a newb at building my own images, do I just checkout binhex/arch-rtorrentvpn from Github on a Pi running Arch, and then do a "docker build"? I probably need to check out the two upstream repos too (binhex/arch-int-vpn and binhex/arch-base). Or would I be better off just installing all of this stuff from scratch and running it directly on the host? Obviously, I lose some of the advantages of using docker, but... yeah. I dunno. Getting VPNs properly configured always flummoxed me, but I want to keep my production box lean and simple. Or maybe we could just get this docker image available for ARM on DockerHub? LOL

This was enough for me to figure it out. To document for others using VPN Unlimited, the configuration files you get from them don't specify VPN_PORT, and the container complains loudly. I, like an idiot, put in 443. That didn't work, and trying to start the configuration outside of the docker with and without that port confirmed it WAS the remote line. Setting the VPN_PORT in the config file to 1194 made everything right as rain. (Note, VPN Unlimited doesn't document available ports on their website, but I did find someone else who did; 443 was listed as supported, but clearly wasn't working. The default VPN port of 1194 did.) Thanks, binhex. Donation incoming.

So, I've been wrestling with this for a while with zero luck. I'm attempting to run the container on an Ubuntu 18.04 host, and with the VPN disabled it works. With the VPN enabled, it appears to never successfully connect. Ubuntu has no tun.ko module; however support for those interfaces is included in the kernel: $ dmesg | grep tun [ 2.297678] tun: Universal TUN/TAP device driver, 1.6 Basically, what I see is that the OpenVPN starts, but never gets a valid IP address. 2019-05-26T15:15:19.194876122Z [info] OpenVPN started 2019-05-26T15:15:19.194889755Z 2019-05-26T15:15:19.195350049Z 2019-05-26 11:15:19,195 DEBG 'start-script' stdout output: 2019-05-26T15:15:19.195364298Z [debug] Waiting for valid IP address from tunnel... 2019-05-26T15:15:19.195373706Z 2019-05-26T15:15:19.195854980Z 2019-05-26 11:15:19,195 DEBG 'start-script' stdout output: 2019-05-26T15:15:19.195870025Z Sun May 26 11:15:19 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]209.58.135.108:443 2019-05-26T15:15:19.195880028Z Sun May 26 11:15:19 2019 UDP link local: (not bound) 2019-05-26T15:15:19.195890919Z Sun May 26 11:15:19 2019 UDP link remote: [AF_INET]209.58.135.108:443 2019-05-26T15:15:19.195906454Z 2019-05-26T15:15:49.680951014Z 2019-05-26 11:15:49,680 DEBG 'start-script' stdout output: 2019-05-26T15:15:49.680982600Z Sun May 26 11:15:49 2019 [UNDEF] Inactivity timeout (--ping-exit), exiting 2019-05-26T15:15:49.680991231Z 2019-05-26T15:15:49.681155877Z 2019-05-26 11:15:49,681 DEBG 'start-script' stdout output: 2019-05-26T15:15:49.681192860Z Sun May 26 11:15:49 2019 SIGTERM[soft,ping-exit] received, process exiting Can anybody provide any help? VPN authentication is via a private key, redacted in the log. supervisord.log

So, it appears the VPN isn't working for me (everything works great with the VPN off, but with it on I get output like this roughly 30 seconds after OpenVPN is fired up: 2019-03-12 11:36:45,451 DEBG 'start-script' stdout output: Tue Mar 12 11:36:45 2019 [UNDEF] Inactivity timeout (--ping-exit), exiting 2019-03-12 11:36:45,451 DEBG 'start-script' stdout output: Tue Mar 12 11:36:45 2019 SIGTERM[soft,ping-exit] received, process exiting I'm connecting to VPN Unlimited, and I've tried using both username/password and a private key in my .ovpn file to connect. The .ovpn file was pulled forward from an old Docker file that is no longer supported and broke when I upgraded to Ubuntu 18.04 which worked perfectly. The only change I made to the OpenVPN config file was to add the port. Once I did that, it ran all the way thru to starting the VPN but still failed. Are there any things I could look at first? Should I upload a full log? I'm fairly competent with Linux, but OpenVPN remains a mystery to me.