It only started from 0.88 with me and I did add the extra port and ssl but I think it’s luck that it has not failed again. Controversial Nigerian singer, Habeeb Okikiola, popularly known as Portable, has revealed why he refused to perform at the president-elect, Bola Tinubu’s Renewed Hope Concert in Abuja on Thursday. One change I did make yesterday was to specify the port: 8080 and ssl: false even those are the defaults and don’t need to be configured.Īnyway, you might think it’s fixed but it seems to be an intermittent problem. If you look in th e.py file you will see that it only does that persistent notification prompt for the API key when config via the API in config yaml fails… so if that fails and you have disabled discovery then the sabnzbd sensor won’t work at all. I entered it and it creates a nf in the donfig directory… But then when I restarted again, it would also come up with the config error in the log again and prompt AGAIN for me to enter the API key even though the conf file exists. When mine started doing this a couple of days ago, it started prompting via the persistent notification for the API key. We will probably ask you to do a test using only basic settings. It might get rid of the annoying persistent notification but it won’t work either. Check your connection in Status and Interface settings window. If you disable discovery, then if it isn’t detected via config and there is a config error then it won’t work at all. :( guess we need to call this out better in the readme since its hitting more people than expected. gotcha, explains the recent 'sab stopped working since upgrading to 3.3.x' ive seen reported now. Now all requests are verified the same way. Sometimes it works, sometimes it doesn’t and gives an error in the log. Because in previous versions, only requests to the frontend pages (not API) were passed through the hostname verification.

Sabnzbd refused to connect