-
-
Notifications
You must be signed in to change notification settings - Fork 114
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
500 error when upload file greater than 1M via rpc.php #245
Comments
Seeing the same behavior with the latest image. Attempting a 1,715KB .torrent file upload via RPC.php triggers HTTP 500 response. Also manually uploading .torrent via rutorrent interface fails with response HTTP 413 Entity Too Large, which appears to be due to nginx configuration. Possibly a hint as to what's happening?
Even with XMLRPC logging enabled, seemingly nothing insightful is logged. |
Could you try setting |
@stickz it's not working |
@f0oster for me it's working from the rutorrent interface. Do you have an nginx ingress in front? |
Good point... I do have an nginx reverse proxy configured which I was likely using during testing, whoops. I'll test and confirm shortly. Edit: Yep, confirming that it does work through the rutorrent interface when I bypass my reverse proxy. Sorry for the false alarm. |
You may need to update your configuration to try
It's actually faster to do this, if you have the CPU processing resources. There is limited situations (not yours) where it creates too much overhead. Sonarr has much more overhead than this task. If you can run sonarr, this will work great. |
@stickz I don't think Sonarr works with |
It does. You just need to change the url base path. ruTorrent will accept the |
rutorrent returns a 200 HTTP code, but Sonarr fails
|
You can try to talk directly to rTorrent on Sonarr through the URL path |
(port 31299 is forwarded to 8000) Sonarr test works (as before with httprcp)
but not uploading a torrent
8000 port seems to be the XMLRPC_PORT |
When switching Sonarr to |
I have a similar problem in Radarr. When trying to download a torrent file by Radarr, I receive the following message: |
Support guidelines
I've found a bug and checked that ...
Description
When uploading a torrent greater than 1M on
/plugins/rpc/rpc.php
a 500 HTTP header occurs. I found no interesting error log to investigate. I already increasedXMLRPC_SIZE_LIMIT
to16M
andMEMORY_LIMIT
to2048M
without success.Expected behaviour
Should return an 200 http
Actual behaviour
500 error code
Steps to reproduce
/plugins/rpc/rpc.php
Docker info
Kubernetes
Version
docker-compose --version
):uname -a
):Docker compose
Kubernetes
Container logs
Additional info
Using 4.1.5-0.9.8-0.13.8 docker image
The text was updated successfully, but these errors were encountered: