binhex
-
Posts
7,921 -
Joined
-
Last visited
-
Days Won
38
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by binhex
-
-
Just a FYI for PIA users:
There was a vulnerability that allowed IP address to be leaked when port forwarding is enabled: https://www.perfect-privacy.com/blog/2015/11/26/ip-leak-vulnerability-affecting-vpn-providers-with-port-forwarding/
PIA seems to have patched servers to fix the problem and nothing further needs to be done for OpenVPN users: https://www.privateinternetaccess.com/forum/discussion/comment/34571/#Comment_34571
Users who connect through the PIA client should update to the latest clients (v.53) released today: https://www.privateinternetaccess.com/forum/discussion/19391/updated-mac-windows-and-linux-clients-v-53-released#latest
Just so nobody looses sleep over this, delugevpn users are pretty much impervious to this attack, as the attacker requires you to go to a website or other url whilst connected to the vpn tunnel in order to get the victim to use the new port forward and thus packet sniff for the real ip of the victim. As delugevpn is a docker container running ONLY deluge, openvpn, and privoxy and not a full blown Linux OS running X then this is fairly unlikely, quote from one of the websites:-
- Attacker activates Port Forwarding on server 1.2.3.4, example port 12345
- Attacker gets the victim to visit 1.2.3.4:12345 (for example via embedding <img src=”http://1.2.3.4:12345/x.jpg”> on a website)"
The other thing to bear in mind is the ip of the docker container will be the internal Docker NAT, so it wont be your real ip but a 172.16.x .x ip and thus the attacker would have to deal with another level of security in order to get identifying information out of the running container, im personally not worried by this at all, esp as PIA have now also patched their server side.
-
I can't seem to create a delugevpn container.
After configuring my settings and then hitting create nothing happens. I've added other containers just to see if the problem was on my end and they worked fine.
Anybody know what the issue is?
I too am having the same problem when trying to create a delugevpn container as well.
im going to need more info than this guys, what errors are you seeing if any?, screenshots of what your seeing would be great.
I personally get no errors, infact I get nothing at all.
I click create, but nothing happens. It's like the link is broken/dead.
I have same issue. No problem for other containers. I let it wait for like an hour after clicking create button. Nothing happens. Any solution?
I as well let it sit for over an hour. Nothing.
hi guys, just for my own peace of mind i deleted my running container and image and pulled down delugevpn twice in succession with no issues, the image pulls down and the container is created so not sure what is going on here.
ok lets try and get some more detail on this, everybody with this issue please reply to the following questions:-
1. when you click the create button does ANYTHING happen?, as in a box, a window, a text box, or are you saying its as if you didnt click on the "create" button at all?.
2. how full is your docker image file, it could be the case the image file is full in which case you cannot download an further images until this is fixed.
3. if you ssh into unraid and do a ping to www.google.com can you get a reply?, this just proves name resolution is functional.
4. can you tell me what version of unraid your running.
5. have you ever been able to pull down delugevpn before or is this the first attempt?.
6. are you using the unraid "Community Applications" plugin to pull down the delugevpn image?.
If all else fails can you try stopping docker completly, delete the docker image and re-pull down the images again, please note you still can use your defined container settings, these are in the "[ templates-user ]" dropdown when you click on "Add Container" button.
-
Please update the Plexpass docker.
The last Update implemented a faulty disk space check and thus broke transcoding.
Seems there was a fix released today.
done.
-
I can't seem to create a delugevpn container.
After configuring my settings and then hitting create nothing happens. I've added other containers just to see if the problem was on my end and they worked fine.
Anybody know what the issue is?
I too am having the same problem when trying to create a delugevpn container as well.
im going to need more info than this guys, what errors are you seeing if any?, screenshots of what your seeing would be great.
I personally get no errors, infact I get nothing at all.
I click create, but nothing happens. It's like the link is broken/dead.
OK, i think what your seeing is a known unRAID bug, ive actually commented about this in the bug report raised in the defect section, but no action forthcoming yet, feel free to nudge jonp about this :-P
http://lime-technology.com/forum/index.php?topic=43303.msg413896#msg413896
so the fix for this is patience, it can take up to 5 mins to download the image, depending on the speed of your connection, so click on the create container and sit tight, if it is this particular bug then you will eventually see the window refreshes and you will see success at the bottom, let me know the outcome.
-
Has anyone gotten newshosting VPN working with Deluge??
yes it should work, basically as long as you can get hold of a openvpn configuration file (extension normally .ovpn) then you should be good to go, instructions on how to configure for newshosting vpn as follows:-
1. Download the ovpn file for your choosen endpoint from http://www.newshosting.com/vpn/software/configs/
2. Configure DelugeVPN Port Mappings and Volume Mappings as desired
3. Configure DelugeVPN environment variables as follows:-
VPN_REMOTE - Not required, as this is a custom provider VPN_USER - Username as provided by your VPN provider VPN_PASS - Password as proviuded by your VPN provider ENABLE_PRIVOXY - Either "yes" or "no", your preference VPN_PORT - This is the port specified in the ovpn file after the "remote <hostname>", normally 1194 VPN_PROV - This is the VPN provider, as this is not AirVPN or PIA we set this to "custom" VPN_ENABLED - Set this to "yes" LAN_RANGE - Set this to your internal home lan range, allows other applications to talk to the Deluge daemon
4. Start DelugeVPN to create folders under /config
5. Stop DelugeVPN, then paste the earlier downloaded ovpn file into /config/openvpn/
6. Start DeliugeVPN and monitor supervisord.log file in /config
7. Optionally go to the website http://torguard.net/checkmytorrentipaddress.php and follow the instructions to verify the VPN tunnel is working
-
I can't seem to create a delugevpn container.
After configuring my settings and then hitting create nothing happens. I've added other containers just to see if the problem was on my end and they worked fine.
Anybody know what the issue is?
I too am having the same problem when trying to create a delugevpn container as well.
im going to need more info than this guys, what errors are you seeing if any?, screenshots of what your seeing would be great.
-
So, my question is : How to integrate the delugeVPN to Couchpotato ??
Ugh. I was having the same issue and eventually gave up and used a black hole directory. But because of your post I looked at it again and got it to work!
You have to:
1) Enable remote connections to the daemon in Deluge (Preferences->Daemon->Allow Remote Connections)
2) Restart Deluge
3) In CouchPotato specify the host as <unRAID server IP>:58846
4) In CouchPotato get the username/password from the 'auth' file in the deluge app directory (the format of the auth file is username:password:permissions)
Tried all of that, still same error
The Auth file has this for credentials : localclient:34646yergsgwe6362246246:10 (pwd I randomely here). I tried using user: localclient and password: 34646yergsgwe6362246246
So it seems to not work. When you said "Restard Deluge", you mean Stop and Start the Docker ?
just to be clear, your auth file should look something like this:-
localclient:c5eaa1234587cc9d075e55829d72779b9a04f:10 admin:<my password>:10
so the second line is the one your interested in, this contains the username and password you would enter into couchpotato, if you dont see this line then im guessing its probably because the option to "allow remote connections" isnt ticked, or the delugevpn container hasnt been restarted.
-
+1 for the above, I understand the convenience of auto updates, but I think it can come at quite a high price, the dockers I produce will never include code to auto update.
-
just incase anybody is interested, the way i configure the transcode directory for the plex and plex pass images i create is simply to set the environment variable to point at the chosen folder, in this case i just create a tmp folder under /config and get it to store temporary transcode files in there, link to (old) article showing this:-
https://support.plex.tv/hc/en-us/articles/200273978-Linux-User-and-Storage-configuration
as for tracking down unruly docker containers, i did once have to debug an issue with miniDLNA creating a VERY large log file inside the container, one of the techniques i used to track it down was to search the loopback mounted docker image for large files:-
find /var/lib/docker/btrfs -type f -size +50000k -exec ls -lh {} \; | awk '{ print $9 ": " $5 }'the above will display all files 50MB or larger, the container id is shown in the path, as well as the file system in the docker container, with a bit more work somebody could easily map the container id in the path to the friendly name of the container for a more human friendly result :-).
Thanks Binhex, I used this command to find anything over 1GB. The container that starts with e93 is binhex/sonarr, but I am unable to find any dockers that start with 92e. Is there something I am missing here? I am searching by using docker ps -a command.
/var/lib/docker/btrfs/subvolumes/92e0d85384a0b19ed2dc7c91e6c2471f66d7f08b1c4905c642ee6c09a3e34b12/The: 993M
/var/lib/docker/btrfs/subvolumes/92e0d85384a0b19ed2dc7c91e6c2471f66d7f08b1c4905c642ee6c09a3e34b12/The: 1.2G
/var/lib/docker/btrfs/subvolumes/92e0d85384a0b19ed2dc7c91e6c2471f66d7f08b1c4905c642ee6c09a3e34b12/The: 2.8G
/var/lib/docker/btrfs/subvolumes/92e0d85384a0b19ed2dc7c91e6c2471f66d7f08b1c4905c642ee6c09a3e34b12/The: 2.7G
/var/lib/docker/btrfs/subvolumes/92e0d85384a0b19ed2dc7c91e6c2471f66d7f08b1c4905c642ee6c09a3e34b12/The: 1.1G
/var/lib/docker/btrfs/subvolumes/e93e17d188f4b6ef2916abf382b43e3ed490c616477db527b15f846d8b80d56e/The: 2.7G
UPDATE: I looked for any files over 50M in that container and added up the files and I am already at almost 20G. This seems to be the culprit of my growing docker size. How can I find out what container this is?
UPDATE #2: Apparently this is a known issue with subvolumes not getting deleted properly. According to the following https://github.com/docker/docker/pull/15801 is should be fixed with Docker 1.9. Does anyone know if this will be in unRAID 6.2?
hmm interesting bug raised there, could explain growing unraid docker image size if a user is doing a lot of churn, i.e. creating and deleting docker containers, still doesnt cover the case where people are seeing usage grow whilst not doing any creation/deletion of containers (just to be clear im NOT seeing this <-).
-
https://github.com/binhex/arch-patches/releases/download/scheduler-0.2-py2.7/Scheduler-0.2-py2.7.egg
ive not currently had time to test this yet so im looking for feedback on whether this now works as expected, so please post back with your results.
Thanks so much for the quick fix! I'm testing it now and it seems to be working fine. I'll post again if I run into any problems.
Thanks again for all your work binhex, it's really appreciated.
EDIT: I just checked and the latest MyScheduler plugin also appears to include the fix to core.py. MyScheduler is basically the standard scheduler with an option to force selected torrents to download, regardless of the scheduler (very handy).
thanks for the link to MyScheduler, always nice to have options eh :-).
p.s im nicking your instructions for how to connect couchpotato and delugevpn together and putting it in a FAQ, think this question has been asked enough times to warrant it :-), one step missed out though is to make sure you define the lan range via the env variable for delugevpn, otherwise if you try to connect a non docker instance of couchpotato it wont work.
-
I updated my mainserver to 6.1.4. Saw much lower parity check speeds immediately after reboot. The M1015s in my server after comparable to the H310 I think. Should I enter mdcmd set md_sync_thresh -1 from the command-line?
M1015 should be the same as H310.
Go to > settings > disk settings and check you md_sync_window value, default is 384.
Use that value-1 for md_sync_thresh, for the default value would be:
mdcmd set md_sync_thresh 383
im assuming the value for this setting is written to the flash drive yes?, as in it will be persistent and doesn't require re-applying on boot?
-
i found this issue on Docker's github:
https://github.com/docker/docker/issues/3182
is this related?
no, we are using btrfs, not devicemapper, and what brit said :-)
-
Has anyone tried this possible fix for the Deluge scheduler issue?
http://forum.deluge-torrent.org/viewtopic.php?f=9&t=52553
hi death.hilarious, thanks for the link!, had a good look at the code and doing some testing at the moment to see best way to include the patch.
ok so it looks like the scheduler plugin for deluge is packaged as an egg file (basically a zipped python module), i looked at patching the script and then rezipping but for some reason deluge wouldnt pick it up as a default plugin, maybe some md5 checks are done, not sure.
so in the end ive gone with the approach of remove the faulty plugin altogether and pushed up a patched egg that can be manually installed. so please download the latest docker image with tag latest, then once up and running go to preferences/plugins and download and install the scheduler plugin, link to the download here:-
https://github.com/binhex/arch-patches/releases/download/scheduler-0.2-py2.7/Scheduler-0.2-py2.7.egg
ive not currently had time to test this yet so im looking for feedback on whether this now works as expected, so please post back with your results.
-
Has anyone tried this possible fix for the Deluge scheduler issue?
http://forum.deluge-torrent.org/viewtopic.php?f=9&t=52553
hi death.hilarious, thanks for the link!, had a good look at the code and doing some testing at the moment to see best way to include the patch.
-
regarding delugevpn:
1. Is there a killswitch built in such that internet connection gets cut off if VPN loses its connection?
2. Is there an autorestart for deluge and openvpn in case the daemon crashes?
hi Nem, replies as follows:-
1. there is no killswitch as its not required, im using iptables instead to prevent any ip leakage if the vpn tunnel was to go down, you can test this yourself by jumping into the running container and killing the vpn process, you will see tjhat dl/ul speeds drop to 0.
2. thee is an autorestart for the vpn tunnel if it goes down, its a bit harder to code for a crash of deluge, as things need to start in the right order, on the plus side i have found deluge quite stable and have yet to see a crash once its running.
-
just incase anybody is interested, the way i configure the transcode directory for the plex and plex pass images i create is simply to set the environment variable to point at the chosen folder, in this case i just create a tmp folder under /config and get it to store temporary transcode files in there, link to (old) article showing this:-
https://support.plex.tv/hc/en-us/articles/200273978-Linux-User-and-Storage-configuration
as for tracking down unruly docker containers, i did once have to debug an issue with miniDLNA creating a VERY large log file inside the container, one of the techniques i used to track it down was to search the loopback mounted docker image for large files:-
find /var/lib/docker/btrfs -type f -size +50000k -exec ls -lh {} \; | awk '{ print $9 ": " $5 }'the above will display all files 50MB or larger, the container id is shown in the path, as well as the file system in the docker container, with a bit more work somebody could easily map the container id in the path to the friendly name of the container for a more human friendly result :-).
-
1
-
-
Weird it looks like there's still an exception on the new build too: https://hub.docker.com/r/binhex/arch-plexpass/builds/bjnwwuqkm2qj3f8xbhg5qng/
wonder what's up
looks like docker hub is properly stuffed right now, im getting no build output for one of the repositories, and a VERY strange exception error message, with what looks like a python traceback shown at the top of the page for another repo, not impressed!. fingers crossed the devs will get this sorted asap and i can kick off the some builds for you guys, in the meantime sit tight, eat popcorn and watch a movie :-).
for the interested, here are the issues:-
https://github.com/docker/hub-feedback/issues/457#issuecomment-155564021
https://github.com/docker/hub-feedback/issues/455#issuecomment-155563190
ok updates on the above, so the empty console output issue continues with the base image, but its not a blocker so for now ive logged the issue with docker hub and let them deal with it. The other issue showing an exception is actually a bug in the build, basically their bug tracking system looks a bit screwed right now but it did highlight an issue, the issue was eventually tracked down to a problem with the latest version of sudo, rolled backed a version and its all fixed now.
so back to the initial problem that sparked all this, plexpass is currently sitting in the docker hub queue waiting to build, once its built then plexpass will be up to 0.9.14, with yet another version coming once it shows up in AUR.
-
Weird it looks like there's still an exception on the new build too: https://hub.docker.com/r/binhex/arch-plexpass/builds/bjnwwuqkm2qj3f8xbhg5qng/
wonder what's up
looks like docker hub is properly stuffed right now, im getting no build output for one of the repositories, and a VERY strange exception error message, with what looks like a python traceback shown at the top of the page for another repo, not impressed!. fingers crossed the devs will get this sorted asap and i can kick off the some builds for you guys, in the meantime sit tight, eat popcorn and watch a movie :-).
for the interested, here are the issues:-
https://github.com/docker/hub-feedback/issues/457#issuecomment-155564021
https://github.com/docker/hub-feedback/issues/455#issuecomment-155563190
-
Is it possible to rev the PlexPass Docker to 0.9.12.19.1537? It appears there have been some improvements to Apple TV support. Thanks!
already done, try a pull down of the new image odd looks like the build didnt complete, im currently looking into this...
-
Hi there,
on my SickRage setup, snatched nzbs are not being sent to sabnzbd since updating to the latest build 1 hour ago.
Just wondering if this is a general sickrage issue, or in any way related to the docker build.
In the log, i can see the following block, after a nzb has been snatched.
AANameError: global name 'datetime' is not defined
AA if datetime.date.today() - curEp.airdate > datetime.timedelta(days=7):
AA File "/opt/sickrage/sickbeard/sab.py", line 58, in sendNZB
AA dlResult = sab.sendNZB(result)
AA File "/opt/sickrage/sickbeard/search.py", line 120, in snatchEpisode
AA search.snatchEpisode(result)
AA File "/opt/sickrage/sickbeard/search_queue.py", line 226, in run
2015-11-03 17:24:58 INFO SEARCHQUEUE-BACKLOG-296295 :: [###indexer###] :: Downloading ##episode name here### from https://###indexer###.com
thats a bug in sickrage, looks like they stuffed up on reference to the datetime python module, i would expect this to be fixed pretty quickly, as soon as they drop a new release i will trigger a build, will post here when that happens
-
OK, updated to Plexpass and it says I need to update to 0.9.12.18 manually, i'm currently running 0.9.12.17. Any idea?? Is that just because you didn't update the docker yet?
Restart the Plex Docker container and check if it updates. If not, you need to wait for the maintainer of the container to update to the latest version. See FAQ in first post.
As per the FAQ in post #2 none of the dockers i create automatically update on restart, reasons for this are detailed in the FAQ. I have kicked off an update of the image for both plex and plexpass editions, please force a check at your convenience and you should find it bring you up to date.
-
I'm having a problem with btguard. I tried to search but I'm not finding the right info.
I am using deluge and I had btguard working and then I removed the container to change things up as I was learning my way around shares etc. now my btguard test torrent says my ip is not being protected. I tried removing all files from app data and reinstalling every different docker image of deluge to no avail. Is there maybe something that is getting left over somewhere besides the appdata folder?
any thought?
asrock extreme 11ac
i7 4770
wd green 4tb x 3
crucial 500gb sad cache x 2
corsair voyager 16gb flash
dockers - plexpass + deluge
please can you post your supervisord.log file, i will also need a copy of your ovpn file, please make sure you remove any usernames and passwords, im assuming your using the delugevpn docker right?
-
Hi! I'm having some issues with DelugeVPN. I have it setup so when a torrent finishes downloading it is move to a "Completed" folder. My problem is that when a torrent finishes, it will cause all of the other torrents to stop downloading for a little while(About a minute maybe). Do you think this is possibly a problem with me not having a cache drive? Is there any log I can look at to see what's happening exactly? The log you can pull up from the unRaid webUI when clicking on the docker does not show anything when the torrents all pause. Any ideas on how to fix this would be great! Thanks!
hi holbert, this MAY be related to the fact you don't have a cache drive, in as much as if you are running your docker containers off the array and/or moving files/folders from different locations on the array then this MIGHT cause some interruption due to IO saturation on write. if you can afford the luxury of a cache drive then i would recommend it, it will mean lower power consumption for you, as you can leave your array drives spun down, as well as giving you potentially the speed boost when writing (writes to cache then moves).
-
Thanks for letting me know its working guys, very pleased I can tick this off :-)
[ARCHIVE] binhex docker repository
in Docker Containers
Posted
ok question 6. is the interesting one, i think i would probably put good money on the Community Applications plugin being the issue here, not sure why its playing up for this particular docker image but i think thats probably the culprit.
can you try not using the plugin and instead pull it down using the procedure in post #1 "installation", if it does then you will need to drop by the Community Application thread and let them see if they can help figure out what is going on (sorry i dont currently use the CA plugin).