Jump to content
binhex

[Support] binhex - DelugeVPN

4959 posts in this topic Last Reply

Recommended Posts

34 minutes ago, strike said:

That I don't know as I've never tried it. Moving the torrents it's the easy part, but you have to set the file location for each torrent then force a recheck to be able to pick up where you left of. I think I remember (vaguely) someone in this thread doing it, so you might find some info if you search (use the site option in google for better search then the forum). 

What is the default username and password for rtorrent?

Share this post


Link to post
13 minutes ago, Raczo said:

What is the default username and password for rtorrent?

I have no idea, I've never tried the rtorrentvpn container. But I bet you'll find it on the github page which is normally linked in the support thread.

Share this post


Link to post

I've got this Docker up and running, using Windscribe VPN. Downloading working fine, but I can't seed/upload at all. I've spent several hours searching this thread and trying various tips, but nothing has worked.

 

How do I find the IP and port to use on https://www.yougetsignal.com/tools/open-ports/ to confirm my port is accessible? Or is there a better preferred tool/method when OpenVPN is involved?

Share this post


Link to post
21 hours ago, binhex said:

not sure why its showing updates as i havent pushed anything for at least a couple of weeks+ (delugevpn 29 days), that aside deletion of the container is perfectly normal for an update, when you click on update in the unraid web ui what actually is happening is pull down of the new image, then deletion of the existing container, then re-creation of the new container, keep in mind no configuration should be contained within the container, its all volume mounted to the host via /config, so deletion of the container will mean no loss of config.

 

so without a screenshot of the commands executed during the update its hard to say why it couldnt re-create the container, im assuming its still in this stuck state right?, can you post a screenshot.

Resolved it. Seems the docker contain was getting full. Stopped docker and increased its size and all was good. Cant say an auto-delete of the container was great. A warning might have been better.

Share this post


Link to post
2 hours ago, darrenyorston said:

Cant say an auto-delete of the container was great. A warning might have been better.

That's not this docker's fault.  Do you not receive notifications when your container is getting full?

Share this post


Link to post
2 hours ago, Cessquill said:

That's not this docker's fault.  Do you not receive notifications when your container is getting full?

I did not say it was the containers fault. Try reading my post again.

 

Yes I do receive notifications. All updates are selected, as are all notices, warnings, and alerts. I did not receive a warning. My containers showed as "Update Ready". I updated the container and it deleted it. My only issue is that when I selected update it would have been preferable to be notified the container was going to be deleted. If it had I would not have selected update. Thankfully it was not something or greater value.

 

According to the O/S my containers total 11.9 GB. My container size was set 20GB when this occurred. As a consequence I raised it to 30GB. I have since raised it to 50GB so as to stave of similar issues in the future.

 

 

Edited by darrenyorston
expanded

Share this post


Link to post
8 minutes ago, darrenyorston said:

I did not receive a warning.

You did not receive a warning that your container was getting full?  If you did, that was your warning - that's what I'm getting at.  I understand that dockers removing or reporting false updates is frustrating, but there will be unexpected behaviour if you run out of space.  And since dockers don't store any config/data, there's no harm done.

Share this post


Link to post
13 minutes ago, Cessquill said:

You did not receive a warning that your container was getting full?  If you did, that was your warning - that's what I'm getting at.  I understand that dockers removing or reporting false updates is frustrating, but there will be unexpected behaviour if you run out of space.  And since dockers don't store any config/data, there's no harm done.

Let me try to make it clearer for you. I DID NOT RECEIVE A WARNING THAT THE CONTAINER WAS GETTING FULL. Furthermore, I would not call 12GB in a 20GB container "getting full". As I said I am not overly concerned that the container was deleted as it was easy enough to re-install. I am more concerned that clicking update caused the container to delete. Makes me hesitant to update any container.

Edited by darrenyorston
addition

Share this post


Link to post

OK.  Only trying to help - your container size information was not in your post when I initially replied.

Share this post


