Page 1 of 1

CouchPotato no longer accessible via browser

PostPosted: Sun Dec 02, 2018 3:47 am
by JeremyCreekit
I've used CouchPotato successfully for years but recently I've been unable to access it via my browser.

This issue specifically seems to be affecting Headphones and CouchPotato for me. However, the following apps are all still working as usual: SABNZBD, Sonarr, Mylar and Deluge. It's just CouchPotato and Headphones that I can't access via my browser.

I've tried the following:

1) Disabling and re-enabling the app through the ADM App Central has no effect

2) Whenever my NAS turns off due to a power outage, I need to delete the .pid file for the app and manually restart it with the following commands, which are not working in this case:

Code: Select all
rm -rf /usr/local/AppCentral/couchpotato/couchpotato.pid
/usr/local/AppCentral/couchpotato/CONTROL/start-stop.sh restart


3) Sometimes, I need to manually re-enable port forwarding for certain apps after updates and/or crashes by going to Settings > Manual Connect > EZ-Router. However, in this case, disabling and renabling port forwarding is having no effect.

Any ideas on what could be wrong? Thanks!

Re: CouchPotato no longer accessible via browser

PostPosted: Thu Dec 13, 2018 8:44 pm
by JeremyCreekit
*BUMP

Re: CouchPotato no longer accessible via browser

PostPosted: Fri Dec 14, 2018 6:51 pm
by Marco@ASUSTOR
JeremyCreekit wrote:*BUMP

Perhaps contact CouchPotato devs? Maybe they'd know a way to help you.

Re: CouchPotato no longer accessible via browser

PostPosted: Sun Dec 16, 2018 3:49 pm
by JeremyCreekit
Thanks. I thought it might relate to the specific Asustor implementation but I can do that...

Re: CouchPotato no longer accessible via browser

PostPosted: Mon Dec 17, 2018 9:48 am
by Marco@ASUSTOR
JeremyCreekit wrote:Thanks. I thought it might relate to the specific Asustor implementation but I can do that...

Sorry dude, it's a third party app, we just put it on the store, that's it.

Re: CouchPotato no longer accessible via browser

PostPosted: Wed Feb 06, 2019 3:53 am
by clinton.hall
The issue here is that a power failure can result in a corruption of the database if the CP is writing to it at the time.
Even if the database is ok, you will need to delete the pid file before restarting the app (as per your first post).

Best solution is a small USB that keeps power to the NAS and triggers a safe shutdown. I have never had an issue with CP of HP when using a UPS.

Re: CouchPotato no longer accessible via browser

PostPosted: Wed Feb 06, 2019 4:05 am
by JeremyCreekit
Thanks Clinton :)

I'd previously used these commands to restart apps after losing power.

Code: Select all
rm -rf /usr/local/AppCentral/couchpotato/couchpotato.pid
/usr/local/AppCentral/couchpotato/CONTROL/start-stop.sh restart


Worked for all the other apps except CouchPotato, but I do think it has something to do with losing power. In the end, I uninstalled the app via App Central and reinstalled it which worked (lost all my settings but oh well).

Re: CouchPotato no longer accessible via browser

PostPosted: Wed Feb 06, 2019 1:15 pm
by clinton.hall
make a (semi-regular) backup of /usr/local/AppCentral/couchpotato/config
that way after re-installing, you just stop the app, restore the backup, and you should have everything again.

Re: CouchPotato no longer accessible via browser

PostPosted: Mon Feb 11, 2019 5:57 pm
by JeremyCreekit
Thanks :)