Bungy

Please check the documentation located here: https://github.com/jshridha/docker-nzbgetvpn If you can't figure out what to change, please post back and I'll try to help.

@Katherine I pushed a build that bumps nzbget to v20.0, updates the baseimage, and adds in the packages you need. With the updated baseimage, the setup for the VPN has changed. Please check the docs for setup info. It may take 10 minutes or so for the build to finish.

@Katherine In the meantime, try out this Dockerfile for adding in those packages: FROM jshridha/docker-nzbgetvpn:latest RUN pacman -S python2-requests-oauthlib python-requests-oauthlib \ python2-markdown python-markdown \ python2-decorator python-decorator That should get you the dependencies into python2 and python3 that you requested. Good luck and feel free to ping me if you notice nzbget get into archlinux's package manager. I don't always do the best job of keeping a close eye on those

The new NZBGet hasn't hit the archlinux repo yet: https://archive.archlinux.org/packages/n/nzbget/ Once it gets in there, I'll trigger a rebuild and get NZBget updated. I'll also try to include those packages. I'm not sure what their equivalents are in archlinux.

I saw that. I'll push an update to the docker container soon.

pwgen doesn't exist on unraid. You may have to run that command from within a Ubuntu docker container or another container that has that command. Sent from my SM-N950U using Tapatalk

@Katherine I decided to go ahead and include python3. You're not the first user that requested it, and more things are moving towards python3 so it's definitely warranted. Give it about 10 minutes for the build to finish and then pull down the new image. Revert your shebang back and you should be good to go.

Post the script and I'll take a look. Otherwise, it may just be easiest for me to include python3 in and you can reset your shebangs to the original.

The issue is that python2 is installed, but python3 is not. If your scripts are compatible with python2, the easiest fix will be to change the shebang in your scripts to point to /usr/sbin/python2. Otherwise, I'll have to include python3 in the container. Let me know if you need python3 and I'll be happy to include it.

No, you will need to provide your own certificates if you would like to use this option. The docker does not generate certificates by default. This shouldn't be hard to accomplish though. There's plenty of tutorials out there on how to use openssl to generate certificates.

The top of your logs are cut off. What do you have LAN_NETWORK set to and what is your unraid server's ip address?

That's the problem. LAN_NETWORK should be set to 192.168.0.0/24 if that is your IP address. Make that change and you should be able to connect.

This is a common symptom of trying to access the docker container from a machine that is not on the LAN_NETWORK subnet. Can you verify the ip address of the machine you're trying to connect from? Can you also exec inside of the container and verify it is connected to the VPN?

Build with version 18.1 is up and running. I'll update to 19.0 as soon as it hits the arch repository.

My goal is to update to 18.1. However, this requires an update to openssl libraries, which ends up breaking lots of binaries that require the older openssl version. I haven't had the time to sort out all the packages required to update, but I'll take a look again shortly. Keep poking me because I may forget!

I pushed a new commit that fixed the issue yesterday. Feel free to post here or on the github issue if you have any more problems.

The problem isn't the upgrad to unraid. The problem is you recreated the container so the /home/git/data directory is now missing. It seems your config is missing the directory mapping for /home/git/data. You'll have to manually map /home/git/data in the container to /mnt/user/appdata/gitlab on the host for example to get persistent storage to work. The template should have handled that for you, but maybe you changed the default settings?

This seems to be an issue to take up with the official owncloud team for their docker image. I only wrote the template and not the container. Alternatively, you can use these commands to install smbclient: docker exec -it owncloud bash apt-get update apt-get install -y smbclient exit Keep in mind that your apps will disappear unless you manually persist their storage on your unraid server. Also, the above commands will have to be re-done every time you recreate the container. The owncloud container wasn't designed to use the external storages plugin. I'd suggest you use docker volume mapping instead to provide similar functionality.

I'm out of ideas. Can you get me remote access to your server and I'll dig into it more? A ssh terminal, TeamViewer, gotomeeting, or something like that will work. Ssh terminal is preferred. Sent from my Nexus 5X using Tapatalk

Try changing the VPN address to uk-london.privateinternetaccess.com Sent from my Nexus 5X using Tapatalk

Either one will work, so let's go with tower ip address Sent from my Nexus 5X using Tapatalk

What is your LAN network IP address and subnet mask? Also try adding in the parameter: ENABLE_PRIVOXY=no Sent from my Nexus 5X using Tapatalk

The docker is still supported, just my time for support is now more limited. Can you post your full config? My guess is that there is a parameter that isn't set. Likely the parameter for the LAN_NETWORK. If you're used to looking at docker-compose setups, here's my config. You can probably easily tell which environmental variables you'll need to change to get it to work. nzbget: restart: always image: jshridha/docker-nzbgetvpn privileged: true volumes: - /mnt/disks/external/Downloads:/data - /mnt/disks/external/appdata/nzbgetvpn/config:/config - /etc/localtime:/etc/localtime environment: - VPN_ENABLED=yes - VPN_USER=USERNAME - VPN_PASS=PASSWORD - VPN_REMOTE=us-east.privateinternetaccess.com - VPN_PORT=1198 - VPN_PROV=pia - VPN_PROTOCOL=udp - ENABLE_PRIVOXY=no - LAN_NETWORK=192.168.1.0/24 - STRONG_CERTS=no ports: - "6789:6789"

It depends which container you're using. I don't believe you can if you're using Linuxserver's container. They generally design their containers to be single container deployments. You can use external databases when using Clue's container. Check here for documentation: https://github.com/clue/docker-ttrss Sent from my Nexus 5X using Tapatalk

I want to say I saw the same problem but my memory may be failing me. Try to shutdown the machine, remove all but one ram disk, and try again. That worked for me on my 6gb system. Sent from my Nexus 5X using Tapatalk