Question IP Whitelist or Password

[thedome]

Hi,

Is it possible that we secure the sub-/domains via "protected directories" or via the IP?
So that you either communicate from a certain IP or have to enter a user/password?
(Without using custom .htaccess and .htpasswd!)

greetings

 

[IgorG]

You can try to use solution from this KB article How to allow access to a website directory from specific IP address in Plesk?

Or use Protected directory feature Restricting Access to Content

 

[thedome]

However, with the solutions mentioned, protection cannot be ruled out.

I would like to be able to access the site from the office (static IP) without having to enter a password and to use the directory protection from outside connections.

 

[ChristianL.]

It would be nice to have an option to allow specific IPs to bypass the basic auth.
This would be helpful not only for every, by basic auth, protected WordPress site because WordPress needs to connect to it self. In addition there are some external services that need to connect to the site and don't support password protected sites. Unfortunately using https://user:[email protected] doesn't work in our use cases, too.
Why not offering the option to add IP addresses in addition to adding users?

 

[Kaspar]

It would be nice to have an option to allow specific IPs to bypass the basic auth.
This would be helpful not only for every, by basic auth, protected WordPress site because WordPress needs to connect to it self. In addition there are some external services that need to connect to the site and don't support password protected sites. Unfortunately using https://user:[email protected] doesn't work in our use cases, too.
Why not offering the option to add IP addresses in addition to adding users?

You could configure your own password protected directory using the build in mechanisms of either apache or nginx. That would allow you whitelist any ip.

For example with .htaccess file:

AuthName "Restricted Area"
AuthType Basic
AuthUserFile /var/www/vhosts/example.com/.htpasswd
Require valid-user
Order deny,allow
Deny from all
Allow from 123.123.123.123
Satisfy any

Or with nginx (add to additional nginx directives of domain)

location ~ ^/.* {
    satisfy any;

    allow 123.123.123.123;

    auth_basic "Restricted Area";
    auth_basic_user_file "/var/www/vhosts/example.com/.htpasswd";
}

 

[ChristianL.]

Thanks @Kaspar this is a workaround that could do it's job.

But:

1. this requires access to the Web-Server-Settings
2. on nginx it does not match to `location /`. Instead a `location ~ ^/.*` is used to avoid duplicate locations, what could cause other problems (loosing settings of `location /`)
3. you'll have to create and manage the .htpasswd file manually, what isn't that smooth as using the Plesk UI.