cannot connect to Sickrage Web UI
|
Posts: 13
Threads: 5
Joined: May 2016
Reputation:
0
[Not Solved]
May 14, 2016, 07:44 AM
Hi, I installed SickRage using this guide http://www.htpcguides.com/install-sickra...ntu-14-04/ and all worked well but I cannot get to the web UI. I keep getting Connection refused. when I display which ports the server is listening on port 8081 is not there. I am using Ubuntu 14.04 Server version.
can anybody advise on what I am doing wrong?
(I have been away from Linux for a long time)
Thanks Andre
Posts: 1,646
Threads: 2
Joined: Aug 2015
Reputation:
42
[Not Solved]
May 14, 2016, 08:41 AM
What happens when you run Sickrage manually?
Code:
python /opt/sickrage/SickBeard.py
Posts: 13
Threads: 5
Joined: May 2016
Reputation:
0
[Not Solved]
May 14, 2016, 09:09 AM
(This post was last modified: May 14, 2016, 10:23 AM by dragon_reborn.)
(May 14, 2016, 08:41 AM)Mike Wrote: What happens when you run Sickrage manually?
Code:
python /opt/sickrage/SickBeard.py
Hi Mike, a huge amount of messages are scrolling by. Where is the log file saved? --found it in var/log/syslog I see this after starting sickrage manually.
May 14 10:47:41 mage-PC kernel: [176352.310201] init: sickrage main process (11610) terminated with status 1
where can I fend the logs specific for SickRage?
Posts: 13
Threads: 5
Joined: May 2016
Reputation:
0
[Not Solved]
May 14, 2016, 11:37 AM
(May 14, 2016, 09:09 AM)dragon_reborn Wrote: (May 14, 2016, 08:41 AM)Mike Wrote: What happens when you run Sickrage manually?
Code:
python /opt/sickrage/SickBeard.py
Hi Mike, a huge amount of messages are scrolling by. Where is the log file saved? --found it in var/log/syslog I see this after starting sickrage manually.
May 14 10:47:41 mage-PC kernel: [176352.310201] init: sickrage main process (11610) terminated with status 1
where can I fend the logs specific for SickRage?
after starting it manually when I try access the Web UI it connects but now I get a different message:
[Errno 2] No such file or directory: u'/opt/sickrage/cache/mako/layouts/main.mako.py'
Posts: 1,646
Threads: 2
Joined: Aug 2015
Reputation:
42
[Not Solved]
May 14, 2016, 12:48 PM
My guess would be the init.d script has an incorrect user.
That error for mako could just be temporary, if everything displays and works properly in the web interface I wouldn't worry about it.
Posts: 13
Threads: 5
Joined: May 2016
Reputation:
0
[Not Solved]
May 14, 2016, 03:38 PM
(This post was last modified: May 14, 2016, 03:43 PM by dragon_reborn.)
(May 14, 2016, 12:48 PM)Mike Wrote: My guess would be the init.d script has an incorrect user.
That error for mako could just be temporary, if everything displays and works properly in the web interface I wouldn't worry about it.
thanks, I checked the init.d and it refers to /etc/default/sickrage which I checked and it has the correct user recorded. Still the same issue "connection Refused"
This site can’t be reached
XXXXX refused to connect.
ERR_CONNECTION_REFUSED
(May 14, 2016, 03:38 PM)dragon_reborn Wrote: (May 14, 2016, 12:48 PM)Mike Wrote: My guess would be the init.d script has an incorrect user.
That error for mako could just be temporary, if everything displays and works properly in the web interface I wouldn't worry about it.
thanks, I checked the init.d and it refers to /etc/default/sickrage which I checked and it has the correct user recorded. Still the same issue "connection Refused"
This site can’t be reached
XXXXX refused to connect.
ERR_CONNECTION_REFUSED
if I run sudo python /opt/sickrage/SickBeard.py -d and try and conect via the web i juts get a blank screen... Is ther a manual somewhere for Sickrage? maybe I need to RTFM.
Posts: 1,646
Threads: 2
Joined: Aug 2015
Reputation:
42
[Not Solved]
May 14, 2016, 03:52 PM
Remove -d so you don't daemonize
Posts: 13
Threads: 5
Joined: May 2016
Reputation:
0
[Not Solved]
May 14, 2016, 04:17 PM
(May 14, 2016, 03:52 PM)Mike Wrote: Remove -d so you don't daemonize
I did but now I just get a blank screen on Chrome when trying to connect
Posts: 1,646
Threads: 2
Joined: Aug 2015
Reputation:
42
[Not Solved]
May 14, 2016, 04:51 PM
Weird, even with -d I have it working. Just tried on a fresh Ubuntu 14.04 using this guide. Using init.d and not upstart.
|
|
Recent Posts
|
Split Tunnel Docker Containers
jonesPhedra Mar 27, 2024, 03:10 AM
|
Plex server not powerful enough, but only with s...
jonesPhedra Mar 27, 2024, 03:02 AM
|
About Swap
jonescelinaa Mar 18, 2024, 02:11 AM
|
game Geometry Dash Scratch
jonescelinaa Jan 31, 2024, 04:21 AM
|
Find My IP Address - Kodi - Updated
jonesPhedra Jan 29, 2024, 02:56 AM
|
Latest unread posts | Unanswered posts |
|