#11
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?)
#12
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.
#13
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.
#14
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.
#16
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 :)
#17
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/(sabnz ... rr/radarr)