My new log with VPN enabled. No error but stuck on queued when testing with official Ubuntu ISO. https://pastebin.com/5JcmCTTk

Edited March 10, 20206 yr by brikn
Adding picture

2 hours ago, brikn said:

My new log with VPN enabled. No error but stuck on queued

what is /data mapped to on the host?.

6 hours ago, binhex said:

yep i do, but im not sure what use it will be to you as its very specific to my setup (nginx reverse proxy and custom ports), not to mention i would have to scrub out a lot of the info due to security concerns, all i can say, is keep at it, its definitely achievable.

Could we sort this out in PM, I'm also using a reverse proxy? I just need to see how you formatted your credentials etc so I can match my input to the app and the way I run rTorrent?

Quote

what is /data mapped to on the host?.

/mnt/data

 

 

what is /data mapped to on the host?.

/mnt/data
 
 
And does that path exist on the host? That's not a normal path for unraid.

Sent from my CLT-L09 using Tapatalk

yeah it exists. It's the same one I use for delugevpn. Oh this isn't on Unraid, is that why it's not working?

Edited March 10, 20206 yr by brikn

15 hours ago, brikn said:

Oh this isn't on Unraid, is that why it's not working?

nope, this container can run on any distro that is capable of running docker. ok check permissons here, does the user with uid 1000 and gid 1000 have read and write access to /mnt/data ?

What is to proper way to update the timezone varible if I am trying to make is US Pacific Time? 

yeah, i did "chown -R brian:brian /mnt/data" before and that user is what also is assigned 1000 UID and GID.

Hi just wondering if anyone had a solution to this.

 

I keep seeing the below to the autodl. Never had this before. Thanks in advance :)

 

3 hours ago, Gursh said:

Hi just wondering if anyone had a solution to this.

 

I keep seeing the below to the autodl. Never had this before. Thanks in advance

 

I am also getting this error. I have disabled my autodl for now. I think the git repo might have changed their URL?, not too sure but I think this is an issue with autodl in general not just you or your setup but I am talking out of pure speculation.

10 hours ago, noraa said:

I am also getting this error. I have disabled my autodl for now. I think the git repo might have changed their URL?, not too sure but I think this is an issue with autodl in general not just you or your setup but I am talking out of pure speculation.

I'm getting this error and actually getting similar errors when autodl tries to snatch torrents as well.  Anyone else having that issue? 

 

I don't think the problem lies with autodl itself, because if I run autodl directly on the host machine I don't see any of the above errors.

Edited March 15, 20206 yr by Tasteless

I just updated my client, and now the default username and password that I've typed every day don't work. Am I being dumb, or did something change?

I just updated my client, and now the default username and password that I've typed every day don't work. Am I being dumb, or did something change?

See post #2 of this thread

Sent from my CLT-L09 using Tapatalk

On 3/14/2020 at 9:54 AM, Gursh said:

Hi just wondering if anyone had a solution to this.

 

I keep seeing the below to the autodl. Never had this before. Thanks in advance

 

Both my friend and I are getting this same error as well. I understand the issue is with autodl itself but is there any eta on when a fix is coming, whether a downgrade of the autodl version within the docker or some fix? It looks like that has been happening since March 11th cause both my friend and I haven't had any autoadded since then.

Edited March 16, 20206 yr by Bensawsome

On 3/11/2020 at 7:46 PM, brikn said:

yeah, i did "chown -R brian:brian /mnt/data" before and that user is what also is assigned 1000 UID and GID.

I've tried recreating, changing permissions to root for the container and data directory but still nothing. I always get some form of error, whether it is tracker timeout or invalid IP, or just not connecting to any peers. I've read every source I could find about this issue but the only thing I can find is permissions error but nothing I do seems to fix the problem. I can get delugevpn and qbittorrentvpn working with ease but rutorrentvpn is still not working.

10 hours ago, Bensawsome said:

Both my friend and I are getting this same error as well. I understand the issue is with autodl itself but is there any eta on when a fix is coming, whether a downgrade of the autodl version within the docker or some fix? It looks like that has been happening since March 11th cause both my friend and I haven't had any autoadded since then.

For the record, I don't think the issue lies with autodl-irssi or binhex's code.  I think it is a messed up release on docker hub.  If I build the image myself from source via binhex's git everything works great.

6 hours ago, Tasteless said:

For the record, I don't think the issue lies with autodl-irssi or binhex's code.  I think it is a messed up release on docker hub.  If I build the image myself from source via binhex's git everything works great.

Looks like it. I'm building a custom image from source and can't reproduce the issue either.

8 hours ago, Tasteless said:

For the record, I don't think the issue lies with autodl-irssi or binhex's code.  I think it is a messed up release on docker hub.  If I build the image myself from source via binhex's git everything works great.

its very possible that there was an issue with autodl-irssi at the time of the build (pulls from master branch), and this issue has now been resolved, so subsequent builds are ok, i will create a new image shortly and see if this fixes the issue.

6 hours ago, binhex said:

its very possible that there was an issue with autodl-irssi at the time of the build (pulls from master branch), and this issue has now been resolved, so subsequent builds are ok, i will create a new image shortly and see if this fixes the issue.

Just updated it. That fixed it. Thank you very much

Edited March 17, 20206 yr by Bensawsome

I'm having some trouble with Auto Dl, is there a way to screen or tmux attach to the running instance of irssi on the container? 

I'm getting an error that basically says that could not save state for AutodlState.xml, cannot write to /home/nobody/.autodl/AutodlState.xml

Thanks for the fix. @bumperjeep I think it may permissions. Im not that great at linux, but I had a similar issue with writing being an issue. Goodluck!

the container name on the dashboard is blue indicating there is an update, but update option is not in drop down menu. Go to docker tab and sure enough update ready and apply update are there. run update and it completes. but still shows update ready. tried twice now same result. any idea??

Hey! Having problems with setting up torrents being moved to a diff directory when completed.

Tried to change it in the GUI, "Autotools" section - didn't work, but the setting seems to be saved.

 

Then the FAQ says "So rutorrent is purely a web frontend to rtorrent, and as such does NOT modify any settings for rtorrent...", and I still don't get the logic of it. Why the hell would you even have settings in GUI that just don't work? Why to add them to GUI at all? Seems like nonsense to me.

 

Then there is rtorrent.rc file, it has a setting with my folder for torrents being downloaded (incomplete), but I don't see any settings for moving torrents to another directory after completion.

 

BTW, I changed the default directory for downloads in the GUI, and it works the way it should - torrents are being downloaded to the new dir. And the FAQ says it shouldn't have worked.