Sickchill: Unable to connect to provider T411

Created on 6 Apr 2017  路  19Comments  路  Source: SickChill/SickChill

Before submitting your issue:

Enable debug logging in SickRage settings, reproduce the error (be sure to disable after the bug is fixed)

Branch/Commit: master / 4b3dad8eec3e238b1cadc809acf8e0e26deb9eb3
OS: Debian jessie
What you did: search for needed episodes
What happened: "Unable to connect to provider T411"
What you expected:
Logs:

PASTE LOGS HERE

Journal des 茅v茅nements

2017-04-06 10:18:04 INFO SEARCHQUEUE-BACKLOG-153021 :: No needed episodes found during backlog search for: [The Walking Dead]
2017-04-06 10:18:04 WARNING SEARCHQUEUE-BACKLOG-153021 :: [T411] :: Unable to connect to provider
2017-04-06 10:18:04 WARNING SEARCHQUEUE-BACKLOG-153021 :: [T411] :: Unable to connect to provider
2017-04-06 10:18:04 WARNING SEARCHQUEUE-BACKLOG-153021 :: [T411] :: Unable to connect to provider
2017-04-06 10:18:04 WARNING SEARCHQUEUE-BACKLOG-153021 :: [T411] :: Unable to connect to provider
2017-04-06 10:18:04 WARNING SEARCHQUEUE-BACKLOG-153021 :: [T411] :: Unable to connect to provider
2017-04-06 10:18:04 WARNING SEARCHQUEUE-BACKLOG-153021 :: [T411] :: Unable to connect to provider
2017-04-06 10:18:04 WARNING SEARCHQUEUE-BACKLOG-153021 :: [T411] :: Unable to connect to provider
2017-04-06 10:18:03 INFO SEARCHQUEUE-BACKLOG-153021 :: [T411] :: Performing episode search for The Walking Dead

Bug / Issue Upstream

Most helpful comment

All 19 comments

Same problem here.

Same behaviour observed.
OS : Raspbian
Tried to ping the site from the same machine with success, but still gets the "unable to connect" in Sickrage.

