Common ruTorrent Errors and How to Fix Them

Troubleshooting Flowchart #

Use this flowchart to quickly diagnose your issue:

  ruTorrent DIAGNOSTIC FLOWCHART
  ═══════════════════════════════════════════════════════

  What's the problem?
       │
       ├── Can't log in?
       │   ├── Wrong password → Check client area for credentials
       │   ├── 502/503 error → rTorrent may be down, restart from dashboard
       │   └── "Unauthorized" → Clear browser cache, try incognito
       │
       ├── Torrent has red ✕?
       │   ├── "Disk full" → Free space (see disk quotas guide)
       │   ├── "Hash check" → Re-check torrent (right-click → Hash Check)
       │   └── "Tracker error" → Tracker may be down, wait & retry
       │
       ├── Download speed is 0?
       │   ├── Seeds = 0 → No seeders available, try another torrent
       │   ├── "Queued" → Increase queue limit (see queue guide)
       │   └── Disk full → Free space first
       │
       ├── Torrent stopped automatically?
       │   ├── Public torrent → Normal! See seeding rules guide
       │   └── Private torrent → Check disk space & upload limits
       │
       └── ruTorrent loads but blank/broken?
           ├── Clear browser cache (Ctrl+Shift+Del)
           ├── Try different browser
           └── Disable browser extensions

ruTorrent is known for the vast functionalities it provides. With many features, there is a higher probability that you will run into some errors. These errors are small and their fixes are even smaller.In this article, we will address all the common ruTorrent errors and how you can fix them.

Error: Bad data from the tracker or Bad Tracker Data #

Solution: #

It occurs when the tracker is overloaded. The ideal solution is to be patient and wait for the torrent to stabilize. If it error remains after some time too, then you might want to consider changing the torrent file.

Error: #

Problem connecting to tracker – timeout exceeded #

Problem connecting to tracker – HTTP Error 503: Connect failed #

Problem connecting to tracker – [Errno socket error] (10061, “Connection refused” #

Problem connecting to tracker – (111, ‘Connection refused’ #

Solution:  #

This again needs patients from your end. When trackers are facing heavy traffic, some connection issues may take place. In such cases, just keep your ruTorrent running, the error will be resolved once the connection is back.

Error: Problem connecting to tracker – HTTP Error 404: Not Found #

Solution:  #

The torrent file is no longer available.

Error: Problem connecting to tracker – HTTP Error 400: Not Authorized #

Solution:  #

The torrent file is very old and has been removed.

Error: Problem connecting to tracker – HTTP Error 407: Proxy Authentication Required #

Solution:  #

Check and very your login credentials of the server to re-establish connection with the tracker.

Error: *(IOError – [Errno13] Permission denied) #

Solution:  #

ruTorrent is running and another ruTorrent instance is opened. This is not allowed by the trackers. Therefore restart your ruTorrent.

Error: Connecting to peers #

Solution:  #

There might not be any peers available at the moment. Leave the ruTorrent on and the error will be gone when peers are found.

Error: Problem connecting with tracker – (10054,’Connection reset by peer’) #

Solution:  #

The connection has been shut down by the remote computer. It cannot be resolved.

Error: PHP module PCRE is not installed. ruTorrent will not work. #

Solution:  #

A PHP module is missing, Please raise a ticket and mention the error.

Error: Rejected by tracker – Port XXXX is blacklisted #

Solution:  #

One of the default ports is being used to establish the connection. The tracker won’t allow such a connection with a client as these are the common ports that are throttled by the ISP. You should contact the tracker and request the ports that are ideal.

Error: Web server can’t access rTorrent’s session directory for reading. ruTorrent will not work. #

Solution:  #

This is usually caused by settings of permissions. Contact support in case of such an issue.

Error: #

rTorrent’s user can’t access settings directory for read/write/execute. ruTorrent will not work. #

rTorrent’s user can’t access file ./test.sh for read/execute. ruTorrent will not work. #

rTorrent’s user can’t access torrents directory for read/execute. You can’t add torrents through ruTorrent. #

Web server can’t access settings directory for read/write/execute. ruTorrent can’t save own settings. #

Web server can’t access torrents directory for read/write/execute. You can’t add torrents through ruTorrent. #

Solution:  #

These errors point out that the installation of ruTorrent is not done correctly. Please contact support in case of such issues.

Error: Bad link to rTorrent. Check if it is really running. Check $scgi_port and $scgi_host settings in config.php and scgi_port in rTorrent configuration file. #

Solution:  #

This means that the ruTorrent instance is terminated or did not start. If you are able to see the list of torrents with this error then there is an issue with the ruTorrent configuration file. 

Error: *rTorrent is compiled with incorrect version of xmlrpc-c library, without i8 support. Version must be >= 1.11. Some functionality will be unavailable. #

Solution:  #

Old forms of xmlrpc-c don’t uphold long integers. So numbers more noteworthy than 2G will be appeared as negative. Furthermore, the exchange window @Settings@ won’t work as expected. Note – it isn’t sufficient to have quite recently the library xmlrpc-c variant >=1.11 in the framework. It is important to have rTorrent assembled with it.

Error: plugin: rTorrent’s user can’t access PHP interpreter. Plug-in will not work. #

Solution:  #

This error is identified with PHP running on the framework. Note – if PHP is working in the framework, it doesn’t generally imply that the interpreter exists in the framework as well. The bundle php-cli is important. Web-worker may utilize e. g. php-fcgi which doesn’t contain an interpreter. Again in the event that you are inexperienced with this, if it’s not too much trouble, contact us by opening a help ticket so we settle this for you.

Error: xxx plugin: Plugin will not work. Web-server can’t access to external program (program name) #

Solution:  #

Some plugins are missing to work properly. Contact support and we will resolve the issue for you.These are the top and most common errors, if you have found anything apart from this, please contact support team for assistance.