Password Protect WAN

[daniel_owen_uk]

Hmm, trying to think of a way to do this.

On my LAN I want users to not have to bother with a Web Password, makes browser scripts a little ugly and it's just a pain, not required.

WAN side however I want a password, is there any way you could detect the IP the request is coming from (maybe set Router IP in config) and prompt only if access is actually from the web?

[daniel_owen_uk]

Ahhh, moving to 3, my config file is in a fixed place (as far as I can see), the problem is I usually run two SAB applications.

One LAN on a port that can't be accessed from the outside world.

One WAN that can be, but has password protected web interface.

When I install my second SAB3 it doesn't matter, as I can actually have them running on seperate ports (they are sharing the same config file).

[switch]

Another way to do it would be to use nzbdstatus for adding posts from newzbin. You can specify your username and password in the options.

If you don't like logging in all the time, you can add your username and password to your bookmark:
http://localhost:8080/sabnzbd/?ma_usern ... d=password

[daniel_owen_uk]

Personally I would like to see the config file named as per the directory (ie I call mine C:\Program Files\Sabnzbd\SabWAN & C:\Program Files\Sabnzbd\SabLAN) you should change the config file to reflect the last directory.

Most users wouldn't spot the change, but anyone wanting to install the server more than once, would have the option to do so.  Fixing the configuration file location is a step backwards imo.

[switch]

Just place the ini file in the same folder as your sabnzbd.exe's if you want to run multiple instances of sab.

Or specify the ini location with "-f /path/to/config/sabnzbd.ini" at the end of a shortcut/at the command line.

[auskento]

If you secure it behind apache, then you can accomplish this.

I have my WAN version protected via https (as posted by another member on the sourceforge forums)

I also have a standard http version which is only accessible from my internal network.

[Dan]

If you secure it behind apache, then you can accomplish this.

I have my WAN version protected via https (as posted by another member on the sourceforge forums)

I also have a standard http version which is only accessible from my internal network.

Are you aware of any documentation for windows users that would give me an idea of how to set this up with apache and https support?

[freeshna]

Can you split a WAN connection to a router and directly to a pc? I want to allow connectivity for 3 other pc's (router) but I need a fourth computer (direct from cable modem) to get the full bandwidth I am paying for to achieve maximum download speeds.

<URLs removed>

[shypike]

No.

[daniel_owen_uk]

Old post I know....

Does this still work?

I am trying to use it on my ipad but even with the ?ma_username=blahblah&ma_password=blahblah at the end of my url it still prompts for a password.

Any help?

[shypike]

The ma_* stuff only works in API calls, not in the regular URL.
Doesn't Mobile Safari allow you to store username and password automatically?

[daniel_owen_uk]

For certain types of login yes, not for sabnzbd though, unless I am missing something

[shypike]

As long as Safari keeps running, it remembers the credentials.
It's not like you reboot your iPad all the time, is it?

[daniel_owen_uk]

You are right I don't, but I do close safari fairly frequently. My SBSettings app has a kill all BG apps button that I use.

My questions is more about the style of login;

If I login to this forum the password request is on a webpage, all of my idevices (when set to remember username/password) prompt if I want to remember my sabnzbd forum password, I say yes, and then whenever I want to login I just click login.

If I login to my sab account a different style of login request pops up and there is no choice to remember password.

This would be fairly irrelevant if I could put login details into a bookmark.

[shypike]

Since we upgraded the CherryPy web framework, last year,
we're struggling with the login method.
For the previous version there was an alternative login module.
So far I haven't found a work-around for the current browser login method.
The problem is that the popup login method isn't supported by the password
manager of all browsers. Safari is clearly in that category.