Skip to content
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

Trouble Connecting to Sickbeard #6

Open
kcross88 opened this issue Sep 18, 2012 · 21 comments
Open

Trouble Connecting to Sickbeard #6

kcross88 opened this issue Sep 18, 2012 · 21 comments

Comments

@kcross88
Copy link

I have an issue connecting to sickbeard. I believe the issue may be caused by the version I am running, sickbeard alpha the pirate bay. Is there something I am missing or is this the issue? I have used the ip address, correct port, api key (tried one and generated another and tried that as well) username and password. I have tried with and without the https enabled. I purchased the app through google play and would appreciate any help given, and am still happy to support the cause even if it doesn't work with this version. Thanks for the app, much appreciated.

Not sure how to pull a log but if someone can walk me through it I would be more than willing. the error I am receiving says:

"error retrieving results
ERROR: failed to connect to /192.168.1.128 (port 8081) after 30000ms"

@johnou
Copy link
Collaborator

johnou commented Sep 18, 2012

API is enabled in SickBeard? Can you access the SickBeard web interface from other machines on the network (firewall)?

@kcross88
Copy link
Author

API is enabled in SickBeard. Haven't tried it on another computer. Should I
just try with IP:Port or something else (Not sure of the path to check with
API)? Thanks again.

@johnou
Copy link
Collaborator

johnou commented Sep 18, 2012

If you haven't specified a context IP:Port should be enough to test it => http://192.168.1.128:8081

@kcross88
Copy link
Author

Thanks again, I will test this as soon as I get home after work and will
report back.

@dmstocking
Copy link
Owner

If http://192.168.1.128:8081 doesn't work, add a rule to your firewall to open 8081. Another test would be to see if you can access SABnzbd+ on a different machine as well. (or an android app for SABnzbd+) I'm guessing its just a networking/firewall problem, but you can never be to sure.

@kcross88
Copy link
Author

I'll try both as soon as I get home today. I don't know if this helps out
at all, but I also bought couch tatertot and it works perfect.

@kcross88
Copy link
Author

Opening up a firewall worked perfect. Thanks a ton again. The help is very
appreciated.

@P71Ryan
Copy link

P71Ryan commented Sep 19, 2012

I'm having trouble connecting as well, it shows: "Error: Retrieving Results" and "Error: No route to host" My API is correct and the port is the default 8081. I've tried "local host" and the IP I get from the website, whatsmyip.com. I allowed network/public for the firewall.

@kcross88
Copy link
Author

I'm not an expert by any means, but the ip from whats my ip is a little
different. That's the external ip, you want internal. Local host would be
referring to the current computer you are on I believe. Assuming you are
using this on wifi and on windows 7, go to network and sharing center (in
control panel or on the taskbar) click on the link next to connections,
click details. It will most likely be next to IPv4 blah blah. Try that one
instead. Mines 192.168.1.128, something like that.

If thats not the issue, then it could be the port problem like I had. Also,
you may want to set up a static internal ip so it doesn't change when you
reset your router or modem.

Anyone feel free to correct me if I'm wrong on any of this.

Thanks,

@P71Ryan
Copy link

P71Ryan commented Sep 19, 2012

That worked perfectly! Thanks for the fast and effective response. I tried just about every 192.168.XX I found under my wireless settings except this one lol

@kcross88
Copy link
Author

Also I setup sick beard for private network and I still had manually go in
and make a rule in my firewall for that specific port.

@dmstocking
Copy link
Owner

TODO write a FAQ in the wiki and add links to it in all the forum pots/google play/in app.

@dmstocking
Copy link
Owner

https://github.com/Buttink/sick-stache/wiki/FAQ What else is needs explaining?

@johnou
Copy link
Collaborator

johnou commented Sep 19, 2012

Explaining that using a hostname instead might be more robust on a private network unless the devices have a static IP. Port forwarding, perhaps. Dynamic DNS for those who want to access the information remotely and do not have a static IP?

@dmstocking
Copy link
Owner

I wrote a bit about it. Anything more, and I feel like they should start googling better resources for it.

@dmstocking
Copy link
Owner

I hope the help link to the FAQ fixes this. I'm not going to close this so more people can give feedback.

@zoopz
Copy link

zoopz commented Nov 13, 2012

I also am not able to connect. I can connect fine using a web browser. The error message is: "ERROR: http://192.168.0.9:8081/home//api/******/?cmd=shows", where ***** is the API key.

@dmstocking
Copy link
Owner

Take out the "/" in your path variable so its just "home"

EDIT: Nope nevermind what I said. Try to go to http://192.168.0.9:8081/home on your phone. If that works try.

http://192.168.0.9:8081/home/api/******/?cmd=shows on your computer.

Plus, make sure your on your wifi and not 3/4G. Your 3/4G is on a different network from your wifi.

@dmstocking
Copy link
Owner

I wonder if zoopz fixed his issue.

@zoopz
Copy link

zoopz commented Nov 15, 2012

Well, the strange thing is I didnt have any path defined. After I came home from work I decided to see if it would work on my tablet (galaxy 8.9). It took two reboots to configure SickStache (it would freeze my tablet), but after that it worked - and fast! I picked up my phone to check the settings again, but now that made a connection as well. So I don't know how this happened - but hey my problem is solved :)

@dmstocking
Copy link
Owner

There is a bug where it will crash on first use. I found this out myself on another phone. The auto home part is weird to. I have been doing job interviews and working on a different project, but its about time I stop being lazy and fix these known issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants