Page 1 of 1

Crashes on start after adding invalid listening address

Posted: March 30th, 2021, 1:51 pm
by fizzbin
Woops, I wasn't thinking and entered "192. 168.0.1" as the listening address instead of "127. 0.0.1" now SABnzb crashes when it starts. I couldn't find what file this is stored in -- any advice?

Code: Select all

2021-03-30 11:38:44,495::INFO::[SABnzbd:1431] Starting web-interface on 192 .168.0.1: 8080
2021-03-30 11:38:44,495::INFO::[_cplogging:213] [30/Mar/2021:11:38:44] ENGINE Bus STARTING
2021-03-30 11:38:44,597::INFO::[notifier:122] Sending notification: Error - [30/Mar/2021:11:38:44] ENGINE Error in HTTP server: shutting down
Traceback (most recent call last):
  File "cherrypy \process \servers. py", line 225, in _start_http_thread
     File "cheroot\ server. py", line 1836, in start
  File "cheroot\ server.  py", line 1791, in prepare
    OSError No socket could be created -- (('192. 168.0. 1', 8080): [WinError 10049] The requested address is not valid in its context)
 (type=error, job_cat=None)
 2021-03-30 11:38:44,597::ERROR::[_cplogging: 213] [30/ Mar/ 2021:11:38:44] ENGINE Error in HTTP server: shutting down
Traceback (most recent call last):
  File "cherrypy \process\ servers. py", line 225, in _start_http_thread
  File "cheroot \server py", line 1836, in start
  File "cheroot \server. py", line 1791, in prepare
OSError: No socket could be created -- (('192.168.0.1', 8080): [WinError 10049] The requested address is not valid in its context)
btw, the board thought the python files were links and wouldn't let me make this post until I butchered them.

Re: Crashes on start after adding invalid listening address

Posted: March 30th, 2021, 2:03 pm
by sander
it's stored in the file sabnzbd.ini.

BUT ... :
- you can start SAB with "sabnzbd.exe -s 0.0.0.0" and it will be fine
- AFAIK, on Windows, you might also right-click the SAB item in the bottom bar (if the icon is there ...), and then select "start safely" or something like that. Typing this on Linux, so I can't verify.

Re: Crashes on start after adding invalid listening address

Posted: March 30th, 2021, 2:11 pm
by fizzbin
Thanks! I used -s and that got me back.