CLOSED: SABNZBD Screw Up
Posted: Sun Oct 02, 2016 10:53 am
Hey,
I would have normally posted this in the appropriate SABNZBD forum, but i think the solution to this issue is simple and it belongs in the NOOB section. I know exactly how i screwed the pooch but i cant figure out how to get where i need to go to fix it. I was working with my usenet indexer to download directly from them (i use couch potato normally). My SABNZBD was set to listen to 0.0.0.0 and worked fine. The genius move was to put it to http://localhost:25915/ as i thought this would get me direct access to the indexer. Rebooting was part of the change and lo and behold i received a 503 error - "The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later." I noticed the SABNZBD server was not running and would not start. I rebooted the server and still receive the same error.
I have a feeling i need to get into file to manually change the "http://localhost:25915/" screw up back to the 0.0.0.0 address which worked...the problem is...i cant figure out how to get to the specific area to do so.
Any help here would be appreciated...
Your Noobian Friend
bird
I would have normally posted this in the appropriate SABNZBD forum, but i think the solution to this issue is simple and it belongs in the NOOB section. I know exactly how i screwed the pooch but i cant figure out how to get where i need to go to fix it. I was working with my usenet indexer to download directly from them (i use couch potato normally). My SABNZBD was set to listen to 0.0.0.0 and worked fine. The genius move was to put it to http://localhost:25915/ as i thought this would get me direct access to the indexer. Rebooting was part of the change and lo and behold i received a 503 error - "The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later." I noticed the SABNZBD server was not running and would not start. I rebooted the server and still receive the same error.
I have a feeling i need to get into file to manually change the "http://localhost:25915/" screw up back to the 0.0.0.0 address which worked...the problem is...i cant figure out how to get to the specific area to do so.
Any help here would be appreciated...
Your Noobian Friend
bird