activ

Just in case anyone else runs into this: Docker uses another IP range inside the container. If you don't want to allow all IP's just whitelist your LAN and the docker internal range.

Did you try updating from within the apppication en restarting the docker after? Might be the updated fails to restart due to the lack of a normal init system.

Maybe you could remove it and reinstall, then disable auto update.

I actualy had that issues too, it seems to be a weird transmission bug thing. I just did the settings in the config in the file and left it at that.

Don't worry about it. We all started sometime.

Would probably have been better to leave the post, now the thread has gone weird. Anyway, glad you got it sorted out.

Are you installing on Unraid? Using my repo or another way? I guess you need to correct some stuff if you are running the command manually some stugg I notice in the command you pasted: Where it says: VPN_PROV="pia|airvpn|custom" you will need to choose one. WHITELIST="192.168.*.*" Should be changed to reflect your setup (WHITELIST="10.*.*.*") VPN_USER="vpn username" -e VPN_PASS="vpn password" need to be set I specifically think the pipe sign in VPN_PROV is causing your issue.

The settings file should be in your appdata share under activ-transmissionvpn. I personally like using transmission remote on my Mac to control transmission.

If you set the container variable named WEB_PASSWD to whatever you want (but within what flexget will accept) that should be your password.

Updated it this morning.

Update februari 2018: I no longer have the possibility to keep supporting this docker. If anyone wants to take over please feel free, grab my stuff from GitHub and make your own. I will leave the current state online, because I know people are using it. Overview: Support for Docker image arch-flexget in the activ repo. Application: Flexget - http://flexget.com Docker Hub: https://hub.docker.com/r/activ/arch-flexget GitHub: https://github.com/activ/arch-flexget Credit: I am using the base image made by Binhex, so most of the work was done by him.

Thanks, I didn't think of doing that. Will do it when I do an update for something else too, don't want everyone getting an update notification just because I added a url.

Hah, I did not know that. Thanks

Hey Binhex: Is this something that's in your base image? I was thinking I'd build in the option to use a proxy in some other images, but if it's in your base I won't need to.

Hey, I was wondering if it's possible to have this use the privoxy in one of your vpn dockers. Any experience with that?

I put the Git package in for now to get rid of the error message. Not a very clean solution, but at least it works. The update is already pushed, if you update the docker image the error should be gone.

Yes, that's expected. It's caused by now using git for the installation. My first version used git and didn't have this error, but using git in docker is actually not good practice (as noted by Binhex earlier). It's safe to ignore the message as it only prevents updates and doesn't impact anything else.

Hey, I was doing some testing and built this: https://hub.docker.com/r/activ/debian-neubot/ I'm not sure if I can maintain this long term, but feel free to grab it. Let me know if it works.

No problem, glad you got it working.

Just had a quick look to see if I could get it to work and you need port 58846 and the username/password from the auth file (I did test with the non vpn version so I could be quick).

cool, one other thing you might want to consider is switching from building images locally to getting dockerhub to do the building, this has the advantage that you keep your build env off your environment, as well as people then being able to see the output of the build on dockerhub, not to mention support for tags too. so you can hook github and dockerhub together, and you then set it to auto trigger a build on any github commits or you can set dockerhub to manual trigger, i would advise the second option as this then gives you control to add in tags in dockerhub. tags are important and allows the users to roll back incase of either a bad build or an issue with the app, i basically tag all my releases with <aur release>-XX where XX is a numeric indicating my build count for that version, e.g. for lazylibrarian the tag for first build would be 736.d66f7e9-1-01, this is a funny one as its a github build number so its a bit more cryptic, but you get the idea :-). just to be clear when under heavy dev i would advise building locally until you are confident enough to push it to github and build using dockerhub, building locally is still faster than building on dockerhub. Sounds cool, I'll look into that.

Hey, I'm not sure what you mean. Are you saying you are trying to have LazyLibrarian connect to the deluge in your other docker? No, I have not tested that. Don't really see why it would be an issue though. If the deluge is the one with vpn in it, maybe the iptables firewall is the one blocking things (there are several ip ranges involved). If you can give me a better picture of what you are trying to do I'll try and give you some troubleshooting tips.

I've now also done the switch from git to AUR,the update has been pushed to the docker repo.

You mean you would set a variable selecting Transmission or Rutorrent etc? I'm not sure how that would work, the way I see it Dockers need to be as light weight as they can. Installing three pieces of software and then using only one isn't really light weight. Also, what would the advantage be? The way it is now you can run one of them or all of them at the same time as you want. A big wish for me is to have the Openvpn and torrent dockers seperated so you don't need to run the vpn several times, but I highly doubt I'll be able to do that and not break compatibility with the Unraid UI.

Thanks, tips are very welcome. No.1 is done and I'll have a look at number 2 when I get some time. I'm still getting my bearings on Arch, so I'll do some testing with Aur before changing anything.