2017-04-06 07:25:27 INFO SEARCHQUEUE-BACKLOG-324227 :: No needed episodes found during backlog search for: [Trop]
2017-04-06 07:25:27 WARNING SEARCHQUEUE-BACKLOG-324227 :: [T411] :: Unable to connect to provider
2017-04-06 07:25:27 DEBUG SEARCHQUEUE-BACKLOG-324227 :: [T411] :: Requested a json response but response was not json, check the url: https://api.t411.ai/auth
2017-04-06 07:25:27 DEBUG SEARCHQUEUE-BACKLOG-324227 :: [T411] :: With post data: username=*&password=*
2017-04-06 07:25:27 DEBUG SEARCHQUEUE-BACKLOG-324227 :: [T411] :: POST URL: https://api.t411.ai/auth [Status: 200]
2017-04-06 07:25:26 WARNING SEARCHQUEUE-BACKLOG-324227 :: [T411] :: Unable to connect to provider
2017-04-06 07:25:26 DEBUG SEARCHQUEUE-BACKLOG-324227 :: [T411] :: Requested a json response but response was not json, check the url: https://api.t411.ai/auth
2017-04-06 07:25:26 DEBUG SEARCHQUEUE-BACKLOG-324227 :: [T411] :: With post data: username=
*&password=**
2017-04-06 07:25:26 DEBUG SEARCHQUEUE-BACKLOG-324227 :: [T411] :: POST URL: https://api.t411.ai/auth [Status: 200]
2017-04-06 07:25:25 WARNING SEARCHQUEUE-BACKLOG-324227 :: [T411] :: Unable to connect to provider
2017-04-06 07:25:25 DEBUG SEARCHQUEUE-BACKLOG-324227 :: [T411] :: Requested a json response but response was not json, check the url: https://api.t411.ai/auth
2017-04-06 07:25:25 DEBUG SEARCHQUEUE-BACKLOG-324227 :: [T411] :: With post data: username=
*&password=**
2017-04-06 07:25:25 DEBUG SEARCHQUEUE-BACKLOG-324227 :: [T411] :: POST URL: https://api.t411.ai/auth [Status: 200]
2017-04-06 07:25:24 WARNING SEARCHQUEUE-BACKLOG-324227 :: [T411] :: Unable to connect to provider
2017-04-06 07:25:24 DEBUG SEARCHQUEUE-BACKLOG-324227 :: [T411] :: Requested a json response but response was not json, check the url: https://api.t411.ai/auth
2017-04-06 07:25:24 DEBUG SEARCHQUEUE-BACKLOG-324227 :: [T411] :: With post data: username=
*&password=**
2017-04-06 07:25:24 DEBUG SEARCHQUEUE-BACKLOG-324227 :: [T411] :: POST URL: https://api.t411.ai/auth [Status: 200]
2017-04-06 07:25:23 WARNING SEARCHQUEUE-BACKLOG-324227 :: [T411] :: Unable to connect to provider
2017-04-06 07:25:23 DEBUG SEARCHQUEUE-BACKLOG-324227 :: [T411] :: Requested a json response but response was not json, check the url: https://api.t411.ai/auth
2017-04-06 07:25:23 DEBUG SEARCHQUEUE-BACKLOG-324227 :: [T411] :: With post data: username=
*&password=**
2017-04-06 07:25:23 DEBUG SEARCHQUEUE-BACKLOG-324227 :: [T411] :: POST URL: https://api.t411.ai/auth [Status: 200]
2017-04-06 07:25:23 WARNING SEARCHQUEUE-BACKLOG-324227 :: [T411] :: Unable to connect to provider
2017-04-06 07:25:23 DEBUG SEARCHQUEUE-BACKLOG-324227 :: [T411] :: Requested a json response but response was not json, check the url: https://api.t411.ai/auth
2017-04-06 07:25:23 DEBUG SEARCHQUEUE-BACKLOG-324227 :: [T411] :: With post data: username=
*&password=**
2017-04-06 07:25:23 DEBUG SEARCHQUEUE-BACKLOG-324227 :: [T411] :: POST URL: https://api.t411.ai/auth [Status: 200]
2017-04-06 07:25:22 WARNING SEARCHQUEUE-BACKLOG-324227 :: [T411] :: Unable to connect to provider
2017-04-06 07:25:22 DEBUG SEARCHQUEUE-BACKLOG-324227 :: [T411] :: Requested a json response but response was not json, check the url: https://api.t411.ai/auth
2017-04-06 07:25:22 DEBUG SEARCHQUEUE-BACKLOG-324227 :: [T411] :: With post data: username=
*&password=**
2017-04-06 07:25:22 DEBUG SEARCHQUEUE-BACKLOG-324227 :: [T411] :: POST URL: https://api.t411.ai/auth [Status: 200]
2017-04-06 07:25:22 WARNING SEARCHQUEUE-BACKLOG-324227 :: [T411] :: Unable to connect to provider
2017-04-06 07:25:22 DEBUG SEARCHQUEUE-BACKLOG-324227 :: [T411] :: Requested a json response but response was not json, check the url: https://api.t411.ai/auth
2017-04-06 07:25:22 DEBUG SEARCHQUEUE-BACKLOG-324227 :: [T411] :: With post data: username=
*&password=**
2017-04-06 07:25:22 DEBUG SEARCHQUEUE-BACKLOG-324227 :: [T411] :: POST URL: https://api.t411.ai/auth [Status: 200]
2017-04-06 07:25:21 WARNING SEARCHQUEUE-BACKLOG-324227 :: [T411] :: Unable to connect to provider
2017-04-06 07:25:21 DEBUG SEARCHQUEUE-BACKLOG-324227 :: [T411] :: Requested a json response but response was not json, check the url: https://api.t411.ai/auth
2017-04-06 07:25:21 DEBUG SEARCHQUEUE-BACKLOG-324227 :: [T411] :: With post data: username=
*&password=**
2017-04-06 07:25:21 DEBUG SEARCHQUEUE-BACKLOG-324227 :: [T411] :: POST URL: https://api.t411.ai/auth [Status: 200]
2017-04-06 07:25:20 WARNING SEARCHQUEUE-BACKLOG-324227 :: [T411] :: Unable to connect to provider
2017-04-06 07:25:20 DEBUG SEARCHQUEUE-BACKLOG-324227 :: [T411] :: Requested a json response but response was not json, check the url: https://api.t411.ai/auth
2017-04-06 07:25:20 DEBUG SEARCHQUEUE-BACKLOG-324227 :: [T411] :: With post data: username=
*&password=**
2017-04-06 07:25:20 DEBUG SEARCHQUEUE-BACKLOG-324227 :: [T411] :: POST URL: https://api.t411.ai/auth [Status: 200]
2017-04-06 07:25:20 WARNING SEARCHQUEUE-BACKLOG-324227 :: [T411] :: Unable to connect to provider
2017-04-06 07:25:20 DEBUG SEARCHQUEUE-BACKLOG-324227 :: [T411] :: Requested a json response but response was not json, check the url: https://api.t411.ai/auth
2017-04-06 07:25:20 DEBUG SEARCHQUEUE-BACKLOG-324227 :: [T411] :: With post data: username=
*&password=**
2017-04-06 07:25:20 DEBUG SEARCHQUEUE-BACKLOG-324227 :: [T411] :: POST URL: https://api.t411.ai/auth [Status: 200]
2017-04-06 07:25:19 WARNING SEARCHQUEUE-BACKLOG-324227 :: [T411] :: Unable to connect to provider
2017-04-06 07:25:19 DEBUG SEARCHQUEUE-BACKLOG-324227 :: [T411] :: Requested a json response but response was not json, check the url: https://api.t411.ai/auth
2017-04-06 07:25:19 DEBUG SEARCHQUEUE-BACKLOG-324227 :: [T411] :: With post data: username=
*&password=**
2017-04-06 07:25:19 DEBUG SEARCHQUEUE-BACKLOG-324227 :: [T411] :: POST URL: https://api.t411.ai/auth [Status: 200]
2017-04-06 07:25:19 WARNING SEARCHQUEUE-BACKLOG-324227 :: [T411] :: Unable to connect to provider
2017-04-06 07:25:19 DEBUG SEARCHQUEUE-BACKLOG-324227 :: [T411] :: Requested a json response but response was not json, check the url: https://api.t411.ai/auth
2017-04-06 07:25:19 DEBUG SEARCHQUEUE-BACKLOG-324227 :: [T411] :: With post data: username=
*&password=**
2017-04-06 07:25:19 DEBUG SEARCHQUEUE-BACKLOG-324227 :: [T411] :: POST URL: https://api.t411.ai/auth [Status: 200]
2017-04-06 07:25:18 INFO SEARCHQUEUE-BACKLOG-324227 :: [T411] :: Performing episode search for Trop
2017-04-06 07:25:18 DEBUG SEARCHQUEUE-BACKLOG-324227 :: [T411] :: Fallback episode search initiated
2017-04-06 07:25:16 WARNING SEARCHQUEUE-BACKLOG-324227 :: [T411] :: Unable to connect to provider
2017-04-06 07:25:16 DEBUG SEARCHQUEUE-BACKLOG-324227 :: [T411] :: Requested a json response but response was not json, check the url: https://api.t411.ai/auth
2017-04-06 07:25:15 DEBUG SEARCHQUEUE-BACKLOG-324227 :: [T411] :: With post data: username=
*&password=***
2017-04-06 07:25:15 DEBUG SEARCHQUEUE-BACKLOG-324227 :: [T411] :: POST URL: https://api.t411.ai/auth [Status: 200]
2017-04-06 07:25:15 INFO SEARCHQUEUE-BACKLOG-324227 :: [T411] :: Performing season pack search for Trop

