Unable to connect after updating to the newest version

Having trouble setting everything up? No worries, we'll help.

Re: Unable to connect after updating to the newest version

Postby Kanjar67 » Tue Dec 05, 2017 5:22 am

Hi Kev,
Thanks for the reply, I have tried with those numbers and format but was unsuccessful. So was trying to input the other. Ill put the issues I had again:
1) The remoteaddress.com (is this the ipaddress.com so 192.168.1.102.com? because the Test connection absolutely doesnt even try for long and fails soon)
2) The user:pass@remoteaddy.com (Username password for what? the router, the server, or SAB (SAB has no username or password) and whats remoteaddy?)
Kanjar67
 
Posts: 2
Joined: Sat Dec 02, 2017 10:39 am

Re: Unable to connect after updating to the newest version

Postby Kev » Tue Dec 05, 2017 5:27 am

1) Do you know your local IP address to your PC? If so, type that in after http:// and before the port. If your local IP address is 192.168.1.102, then type http://192.168.1.102:8080 into the Primary Connection String field.

2) If you're unfamiliar with the username here, then you don't need it :) SABnzbd is normally authenticated via the API key, not basic auth, so don't worry about it. Remoteaddy.com is just a shorter way of saying your remote address. It could be anything, so I chose the term "remote address" or "remote addy" for short. I'll make this clearer in a future update.
Developer of nzb360
User avatar
Kev
Site Admin
 
Posts: 1437
Joined: Mon Feb 24, 2014 2:29 am

Re: Unable to connect after updating to the newest version

Postby ce29f93b » Wed Jan 03, 2018 7:18 pm

I'm having this problem with sabnzbd. I upgraded, Radarr and Sonarr work fine. sabnzbd will not connect. My URL is https://user:password@domain.com/sabnzbd

My password has a !, # and $ in it. nzb360 immediately fails connecting to sabnzbd. Radarr and Sonarr, which are both on the same domain (and have the same URL pattern), and have the same password, work fine.

Any ideas? It used to work fine, an update broke it but I just switched to using the web interface.
ce29f93b
 
Posts: 3
Joined: Wed Jan 03, 2018 7:12 pm

Re: Unable to connect after updating to the newest version

Postby Chonner » Wed Jan 03, 2018 11:17 pm

Having the exact same problem as ce29f93b.

Nginx Reverse proxy, with basic auth run by Nginx infront of Sabnzbd, Sonarr and Radarr (located at https://domain.com/sabnzbd or https://domain.com/sonarr or /radarr etc) . Password has plenty of punctuation aswell as letters and numbers

NZB360 can connect to Sonarr and Radarr, but not Sabnzbd. Can open Sabnzbd in the mobile browser fine as well.

Was working fine before, now seems to be broken recently vbut can't pinpoint it to a specific NZB360 or Sabnzd update though.
Chonner
 
Posts: 1
Joined: Wed Jan 03, 2018 11:09 pm

Re: Unable to connect after updating to the newest version

Postby Kev » Wed Jan 03, 2018 11:22 pm

Didn't change any SABnzbd connection code recently, so I would suspect it was SABnzbd or your networking. Any firewall changes?
Developer of nzb360
User avatar
Kev
Site Admin
 
Posts: 1437
Joined: Mon Feb 24, 2014 2:29 am

Re: Unable to connect after updating to the newest version

Postby ce29f93b » Thu Jan 04, 2018 10:26 am

No firewall changes here at all, no changes other than nzb360/sab versions, and it seems like an nzb360 update broke it versus sab (I don't update sab often whereas nzb360 updates from Play Store automatically).

Is there any way to get some logs out of nzb360 to see where its failing? I don't get a negative API key event in sab, or any logs in sab from connection attempts. The failure happens _immediately_ on nzb360, even when I'm on a slow cell network and there's no way my latency is 1ms to my server :)
ce29f93b
 
Posts: 3
Joined: Wed Jan 03, 2018 7:12 pm

Re: Unable to connect after updating to the newest version

Postby kenelbow » Thu Jan 04, 2018 6:24 pm

Chonner wrote:Having the exact same problem as ce29f93b.

Nginx Reverse proxy, with basic auth run by Nginx infront of Sabnzbd, Sonarr and Radarr (located at https://domain.com/sabnzbd or https://domain.com/sonarr or /radarr etc) . Password has plenty of punctuation aswell as letters and numbers

NZB360 can connect to Sonarr and Radarr, but not Sabnzbd. Can open Sabnzbd in the mobile browser fine as well.

Was working fine before, now seems to be broken recently vbut can't pinpoint it to a specific NZB360 or Sabnzd update though.


I can confirm I am having the same issue with Sabnzbd. Sonarr and Radarr are working correctly. All behind and NGINX reverse proxy all using https://user:pass@remoteaddy.com/(sabnzbd/sonarr/radarr)
kenelbow
 
Posts: 1
Joined: Thu Jan 04, 2018 6:18 pm

Re: Unable to connect after updating to the newest version

Postby ce29f93b » Fri Jan 05, 2018 11:34 am

I can confirm its a bug with nzb360. Logcat gave me what I need. Right after touching the "test connection" button:

01-05 12:17:04.377 26977 27926 W HTTP : java.lang.IllegalArgumentException: Illegal character in fragment at index 29: https://xxxx:xxxx#xxxxx@xxx.xxx.xx/sabn ... ashboard=1

I left character 29 unblanked, which is a #. Changing the password to no longer use #'s fixes the bug.

However, I just learned something else with this bug. I use SABNZBD's built in user/password authentication scheme, which presents me with a web page to log in to, not a basic .htpasswd style auth form in the browser. It actually turns out that the URL string for username/password is completely ignored when using the API key for SAB (I thought the password was still required).

So I could remove my username and password and it still works fine, which is a TIL for SAB for me :) However, if I put in a # to the URL string, I definitely get the bug so there is a problem for people who don't use a password on SAB and instead use NGINX to provide first level authentication.
ce29f93b
 
Posts: 3
Joined: Wed Jan 03, 2018 7:12 pm

Previous

Return to Support



cron