{"action":"created","issue":{"url":"https://api.github.com/repos/SickRage/sickrage-issues/issues/1067","repository_url":"https://api.github.com/repos/SickRage/sickrage-issues","labels_url":"https://api.github.com/repos/SickRage/sickrage-issues/issues/1067/labels{/name}","comments_url":"https://api.github.com/repos/SickRage/sickrage-issues/issues/1067/comments","events_url":"https://api.github.com/repos/SickRage/sickrage-issues/issues/1067/events","html_url":"https://github.com/SickRage/sickrage-issues/issues/1067","id":136916539,"number":1067,"title":"Pb \"unable to connect provider\"","user":{"login":"tyflops","id":8401839,"avatar_url":"https://avatars.githubusercontent.com/u/8401839?v=3","gravatar_id":"","url":"https://api.github.com/users/tyflops","html_url":"https://github.com/tyflops","followers_url":"https://api.github.com/users/tyflops/followers","following_url":"https://api.github.com/users/tyflops/following{/other_user}","gists_url":"https://api.github.com/users/tyflops/gists{/gist_id}","starred_url":"https://api.github.com/users/tyflops/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tyflops/subscriptions","organizations_url":"https://api.github.com/users/tyflops/orgs","repos_url":"https://api.github.com/users/tyflops/repos","events_url":"https://api.github.com/users/tyflops/events{/privacy}","received_events_url":"https://api.github.com/users/tyflops/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2016-02-27T13:04:46Z","updated_at":"2016-02-27T13:04:47Z","closed_at":null,"body":"Branch: master\r\nCommit: 1ee61ed7e0a1b31fc5b6d10f3df6d9ff3ade141a\r\nVersion: 2016.02.22-1\r\nOS: synology\r\nWhat you did: episode search \r\nWhat happened:  impossible to connect provider T411 since one week ...\r\nLog : \"2016-02-27 14:00:24 WARNING  SEARCHQUEUE-MANUAL-161511 :: [T411] :: Unable to connect to provider [1ee61ed]\"\r\n\r\n(it was ok before for this provider, all others providers is ok for now)\r\n\r\nIs there something i have to do ? is someone have the same pb ?"},"comment":{"url":"https://api.github.com/repos/SickRage/sickrage-issues/issues/comments/189634929","html_url":"https://github.com/SickRage/sickrage-issues/issues/1067#issuecomment-189634929","issue_url":"https://api.github.com/repos/SickRage/sickrage-issues/issues/1067","id":189634929,"user":{"login":"SickRage2","id":15840237,"avatar_url":"https://avatars.githubusercontent.com/u/15840237?v=3","gravatar_id":"","url":"https://api.github.com/users/SickRage2","html_url":"https://github.com/SickRage2","followers_url":"https://api.github.com/users/SickRage2/followers","following_url":"https://api.github.com/users/SickRage2/following{/other_user}","gists_url":"https://api.github.com/users/SickRage2/gists{/gist_id}","starred_url":"https://api.github.com/users/SickRage2/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/SickRage2/subscriptions","organizations_url":"https://api.github.com/users/SickRage2/orgs","repos_url":"https://api.github.com/users/SickRage2/repos","events_url":"https://api.github.com/users/SickRage2/events{/privacy}","received_events_url":"https://api.github.com/users/SickRage2/received_events","type":"User","site_admin":false},"created_at":"2016-02-27T13:04:47Z","updated_at":"2016-02-27T13:04:47Z","body":"Thanks for the issue report! Before a real human comes by, please make sure your report has all the below criteria checked\n\n- [ ] Include basic information: Branch/Commit, OS, What you did, What happened, What you expected\n- [ ] Enable debug logging (be sure to disable after the bug is fixed)\n- [x] Post debug logs, either inline (for smaller logs) or using gist\n- [ ] Please wrap inline logs inside \\`\\`\\` and \\`\\`\\` for readability\n\nPlease make sure you also read [how to create an issue](https://github.com/SickRage/sickrage-issues/blob/master/README.md) and followed all of the steps. \n\nThe title should describe your issue. Having \"SR not working\" or \"I get this bug\" for 100 issues, isn't really helpful. We will close issues if there isn't enough information.\n\nSometimes the devs may seem like grunts and respond with short answers. This isn't (always) because the dev hates you, but because he's on mobile or busy fixing bugs. If something isn't clear, please let us know, and this bot may get updated to automatically answer you.\n\nThanks!"}}