ruTorrent is known for the vast functionalities it provides. With many features, there is a higher probability that you will run into some Fehlers. These Fehlers are small and their Lösunges are even smaller.In diesem Artikel, we will address all the common ruTorrent Fehlers and how können Sie Lösung them.

Fehler: Bad data from the tracker or Bad Tracker Data

Lösung:

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

Fehler:

Problem connecting to tracker – timeout exceeded

Problem connecting to tracker – HTTP Fehler 503: Connect fehlgeschlagen

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

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

Lösung: 

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

Fehler: Problem connecting to tracker – HTTP Fehler 404: Not Found

Lösung: 

The torrent file is no longer verfügbar.

Fehler: Problem connecting to tracker – HTTP Fehler 400: Not Authorized

Lösung: 

The torrent file is very old and has been removed.

Fehler: Problem connecting to tracker – HTTP Fehler 407: Proxy Authentication Required

Lösung: 

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

Fehler: *(IOFehler – [Errno13] Permission denied)

Lösung: 

ruTorrent is running and another ruTorrent instance is öffnened. This is not allowed by the trackers. Therefore neu starten your ruTorrent.

Fehler: Connecting to peers

Lösung: 

There might not be any peers verfügbar at the moment. Leave the ruTorrent on and the Fehler will be gone when peers are found.

Fehler: Problem connecting with tracker – (10054,’Connection zurücksetzen by peer’)

Lösung: 

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

Fehler: PHP module PCRE is not installierened. ruTorrent will not work.

Lösung: 

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

Fehler: Rejected by tracker – Port XXXX is blacklisted

Lösung: 

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.

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

Lösung: 

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

Fehler:

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. Sie können’t add torrents through ruTorrent.

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

Web server can’t access torrents directory for read/write/execute. Sie können’t add torrents through ruTorrent.

Lösung: 

These Fehlers point out that the installierenation of ruTorrent is not done correctly. Please contact supPort in case of such issues.

Fehler: 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.

Lösung: 

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

Fehler: *rTorrent is compiled with incorrect version of xmlrpc-c library, without i8 supPort. Version must be >= 1.11. Some functionality will be unverfügbar.

Lösung: 

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.

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

Lösung: 

This Fehler 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 öffnening a help ticket so we settle this for you.

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

Lösung: 

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