Link to post
Let me try to make it clearer for you. I DID NOT RECEIVE A WARNING THAT THE CONTAINER WAS GETTING FULL. Furthermore, I would not call 12GB in a 20GB container "getting full". As I said I am not overly concerned that the container was deleted as it was easy enough to re-install. I am more concerned that clicking update caused the container to delete. Makes me hesitant to update any container.
If you are worried about containers being deleted (you shouldn't be) then you cannot update any images, as doing so will always delete the existing container, that's how it's designed to work.

Sent from my EML-L29 using Tapatalk

Share this post


Link to post
26 minutes ago, binhex said:

If you are worried about containers being deleted (you shouldn't be) then you cannot update any images, as doing so will always delete the existing container, that's how it's designed to work.

Sent from my EML-L29 using Tapatalk
 

Yeah ive noted thats how containers update. I use quite a few of your containers and have never had an issue. As a result i thought nothing of updating the container. I was not surprised when it said the container was deleted. Only when it said it was finished. As i said not a huge issue with deluge as it takes only a few minutes to set up.

Share this post


Link to post
35 minutes ago, Cessquill said:

OK.  Only trying to help - your container size information was not in your post when I initially replied.

No problem.

Share this post


Link to post
1 minute ago, darrenyorston said:

No problem.

Out of interest, if you didn't receive a warning, and space in your container was ~8GB, why do you think it was full?  I get that the issue is solved now and you've resized, but just restarting the docker system (which you'll have done to resize) may have solved the issue

Share this post


Link to post
2 hours ago, darrenyorston said:

According to the O/S my containers total 11.9 GB. My container size was set 20GB when this occurred. As a consequence I raised it to 30GB. I have since raised it to 50GB so as to stave of similar issues in the future.

You probably have some issue with your app configuration and increasing it to 50G is only going to make it take longer to fill. It is very unlikely 20G would not be sufficient if you have things configured correctlly.

Share this post


Link to post
1 hour ago, darrenyorston said:

As i said not a huge issue with deluge as it takes only a few minutes to set up.

You can easily reinstall any docker without setting anything up simply by using the Previous Apps feature on the Apps page.

Share this post


Link to post

You should click on the Container Size button on the Dockers page. It will let you see how much space each of your containers is using.

Share this post


Link to post
8 hours ago, BBLV said:

I've got this Docker up and running, using Windscribe VPN. Downloading working fine, but I can't seed/upload at all. I've spent several hours searching this thread and trying various tips, but nothing has worked.

 

How do I find the IP and port to use on https://www.yougetsignal.com/tools/open-ports/ to confirm my port is accessible? Or is there a better preferred tool/method when OpenVPN is involved?

Do you have a windscribe static IP?

https://windscribe.com/features/port-forwarding

Share this post


Link to post
46 minutes ago, jonathanm said:

Do you have a windscribe static IP?

https://windscribe.com/features/port-forwarding

I do not. I didn't realize they offered paid services above the Pro VPN license that I purchased 2 years ago. That's pretty annoying....

 

Do I need their Static IP to be seen properly by the swarm? I have 5 torrents seeding now and only got very minimal uploading overnight. So I'm being seen, just not to a level that is productive whatsoever.

Share this post


Link to post
2 minutes ago, BBLV said:

I do not. I didn't realize they offered paid services above the Pro VPN license that I purchased 2 years ago. That's pretty annoying....

 

Do I need their Static IP to be seen properly by the swarm? I have 5 torrents seeding now and only got very minimal uploading overnight. So I'm being seen, just not to a level that is productive whatsoever.

You need the static IP (basic is OK, no need for the 2nd tier) and then, you'll setup on their website, the Port Forward manually, and it will give you a .ovpn file that you'll then use with this docker.

Share this post


Link to post
8 hours ago, trurl said:

You should click on the Container Size button on the Dockers page. It will let you see how much space each of your containers is using.

I did. Thats where the 11.9gb came from.

Share this post


Link to post

Should my Deluge "Incoming Port" match the port specified in my OpenVPN config file? i.e. OpenVPN has port 1194 and Deluge has port 58946. Could this be the cause of me not being very connectable?

Share this post


Link to post
On 2/15/2019 at 11:25 AM, strike said:

Please remove anything you have in the options variable and try again.

I got it to connect, but Newshosting doesn't allow port forwarding. I wish there was a way to attach a second NIC and route that way, but I'm at the limits of my Linux knowledge right now, with more pressing work projects to do unfortunately.

Share this post


Link to post

Hi everyone,

 

Maybe a stupid question, but can someone explain me why the eth0 and tun0 values diverge? Should't they kind be the same, since tun0 goes through eth0?

 

See attached image. This was from the binhex-delugevpn console.

 

Thanks.

eth0-vs-tun0.png

Edited by l3gion

Share this post


Link to post

Just got this docker installed and working, but I'm having issue adding torrents. When adding via File, the upload fails. When attempting to add via URL, it also fails to download the .torrent content and add to the system. The only way I've found so far is to stop the docker, add the .torrent file to a folder which auto-imports into Deluge, then start the docker again and manage the newly added torrents.

 

Any help with this is greatly appreciated.

Share this post


Link to post
31 minutes ago, seventhaxis said:

Just got this docker installed and working, but I'm having issue adding torrents. When adding via File, the upload fails. When attempting to add via URL, it also fails to download the .torrent content and add to the system. The only way I've found so far is to stop the docker, add the .torrent file to a folder which auto-imports into Deluge, then start the docker again and manage the newly added torrents.

 

Any help with this is greatly appreciated.

I'd never used the delugesiphon Chrome plugin prior to watching SIO's Youtube install tutorial for this docker, but it was a breeze to install and makes adding torrents painless. Highly recommend it as an addition to this docker.

Edited by BBLV

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.