SABnzbd Forums

just upgraded to 1.2.1RC1 [af92797] on ubuntu. Now I'm have IPv6 issues.

I have 2 accounts with a host. I use one for IPv4 and one for IPv6. I manually resolved the host name to IP address for each and place the explicit IP addresses in the server Host fields. I connect fine for the IPv4 but I get errors with the IPv6 address.

Thanks in advance for advise.

Could you post the address so we can test?

Sure, here you go. -- Thanks
2001:67c:174:101::237

Other warnings I see that may or may not be related:
"Warning Secure (SSL) connections from SABnzbd to newsservers and HTTPS websites will be encrypted, however, validating a server's identity using its certificates is not possible. Python 2.7.9 or above, OpenSSL 1.0.2 or above and up-to-date local CA certificates are required."
and
Nameserver / DNS LookupConnection failed!

Nameserver / DNS Lookup Connection failed!

Ah! Now I start to understand your problem and your posts: your DNS lookup is broken. You have to solve that first.

On the command line, what happens when you type
(The message about SSL just means you have an old Python (<2.7.9), which is the case on Ubuntu 14.04. It's not related to your DNS problem)

Here is what I got when I ran those commands.

xxxx@xxxxxx::~$ ping -c4 www.google.com
PING www.google.com (172.217.3.164) 56(84) bytes of data.
64 bytes from sea15s11-in-f4.1e100.net (172.217.3.164): icmp_req=1 ttl=54 time=6.26 ms
64 bytes from sea15s11-in-f4.1e100.net (172.217.3.164): icmp_req=2 ttl=54 time=6.47 ms
64 bytes from sea15s11-in-f4.1e100.net (172.217.3.164): icmp_req=3 ttl=54 time=6.36 ms
64 bytes from sea15s11-in-f164.1e100.net (172.217.3.164): icmp_req=4 ttl=54 time=6.27 ms

--- www.google.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3001ms
rtt min/avg/max/mdev = 6.265/6.343/6.475/0.085 ms
xxxx@xxxxxx:~$ ping -c4 test.xennanews.com
PING test.xennanews.com (91.223.220.236) 56(84) bytes of data.
64 bytes from test.xennanews.com (91.223.220.236): icmp_req=1 ttl=44 time=152 ms
64 bytes from test.xennanews.com (91.223.220.236): icmp_req=2 ttl=44 time=152 ms
64 bytes from test.xennanews.com (91.223.220.236): icmp_req=3 ttl=44 time=152 ms
64 bytes from test.xennanews.com (91.223.220.236): icmp_req=4 ttl=44 time=152 ms

--- test.xennanews.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3001ms
rtt min/avg/max/mdev = 152.068/152.286/152.634/0.448 ms
xxxx@xxxxxx::~$ ping6 -c4 test.xennanews.com
PING test.xennanews.com(test.xennanews.com) 56 data bytes
64 bytes from test.xennanews.com: icmp_seq=1 ttl=57 time=148 ms
64 bytes from test.xennanews.com: icmp_seq=2 ttl=57 time=148 ms
64 bytes from test.xennanews.com: icmp_seq=3 ttl=57 time=148 ms
64 bytes from test.xennanews.com: icmp_seq=4 ttl=57 time=148 ms

--- test.xennanews.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3000ms
rtt min/avg/max/mdev = 148.227/148.510/148.971/0.475 ms

Oh, your DNS is working correctly...?!

Back to your original statement:

Now I'm have IPv6 issues.

I have 2 accounts with a host. I use one for IPv4 and one for IPv6. I manually resolved the host name to IP address for each and place the explicit IP addresses in the server Host fields. I connect fine for the IPv4 but I get errors with the IPv6 address.

Why do you fill out IPv4/IPv6 addresses?
What is the newsserver you want to use?
What is the exact error you get?
What do get when you click on Test Server
If you fill out newszilla6.xs4all.nl as newsserver (no username/password needed) and click on Test Server, what do you get?

In the Status windows, is there an IPv6 address? If so, what are the first symbols?

I'm confused. Testing newszilla6.xs4all.nl inside sabnzbd returns " Server quit during login sequence." However from the command line on the same machine
behaves correctly

All ipv6 address in sabnzbd are returning that same error code. Regardless of explicit IP or needing a DNS lookup

My IPV6 related settings are:
Server load-balancing -- Prevent Load balancing // I did this because I was getting too many connection errors from Astraweb a while back
ipv6_hosting ( off )
ipv6_servers ( 1 )

I'm using a Netgear router supplied IPV6to4 tunnel and get 7/10 from http://test-ipv6.com/. All worked fine on the previous build of sabnzbd I was using. I think I was a build of 1.1. Also, I configured Ubuntu to prefer iPv4 over IPV6 because the tunnel is far less efficient. Here is how: https://community.rackspace.com/products/f/25/t/5110

Now to your questions:
Why do you fill out IPv4/IPv6 addresses? xennanews provides free accounts. I grabbed a couple. They only allow 1 account per IP. I saw they had an IPV6 address. The tunnel acts as another IP that doesn't trip their 1 account per IP checker. Hard coding the IPs fixes the account to IPv4 or IPv6
What is the newsserver you want to use? test.xennanews.com
What is the exact error you get?
Failed to initialize [email protected]@1 with reason: [Errno 99] Address not available - Check for internet or DNS problems
What do get when you click on Test Server- " Server quit during login sequence."
If you fill out newszilla6.xs4all.nl as newsserver (no username/password needed) and click on Test Server, what do you get? " Server quit during login sequence."

In the Status windows, is there an IPv6 address? If so, what are the first symbols? IPv6 address 2002:.......

I would do this:

Stop SABnzbd.
Check and re-check SAB is not running anymore
Start SAB with "sabnzbdplus -f sab-ipv6-test.ini" (so a fresh ini)
Fill out the wizard with newszilla6.xs4all.nl. Click on Test Server. Post the result here.
Complete the wizard.

Warning: newszilla6.xs4all.nl has a retention of one week or so, so you can only download very recent stuff.

I get "Connection Successful!" after a fresh ini. I'm guessing my next steps are to stash my working ini and build a new one?

usemitysam wrote:I get "Connection Successful!" after a fresh ini. I'm guessing my next steps are to stash my working ini and build a new one?

Yes, indeed!

Thanks for the help. I'm all fixed up now. The only thing that had me scratching my head for a moment was using 0.0.0.0 for local subnet access. After that, it all went smooth. Thanks