-
Notifications
You must be signed in to change notification settings - Fork 178
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to connect to Sickbeard #360
Comments
Oh and I should mention that my sickbed instance is not using a web_root variable, so i have left the base path configuration empty in MTPC Manager. I have also tried thought putting in a / and even the /home/ that seems to be applied by sickbeard. |
If you just visit the module (ignore the test) does it work there? |
No unfortunately. I click on the menu item and it shows Sickbed, but does not list any of the shows i have configured to watch. |
If you try http://10.1.1.3:8081/api/b64467968765b2f49a00dd085753ef70/?cmd=sb.ping manually in your browser do you get a reponse from the api then? |
the "home" shouldnt be there if your not using a web_root. |
Hi,
This is likely to be something silly that i'm doing/not doing, but i can't for the life of me get HTPC manager to talk with Sickbed. I'm running a freeness box, I've configured the IP address, port and API key in HTPC manager for Sickbeard. Testing however fails, and when i look in the log, i see messages like
Unable to contact sickbeard via http://10.1.1.3:8081/home/api/b64467968765b2f49a00dd085753ef70/?cmd=sb.ping
If i however paste that URL into a new browser tab, it displays sickbeard fine. Any idea's?
The text was updated successfully, but these errors were encountered: