I get “problem connecting to tracker – HTTP Error 400: Not Authorized” message. What happened?
Trackers often become overloaded, and connections fail often as well. Below we offer a list of errors for which the best solution would be to just leave the client running because most of the time such a problem will disappear by itself. 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’) Other error messages:a) Problem connecting to tracker – HTTP Error 400: Not Authorized: the operators of this tracker do not allow it to be used for this torrent. Generally, this points to an old torrent. You can go to the web site associated with the tracker, as you could find there torrent reseeded or updated for the files you want. If that fails too, try searching for another torrent altogether. b) Problem connecting to tracker – HTTP Error 404: Not Found: likely to be met in case of a dead torrent.
Related Questions
- While registering I keep getting the error message "Sorry, SMSPup http://smspup.com.au is strictly for Australian residents." Why?
- How do I troubleshoot the HTTP status 500 - Internal Server Error error message while I access the CAR report?
- I tried to send a message, but got an error about Social Security Numbers being restricted. What happened?
