New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When adding torrents, directory listing is blank/empty #1647
Comments
Seems like it was indeed a permissions issue on the directory. |
I get this too. If I type in the path manually I can access it just not see. I can even access the files with the path typed in manually (i.e. create a torrent from a directory that I typed in manually), I just can't see the directory. I have execute permissions in the directory for everyone. What did you do to fix this? My permissions are identical to another server I have rtorrent on. Empty upon first pressing ... in rutorrent uid=33(www-data) gid=33(www-data) groups=33(www-data),1000(bmbm) To me it looks like it can't see anything in /home/bmbm/rtorrent/downloads because it doesn't have read, but it should be running as www-data which is in the bmbm group and has read. nginx is using the www-data user according to ps aux I have even restarted (didn't fix) and gave downloads 777 then restarted nginx/apache2 - which unbelievably still did not let me see the directory. |
Upon a git pull update of rutorrent, I immediately was able to see all directories. I guess it was likely not a permission issue but an issue with my rutorrent config itself. That was my original guess but delize's success with the permissions got me sidetracked. |
I've been struggling with same issue for a while and decided to drop a hint here, since this page is the first rutorrent github result you came upon googling for "rutorrent can't select directory". If you're 100% sure you entered right path in the So you should have this line in your server config: rutorrent strongly depends on iframe usage. So strong you wouldn't even see the starting path indicated by |
without php-mbstring may cause this problem |
For Apache2 the line would be:
in the rutorrent virtual host configuration. To get things working check all of the following (example) apache2 runs as www-data and so the /4TBHDD/download directory is: All good now. HTH !!! |
rtorrent version: 0.9.6
libtorrent version: 0.13.6
My download location is CIFS (soon to be NFS) and while the local system has no issues seeing the directories that appear within the root torrent directory (and neither does rtorrent), rutorrent does (even though www-data belongs to the media goup):
For the sake of troubleshooting, I set this to 777, but 775 should suffice under normal circumstances (remember CIFS mount):
apache2 access.log file:
error.log:
This started happening, but didn't happen prior to today when I filled out this issue (I think this was because of an expired cookie though):
If I type the path in manually, it will accept the location.
What is going on with this, and what can be done to correct the either timing out issue or the fact that PHP/rutorrent can't see the directory folders?
Other web based services (like sonarr) can browse the location and see the contents.
The text was updated successfully, but these errors were encountered: