0.6.2 Final NZB association still not working

[kawasabi]

It just won't work for me on Win 7 https...
Same problem as 0.6.1 where it just starts another copy of sabnzbd.

[psa]

What do you mean, when you try to double click an NZB it's not automatically sent to SAB?

[kawasabi]

What do you mean, when you try to double click an NZB it's not automatically sent to SAB?

Yes exactly that.

[shypike]

How do you start the first instance?
The second instance will check the registry for the URL of the first one.
Can you check with regedit?
It shoud have this key:
HKEY_CURRENT_USER\Software\SABnzbd\api\url

BTW: stop all instances first and then start one.

[kawasabi]

The first instance is auto started with windows.
The second instance is only starting when i double click an nzb.
After killing the two instances and start sabnzbd again the imported nzb is in the queue.

I do have the reg-key, it's there.

[shypike]

Do you have only one version of SABnzbd on your system?
If you start one version at startup and have another one
associated with NZB, the the two will refuse to communicate.

Just to make sure.
Can you stop all instances and start one with host address 127.0.0.1 instead of localhost?

[kawasabi]

I do have only one sabnzbd installed.

127.0.0.1 instead of localhost works!

[shypike]

Totally weird.
The cause of the whole issue is that 0.6.1 did not work when localhost was [::1] (IPV6)
instead of 127.0.0.1 (IPV4).
The work-around was extensively tested.
I have no explanation why it doesn't work on your system.

[kawasabi]

Thanks anyway for the feedback.

[sheytoon]

Hi,

Just wanted to say I had the exact same issues.
Win7 would start the first instance during bootup on the configured port (9100 for me on https). RSS feeds would queue up fine in that instance, but any manual nzb downloads would start a new instance on a new port. These new downloads were not visible in the old queue (port 9100), but the files would finish downloading and post-process correctly. I found the new instance incremented the port by 5 (new port was 9105 on https).

I can also confirm I only had one version of sabnzbd installed (0.6.2).

Unfortunately, this was a deal-breaker for me, so I switched back to 0.5.6 and everything is working again.
Hope you are able to solve the issue.

[Faust42]

Hello.

Just wanted to confirm that on Win7 SP1 x64 + sab 0.6.2, switching from localhost to 127.0.0.1 solved the https interface\multiple instances problem.

Thank you.

[shypike]

Hope you are able to solve the issue.

0.6.2 works around the specific problem of localhost resolving to an IPV6 address
(thank you Microsoft  )
The work-arounds listed for 0.6.1 still work for 0.6.2.
The simplest fix is to set SABnzbd's host address to 127.0.0.1.

[sheytoon]

I'm no expert, so apologies if what I'm asking doesn't make any sense... but why is there a difference in behaviour between 0.5.6 and 0.6.2. In both versions, the URL I'm typing in my browser is https://localhost:port, but it works fine in 0.5.6, and not in 0.6.2.

I understand using 127.0.0.1 will fix everything, but why the difference in the first place?

[shypike]

Release 0.5.6 has the same problem.
Only you never notice it because you cannot have an HTTPS-only setup.
0.5.6 will always use two ports when you want HTTPS,
so there will always be a HTTP port available.

So in fact, you will only have the problem if you want to use the HTTPS-only feature of 0.6.x

[sheytoon]

I see, thanks very much for the explanation!