Page 1 of 1

Disable incorrect API warnings?

Posted: January 13th, 2021, 6:09 pm
by FlexibleToast
I setup Sab in a Kubernetes cluster and it's reporting constant api key warnings. They're coming from Traefik my ingress controller which I think is just checking the health of the connection. I went to Config > Special and unchecked api_warnings then restarted Sab. I'm still getting the warnings. I even check the sabnzbd.ini and that option was set to 0. Under Config > Special it shows

Code: Select all

api_warnings ( on )
even though it is unchecked. There is what appears to be a giant asterisk next to it though if that means anything.

Re: Disable incorrect API warnings?

Posted: January 14th, 2021, 1:11 am
by sander
In "api_warnings ( on )" the "on" means the default value. Not the current value.

Re: Disable incorrect API warnings?

Posted: January 14th, 2021, 3:16 am
by safihre
What are the warnings you are getting?
You can also check the mode=auth API-call which has no authentication and as such no errors.

Re: Disable incorrect API warnings?

Posted: January 15th, 2021, 11:15 am
by FlexibleToast
safihre wrote: January 14th, 2021, 3:16 am What are the warnings you are getting?
You can also check the mode=auth API-call which has no authentication and as such no errors.

Code: Select all

 	
WARNING a few seconds ago API key incorrect, Use the API key from Config->General in your 3rd party program: 10.42.1.79 (X-Forwarded-For: 10.42.1.76)>okhttp/3.14.6
Which is my ingress controller.

Code: Select all

$ k get pods -A -o wide | grep 10.42.1.79
kube-system               traefik-5dd496474-wt2d2                      1/1     Running   2          45h     10.42.1.79      pikubed-m1   <none>           <none>

Re: Disable incorrect API warnings?

Posted: January 15th, 2021, 12:42 pm
by FlexibleToast
I think I found the issue. Seems that even though I changed the API in Hydra, the setting didn't stick. I had to actually delete SabNZBD from Hydra and re-add it. I haven't received the errors since then. Guess it wasn't Traefik itself, it was Hydra trying to ingress through Traefik... Which I thought I set to use the service directly. Solved both those problems.