-
Notifications
You must be signed in to change notification settings - Fork 72
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
Bad response from server: (504 [error,getplugins]) Gateway Time-out on NFS share #61
Comments
Hello Fabio72, This problem usually occurs when the source (the downloads directory in this case) is too slow. Maybe trying to add a cache to the NFS mount could fix this problem? |
This keeps happening to me too, I'm using a server with 64GB ram, nvme disks and i9-9900k.... |
still an issue for me |
same for me |
Yes it Occurred to me as well |
I have 10000+ torrents, so this erro makes my rutorrent webUI unaccessible... |
Still an issue |
Yes, when there are more than 12000 torrents, even if I rolled back the
ruTorrent version to stable, it doesn't solve this issue.
…On Thu, May 12, 2022 at 16:06 Danny Michel ***@***.***> wrote:
Still an issue
—
Reply to this email directly, view it on GitHub
<#61 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACL7ZKVQYTNWPSXCQFBWQW3VJS3YRANCNFSM4GKYVQ5Q>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
i only have like 30 torrents |
I've been using it for a while and it used to be great.
Now I dunno what's appening but i'm unable to start it with the downlod folder on an nfs mount.
If I start the container without the disk remapping everything is fine.
I restored an older backup of the VM running docker, but nothing changes.
The download NFS folder is accessible and the permissions seem fine too.
The text was updated successfully, but these errors were encountered: