SickBeard

User avatar
bigfoot65
Project Manager
Posts: 11924
Joined: Mon May 25, 2009 4:31 pm

Re: SickBeard

Postby bigfoot65 » Wed Dec 01, 2010 4:41 pm

Try changing localhost to sickbeard. Sometimes that helps. It may be one of those apps that is not accessible via web-apps proxy outside the LAN.
ßîgƒσστ65
Applications Manager

My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2

silentsoul
Posts: 22
Joined: Tue Aug 10, 2010 4:14 pm

Re: SickBeard

Postby silentsoul » Wed Dec 01, 2010 6:50 pm

Try changing localhost to sickbeard. Sometimes that helps. It may be one of those apps that is not accessible via web-apps proxy outside the LAN.
Tried that too, the issue now is no matter what i cannot access sickbeard it anymore. even from inside the LAN, I still get redirected to localhost:8081

:?:

Kinda at a loss now.

riyadc
Posts: 5
Joined: Thu Nov 25, 2010 2:54 am

Re: SickBeard

Postby riyadc » Wed Dec 01, 2010 8:37 pm

When you tell it to redirect to localhost:8081 your browser is basically looking at itself.
You need to put in silentsoul.yourhda.com:8081 as your redirect address and make your router forward port 8081 to the internal address of your amahi (eg 192.168.1.10).

I use my own domain name and that makes it much easier to access apps from the outside, all you have to do is tell the DNS provider of your domain to forwards sickbeard.yourdomain.com to yourname.yourhda.com. Here is a guide to have multiple apps hosted easily (if you have your own domain though): http://wiki.amahi.org/index.php/Hosting_a_website

stueyboy and dsk should be seeing the sickbeard on your app list now.

silentsoul
Posts: 22
Joined: Tue Aug 10, 2010 4:14 pm

Re: SickBeard

Postby silentsoul » Wed Dec 01, 2010 8:57 pm

When you tell it to redirect to localhost:8081 your browser is basically looking at itself.
You need to put in silentsoul.yourhda.com:8081 as your redirect address and make your router forward port 8081 to the internal address of your amahi (eg 192.168.1.10).

I use my own domain name and that makes it much easier to access apps from the outside, all you have to do is tell the DNS provider of your domain to forwards sickbeard.yourdomain.com to yourname.yourhda.com. Here is a guide to have multiple apps hosted easily (if you have your own domain though): http://wiki.amahi.org/index.php/Hosting_a_website

stueyboy and dsk should be seeing the sickbeard on your app list now.

Right I understand the local host deal, but i already forward port 80 from outside to work with Amahi. Let's forget the apps proxy issue for a second.

When i uninstall and reinstall the app sickbeard using the dashboard, I can no longer access it from inside my LAN.

When at the dashboard if I hover over 'sick beard' it shows the location http://sickbeard.*****.com/ which is correct. But when i click on the link it does not take me there it takes me to localhost:8081

When i type in http://sickbeard.*****.com/ I get the error:
Unable to connect
Firefox can't establish a connection to the server at localhost:8081.

So basically the app is completely broken for me now. i have rebooted the server and reinstalled the application twice.

riyadc
Posts: 5
Joined: Thu Nov 25, 2010 2:54 am

Re: SickBeard

Postby riyadc » Wed Dec 01, 2010 9:02 pm

It seems like a web-apps proxy issue. Can you post what your /etc/httpd/conf.d/100*-sickbeard.conf looks like after a uninstall and install?

Also we're on IRC if you wanna drop by, it'd be faster to get it resolved.

dsk
Posts: 9
Joined: Wed Dec 01, 2010 12:40 pm

Re: SickBeard

Postby dsk » Wed Dec 01, 2010 11:35 pm

Installed and testing it now.

stueyboy
Posts: 101
Joined: Tue Mar 09, 2010 2:54 am

Re: SickBeard

Postby stueyboy » Thu Dec 02, 2010 2:25 am

Thanks for the access folks. I'm probably doing something really thick here but I can't access the server and keep getting a 503: service unavailable error. The log file gives a connection refused HTTP type error and also ap_proxy_connect_backend disabling worker for (localhost) error. Perhaps I ought to leave it untile it's out of alpha testing as my knowledge is poor for diagnosing this sort of thing.

dsk
Posts: 9
Joined: Wed Dec 01, 2010 12:40 pm

Re: SickBeard

Postby dsk » Thu Dec 02, 2010 12:48 pm

Thanks for the access folks. I'm probably doing something really thick here but I can't access the server and keep getting a 503: service unavailable error. The log file gives a connection refused HTTP type error and also ap_proxy_connect_backend disabling worker for (localhost) error. Perhaps I ought to leave it untile it's out of alpha testing as my knowledge is poor for diagnosing this sort of thing.

As root:
/etc/init.d/sickbeard update

Fixed the same error for me. I got the error originally when clicking on the upgrade link within sickbeard.

stueyboy
Posts: 101
Joined: Tue Mar 09, 2010 2:54 am

Re: SickBeard

Postby stueyboy » Thu Dec 02, 2010 1:51 pm

Thanks. I was missing some dependencies which fixed it. Also need to gain read/write control of the directory as well as I got some premission errors when trying to write to the config file. Now it's working fine for me.

Now I need to get SABnzbd working. Just getting empty folder at the moment.

smartstradamus
Posts: 14
Joined: Tue Nov 30, 2010 5:28 pm

Re: SickBeard

Postby smartstradamus » Thu Dec 02, 2010 2:28 pm

HI riyadc

Could I get in on this action?
Sickbeard is a must have app for me and I would love to help in the testing of it.

Thanks

Who is online

Users browsing this forum: No registered users and 25 guests