• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Question Block access to site, limit only from few IP addresses

kojot

Regular Pleskian
Hello,

I have one website which I don't want to be public.
I wan't allow access only from few IP addresses.

I have bunch of another sites, so I can't just limit ports 80 and 443 from firewall.

Is there any option in plesk for that?
 
just use .htaccess to block all IPs except yours or use plesks password protect feature.

eg

order deny,allow
deny from all
allow from <your ip>
 
You can also do something different if you don't want to outright deny the visitors content.
This allows you to send the public to another site, while allowing your own IP addresses to view a site in development or such:

<IfModule mod_rewrite.c>
RewriteEngine On
###### Allow Private Visitors ##########################
RewriteCond %{REMOTE_ADDR} !123.456.789.0 [NC]
RewriteCond %{REMOTE_ADDR} !123.456.789.1 [NC]
###### If Not Authorized, Send People Away #######################
RewriteRule ^(.*)$ https://someotherdomain.com/$1 [L,R=301]
</IfModule>
 
Thx all


@G J Piper
That sounds interesting, but maybe not for this topic, but I will write here, because for me is in relation.

We have one old cakephp site, and at this moment we developing another site in .net to change it.
We will need that old php site. Not all, just site.com/admin part.
So at one moment, all other sites including homepage need to be redirected to that /admin page.
I'm wondering, if I use that rewrite rule, I would have problem with redirection loop?
 
Back
Top