SABnzbd Forums

Hi all,

I have sabnzbd installed on my Windows Server 2012 behind an ASUS AC66U.

Whenever I login the ASUS web interface: https://192.168.1.1:8443/Main_Login.asp and I start the SABNZBD webpage: https://192.168.1.100:9090 I get below error:
Once I remove the cooking called traffic_warning_0, I get a different error: And so on. There are around 3-4 cooking which I need to clear to ensure I can login the sabnzbd portal again.
What I found out is that all these cooking come from the ASUS web interface after logging in.

- asus_token
- traffic_warning_0
- wireless_list*



Is there any way to ensure SABNZBD accepts these cookies? My understanding is that CherryPy checks the cooking names and sees this one as invalid? But it isn't even using this cooking right?

Thanks in advance.

joaor wrote: ↑May 29th, 2017, 6:09 am
Is there any way to ensure SABNZBD accepts these cookies? My understanding is that CherryPy checks the cooking names and sees this one as invalid? But it isn't even using this cooking right?

Thanks in advance.

So is there a way to do this?

The ASUS is setting illegal cookies using the colon in the cookie name, making the SABnzbd webserver unable to continue processing.
It's kind of strange that they share cookies, if both using different IPs.

Usually it helps to for example access SABnzbd through the device-name instead of the IP-address, if this is possible. Or run in incognito-mode for the bad device that makes the bad cookies, so they don't get saved.