[ARCHIVE] binhex docker repository


Recommended Posts

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?

Link to comment

I'm seeing this warning in the delugevpn log file:

 

2015-11-29 16:20:42,310 DEBG 'deluge' stdout output:

[warn] PIA incoming port is not an integer, downloads will be slow, check if remote gateway supports port forwarding

 

Is this normal? Or is there a way to fix it?

Link to comment

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.

Link to comment

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.

 

Link to comment

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

Link to comment

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.

Link to comment

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.

 

Hello!

 

1.) It's like I never clicked it.

 

2.) I'd love to tell you, how do I check!?

 

Is this it?

 

Docker volume info

btrfs filesystem show:

Label: none  uuid: c26ba06a-73b2-4c1f-b5e3-00e88824ac3a

Total devices 1 FS bytes used 4.85GiB

devid    1 size 10.00GiB used 7.79GiB path /dev/loop0

 

btrfs-progs v4.1.2

btrfs scrub status:

scrub status for c26ba06a-73b2-4c1f-b5e3-00e88824ac3a

no stats available

total bytes scrubbed: 0.00B with 0 errors

 

3.) --- www.google.com ping statistics ---

15 packets transmitted, 15 received, 0% packet loss, time 14019ms

rtt min/avg/max/mdev = 8.364/9.980/18.681/2.423 ms

 

4.) unRAID 6.1.3

 

5.) I can't remember, but I think, and that's a big maybe, I pulled it before.  I know for sure I pulled and installed Deluge then removed.  (Whichever one it was I removed it via the Remove function from the unRAID dashboard and selected remove container and image)

 

6.) Yes

 

Let me know if there's anything else I can help with for troubleshooting.

Link to comment

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.

 

1. Nothing happens.  No pop-up window or anything like that.  It's like dead link.

 

2. 7 gb out of 10 gb.  I increased the image size to 15 gb and try it again.  Still nothing happens.

 

3.  Working properly.  Able to get ping response from www.google.com.

 

4. version 6.1.4

 

5. First attempt to download DelugeVPN.  I was able to pull your Deluge image but not DelugeVPN which I want.

 

6.  Yes.

 

7. Still not working......I was able to re-pull all other images including your Deluge but not DelugeVPN.

Link to comment

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).

 

 

Link to comment

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).

You dont use CA?  Sacrilege...

 

You can bypass CA by either doing things thw old fashioned way of using repositories, or hitting Update Applications which will temporarily force CA to to download the actual template instead of creating one from the appfeed.  Either way let me know how it goes

Link to comment

You dont use CA?  Sacrilege...

 

i know squid, spank me now :-), its no reflection on CA, its just me, i like things as clean as possible, less plugins means less chance of issues thats all it is.

 

would be interested to find out why CA doesnt like delugevpn though, bit odd, the only thing i am doing that might be a little out of the norm is that im layering docker images, so delugevpn base image is actually my openvpn docker image, maybe thats tripping up CA?.

Link to comment

All CA does in normal mode is read the appfeed and create a template from it.  If you manually update the app list then it actually reads YOUR template.

 

After that it just passes thru the template to dockerMan to process.

 

I'll compare the generated template to yours tonight and see what the differences are (I do know that its never going to be the exact same, but then it'll come down to where is the issue - kode's feed or my generation.  We'll get it sorted out

Link to comment

I had a look at my generated XML, and its basically identical to your raw template (just different spacing).

 

However, on a quick glance through the thread, it appears that if you just click create CREATE it does nothing.  This is true.  The reason is that there is no value already set for the LAN_RANGE environment variable.  If you hit advanced, then CREATE, you'll see that there is an error message popping up prompting you to fill out that field prior to commencing.

Link to comment

I had a look at my generated XML, and its basically identical to your raw template (just different spacing).

 

However, on a quick glance through the thread, it appears that if you just click create CREATE it does nothing.  This is true.  The reason is that there is no value already set for the LAN_RANGE environment variable.  If you hit advanced, then CREATE, you'll see that there is an error message popping up prompting you to fill out that field prior to commencing.

This behaviour is proper, in a way. There is no way to utilize the VPN part without filling out the advanced fields, so refusing to work if the user hasn't completed the forms is to be expected. The error handling should be changed to reflect missing information instead of invisibly failing though. I think that is something that has to be handled by the docker gui. It should give the missing info error message regardless of whether or not the advanced fields are currently visible.
Link to comment

I had a look at my generated XML, and its basically identical to your raw template (just different spacing).

 

However, on a quick glance through the thread, it appears that if you just click create CREATE it does nothing.  This is true.  The reason is that there is no value already set for the LAN_RANGE environment variable.  If you hit advanced, then CREATE, you'll see that there is an error message popping up prompting you to fill out that field prior to commencing.

This behaviour is proper, in a way. There is no way to utilize the VPN part without filling out the advanced fields, so refusing to work if the user hasn't completed the forms is to be expected. The error handling should be changed to reflect missing information instead of invisibly failing though. I think that is something that has to be handled by the docker gui. It should give the missing info error message regardless of whether or not the advanced fields are currently visible.

This isn't the only container where that "feature" ( bug ) affects installation for new users