I've tested on couchpotato and he found what I want, so I think the problem is on sickrage, not in t411

I confirm, couchpotato works here also, but not SickRage.

How did you set it up in CouchPotato?
Because it doesn't look like T411 is a provider that is built into CouchPotato by default.

BTW the site is reachable, yes, but the API responds to all requests with "ok" instead of an actual response.

Hi !

I have exactly the same problem since few days.
CouchPotato is ok with same settings !

@sharkykh , it's a plugin to use t411 in Couchpotato.

Same issue here, works fine with Couchpotato but unable to connect from Sickrage!

The CouchPotato plugin is not using the API like SickRage does.

T411 need to fix their API.

Go and check the site's forums for announcements about their API service.

Same issue on sickrage :(

[T411] :: Unable to connect to provider

No info on T411.ai ...

Someone commented on the help channel the API is on maintenance and they are working on it. No ETA was given. Information is second hand and cannot be verified.

t411 provider on Couchpotato from djoole : https://github.com/djoole/couchpotato.provider.t411 works with BeautifulSoup : html parser whereas t411 provider on Sickrage works with Rest t411 API.
That's why t411 works fine on Couchpotato and not on Sickrage

Same issue here since a week now :s Anyone has news about that API ?

You should ask the site developers through the proper channels like posting on the forums or via IRC...

Same problem here..

API seems to be working fine today. Let's hope it stays that way for a while...

Was this page helpful?
0 / 5 - 0 ratings

Related issues

Smokey23 picture Smokey23  路  4Comments

oodonnell picture oodonnell  路  4Comments

knyllers picture knyllers  路  4Comments

dilruwan7 picture dilruwan7  路  3Comments

CaptainConsternant picture CaptainConsternant  路  4Comments