#1
I'd like to request the feature to set the use of HTTPS differently for when approaching my server locally versus remotely.

When I'm away, I use a reverse proxy (HTTPS through apache) and nzb360 handles this perfectly (I'm actually amazed at how easy it was to set this up!) Unfortunately, when I'm at home, I can't access my server through the reverse proxy but I have to use it's internal IP and thus without HTTPS. Setting a certificate in the webservice too would handle in errors by the reverse proxy as the certificate is an unsigned one.

Is it possible to add a feature that I can set nzb360 to connect to my local server without HTTPS but remotely to use HTTPS?

Thank you very much for keeping this app so well developed!
#3
I really want to overhaul the entire configuration setup for each service, but the code that deals with the connections are pretty complex at this point :(

My goal is just to have you type in something like this:

LOCAL: http://192.168.0.190:8080/sabnzbd
REMOTE: https://myddnsurl.com:8080/sabnzbd

Instead of separate port fields, SSL checkboxes, etc.

The amount of code that would have to change to support that is a lot. I really want to do it, but I also don't want to break the current connections everyone has. It would be a huge transition. It's something that I am looking to do, however.
#4
I think having separate fields is more user friendly. But I'm sure most people who use nzb360 are more advanced than the average joe so it should be fine. Maybe you can add a wizard to set them up ? Like in Solid Explorer when you add a new location. And it has a test at the end so you know right away if it's working.
#5
Hi,

also really expecting that!

I also use a reverse proxy and so far, I can only set my connection to use lan OR wan... never both...

By the way, you said your goal is to have something like that:
LOCAL: http://192.168.0.190:8080/sabnzbd
REMOTE: https://myddnsurl.com:8080/sabnzbd

But can you made it to include optionnal login/password also, and not the same port/url ?
For ex:
LOCAL: http://192.168.0.190:8080/sabnzbd
REMOTE: https://USER:PASSWORD@sabnzbd.myddnsurl.com:443/

Thank you!
#6
Seconded!
The refactoring complexity is understandable.
Though, could a simple extra check "Use HTTPS locally?" be easily implemented while the new setup is being worked on?
#9
QBccePBv0PqlkkP3TWum wrote:I'd like to request the feature to set the use of HTTPS differently for when approaching my server locally versus remotely.

When I'm away, I use a reverse proxy (HTTPS through apache) and nzb360 handles this perfectly (I'm actually amazed at how easy it was to set this up!) Unfortunately, when I'm at home, I can't access my server through the reverse proxy but I have to use it's internal IP and thus without HTTPS. Setting a certificate in the webservice too would handle in errors by the reverse proxy as the certificate is an unsigned one.

Is it possible to add a feature that I can set nzb360 to connect to my local server without HTTPS but remotely to use HTTPS?

Thank you very much for keeping this app so well developed!
Reverse proxy should work even if on your own network. Look for a feature called NAT loopback or reverse NAT. Most routers should support this.

It makes it easy as I just put in one address for each service for nzb360 and it works anywhere.
cron