Link to comment

I had a look at my generated XML, and its basically identical to your raw template (just different spacing).

 

However, on a quick glance through the thread, it appears that if you just click create CREATE it does nothing.  This is true.  The reason is that there is no value already set for the LAN_RANGE environment variable.  If you hit advanced, then CREATE, you'll see that there is an error message popping up prompting you to fill out that field prior to commencing.

 

I see this behavior happening as well.

 

I will tr the install method in post #1 hopefully tomorrow and report back.  It's been a long 18 hour day today, and I'm finally done with business related stuff.  Wish I had the energy to test now but I can barely get this post written as is.

Link to comment

This behaviour is proper, in a way. There is no way to utilize the VPN part without filling out the advanced fields, so refusing to work if the user hasn't completed the forms is to be expected. The error handling should be changed to reflect missing information instead of invisibly failing though. I think that is something that has to be handled by the docker gui. It should give the missing info error message regardless of whether or not the advanced fields are currently visible.

 

This is not strictly true actually, you dont need to configure the LAN_RANGE if you arent going to talk to the deluge daemon from a non-dockerized application, for instance - couchpotato running on another host on your LAN WOULD require this defining, however couchpotato running as a container on the same unraid host wouldnt, but i dont think i can make this setting optional in the xml, or can i?

 

At the end of the day i agree with you squid, this is def a bug that should be addressed by LT, the user should be notified of missing configuration even if they havent chosen the advanced view option, silent failure is not good.

 

edit - i guess all i can do if you cant mark an env var as optional is populate it with something (common lan range) and then at least people wont get the silent failure

Link to comment

I will tr the install method in post #1 hopefully tomorrow and report back.  It's been a long 18 hour day today, and I'm finally done with business related stuff.  Wish I had the energy to test now but I can barely get this post written as is.

No need to.  This issue has nothing to do with CA (and will also appear if you manually enter the repository).  You're still going to have to hit "Advanced" on the create page no matter what
Link to comment

I will tr the install method in post #1 hopefully tomorrow and report back.  It's been a long 18 hour day today, and I'm finally done with business related stuff.  Wish I had the energy to test now but I can barely get this post written as is.

No need to.  This issue has nothing to do with CA (and will also appear if you manually enter the repository).  You're still going to have to hit "Advanced" on the create page no matter what

 

So if I'm understanding this correctly, in order to get the docker installed I need to select the Advanced option then define my LAN_RANGE?

 

If my local LAN is a 192.168.0 Subnet what's the best way to define this? 192.168.0.1/24? Or can I define the servers loop back itself since all is on the server itself? 127.0.0.1?  Or do I have to define a specific range? 192.168.0.1 - 192.168.0.95?

 

Or am I just totally confused?

Link to comment

I will tr the install method in post #1 hopefully tomorrow and report back.  It's been a long 18 hour day today, and I'm finally done with business related stuff.  Wish I had the energy to test now but I can barely get this post written as is.

No need to.  This issue has nothing to do with CA (and will also appear if you manually enter the repository).  You're still going to have to hit "Advanced" on the create page no matter what

 

So if I'm understanding this correctly, in order to get the docker installed I need to select the Advanced option then define my LAN_RANGE?

 

If my local LAN is a 192.168.0 Subnet what's the best way to define this? 192.168.0.1/24? Or can I define the servers loop back itself since all is on the server itself? 127.0.0.1?  Or do I have to define a specific range? 192.168.0.1 - 192.168.0.95?

 

Or am I just totally confused?

In order to get it installed, SOMETHING has to be in that field.  What goes in that field I have no idea
Link to comment

I will tr the install method in post #1 hopefully tomorrow and report back.  It's been a long 18 hour day today, and I'm finally done with business related stuff.  Wish I had the energy to test now but I can barely get this post written as is.

No need to.  This issue has nothing to do with CA (and will also appear if you manually enter the repository).  You're still going to have to hit "Advanced" on the create page no matter what

 

So if I'm understanding this correctly, in order to get the docker installed I need to select the Advanced option then define my LAN_RANGE?

 

If my local LAN is a 192.168.0 Subnet what's the best way to define this? 192.168.0.1/24? Or can I define the servers loop back itself since all is on the server itself? 127.0.0.1?  Or do I have to define a specific range? 192.168.0.1 - 192.168.0.95?

 

Or am I just totally confused?

 

format for the LAN_RANGE should be:-

 

<start ip address as 4 octets>-<end ip address as 4 octets>

 

e.g.

192.168.1.1-192.168.1.254

 

just be clear, snip from my previous post:-

 

...you dont need to configure the LAN_RANGE if you arent going to talk to the deluge daemon from a non-dockerized application, for instance - couchpotato running on another host on your LAN WOULD require this defining, however couchpotato running as a container on the same unraid host WOULD NOT require this defining...

 

So technically this doesn't need to be defined, BUT it looks like the unRAID webui as it currently is, requires this to be configured otherwise you get the behaviour your seeing with a silent failure to create the container.

 

edit - btw i have now included a ip range in the docker template so this shouldnt happen for any new users (sorry current users will need to still define this).

Link to comment
Guest
This topic is now closed to further replies.