Ranzingabon Hagglesmith

Hi Folks --- new error today after restarted Deluge. All of my torrents to every tracker are now saying "Error: outgoing socket was closed" -- is that a firewall issue, a VPN issue, or what? Really weird, hoping someone could point me at where to focus. In settings I have outgoing port set to "use random ports" like always. No changes anywhere else AFAIK

Hi folks, any thoughts? Now I'm getting errors "Error: unexpected end of file in bencoded string" and "Error: No route to host"

I've noticed some strange problems over the past few weeks-- mostly torrent time-out errors, and now I'm getting the "Error: end of file" on random files from one particular tracker. I thought it might be a problem with the particular AirVPN server I was using, so I restarted the container a few days ago, but the errors just creeped back. Any idea what might be going wrong? My fear is that might be because of the number of torrents I have (~2500 unpaused). I have the ltConfig plugin set up and adjusted, and that fixed errors that arose when I hit around 2,000 torrents, so I'm hoping it's something that can be fixed by playing around with those settings. Strange that rebooting the Deluge docker fixes the timeout errors for a few days. Actually, it seems the "Error: end of file" error I'm receiving from torrents for one particular tracker is not fixed by rebooting the container, so I have no clue what's going on there. I'm running the latest version of the Binhex DockerDelugeVPN via AirVPN. e: rechecking the torrents does not seem to fix the "Error: end of file" problem

Hey, in the off chance you're reading this: which json file are you referring to? I'm going to update to 2.x soon.

Okay, update: I figured out on my own how to switch back to an earlier version of DelugeVPN. I was able to get 2.0.3-1-04 running -- but not 1-05 or 1-06, so some change that occurred after 1-04 creates this problem on Synology docker, if that helps anyone. Then I found out that Deluge 2+ hasn't been whitelisted yet in a lot of places so I reverted to 1.3.15_18_ge050905b2-1-04 which is relatively sluggish but functional.

Thanks for the reply. I'm not using any Ouroboros, so that's not causing the problem on my end. The only active containers I typically have are Sonarr, Jackett, and my beloved DelugeVPN. Hmmm, is there I way I can manually fix this problem I'm experiencing manually? Or just use the correct start command manually? Or maybe revert to an earlier version...

Hiya Lipora - have you been able to solve the init.sh problem? That's the exact problem I'm having since I tried to update my Deluge by using the "clear" function in the Synology DSM Docker. My setup is entirely crippled without Deluge!

Hi. So my DelugeVPN in Docker was working pretty slowly. Then I stupidly decided to play around with it and using the "clear" function in the Synology DSM docker app. I read online that this was one way to update the container. I figured it was worth a shot and that it probably wouldn't completely break it, which is exactly what has happened. So, now when I try to turn the container on, it refuses to run, and I get this message in the log: "/bin/bash: /root/init.sh: No such file or directory" over and over. All my settings still seem to be the same, and all my data is still there in the established /config folder. Any ideas what I did wrong and how I can I get Deluge running again?

Thanks. Hmm, I don't know what happened, but I updated my NAS operating system, rebooted it, and somehow that fixed my problem with Deluge, at least for now. I have no idea what was wrong and what fixed it.

Okay, I have now tried with both the router and the DSM firewalls disabled and experience the same problem.

Okay, here are my port and then firewall settings. Does this look right? DockerVPN port settings: Firewall settings in Synology DSM: edit: Okay, I tried just disabling my Synology DSM firewall totally and that made no difference -- same problem. I tried replacing the AirVPN config before I posted here. I don't see how my router settings could changed, but I can't check that just this minute. Is there anything else I can check for in the mean time?

Hmm, crap. I tried putting in a new openvpn config file before I posted here. I can't think of anything else that I would have changed, unless they changed on their own somehow.

Hello folks. my Binex Docker DelugeVPN suddenly stopped working about two days ago and I can't figure out what's up. I noticed first of all that it my torrents were no longer connecting to the internet last night, so I restarted the docker container before I went to bed. Then today, I found out that DelugeVPN isn't starting up at all, or is getting blocked somehow. I haven't made any changes to any settings and it had been running perfectly (or as perfectly as Deluge runs) for months. Any ideas? I posted the log below. I'm using AirVPN. The only thought I had was to create a new AirVPN config, which I did earlier today, but it still doesn't work and now I'm out of ideas. I set up my docker container using the instructions here: http://tomthegreat.com/2018/03/11/setting-up-deluge-with-vpn-on-synology-using-docker/ and I don't think I've changed anything, at least in a very long time. Here's what's going down when I boot up: The only thing that stands out to me is the "WARNING: file 'credentials.conf' is group or others accessible." An help would be really appreciated! This container is the heart of my entire setup and I'm SOL with it broken.