SABnzbd Forums

Platform: Win7
sab: 0.7.18

Case: Change of https port via API call not taken into account after reboot of sabnzbd (although it will appear well in the field). It is not the case if manually changing it via configuration panel and clicking save button, that would work. NB: if rebooting the computer then the https port is taken into account, I guess something works at first launch that doesnt when rebooting sabnzbd.

Test: Change https port via API call, either try to reboot via API or Configuration reboot button, and double click on the sabnzbd tray icon, you'll see that new https port has not been taken into account in the URL. Test failed.

Level: Truly annoying.

Tell me if this works on your side.

Cheers

Likely never to have been tested.
I'll have a look.
Just to satisfy my curiosity: any particular reason to do this over the API?

I guess you deserve an answer if you have a look at it :-p
My VPN "port forwarding" is changing every two hours, I'm using the sabnzbd API to be aligned with the new port.
And when it is not aligned, no more access from any external tool (ex: SABMobile) !
Now you see why it is annoying ;-)

Works for me.
However, are you using the right keyword?
SABnzbd's configuration is a little weird in this area (historical reasons).
When you enable ONLY https, then the "port" field is used to get the https port number.
When you enable both http and https, "port" is for http and "https_port" is for https.

yes sir, were here talking about the https_port.
Did you try full API test? Changing https_port+reboot via API? Is this on windows? As I said it appears modified in the field but the exe or service is still connected to old port somehow.

ok it seems i had a bad call of reboot function in my code after refactoring. sorry about that and thanks for your help!

No problem. At least the function has been tested now, by both you and me.