• 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!
  • 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.

i cant access plesk from other netwok ?? What should i do ??

F

fahmim

Guest
Hello,

First of all, i already installed Plesk 9.2 for windows in windows 2003 iis 6.0. Everything's was good , but it's just i cant access plesk panel from other network (intranet/internet) and from localhost, everthing work just fine.

Is there any restriction access that i need to configure ?? What should i do ?

by the way, im just doing for my university assignment "How to setup a web hosting" only, not for commercial purpose..

Thanks,
Fahmi
 
Hello,

Are you getting the following message when attempt to access Parallels Plesk Panel (PP):

"Access for administrator from address xx.xx.xx.xx is restricted in accordance with IP Access restriction policy currently applied."

It means that PP IP access policy was configured in such a way that Plesk cannot be accessed from the current IP. To enable Plesk control panel access one needs to login to Plesk Control Panel locally and change IP access policy. It can be done the following way:

Plesk > Server > Personal information section > Access > Remove necessary IP address/subnet/network

If localhost is also blocked and it is impossible to login to Plesk even locally, the Plesk database records regarding access policy need to be corrected. To retrieve the current policy and restricted/allowed IPs the following commands can be used:

"%plesk_bin%\dbclient" --direct-sql --sql="select * from cp_access"
"%plesk_bin%\dbclient" --direct-sql --sql="select * from misc where param='access_policy'";

To clear the access policy settings remove all the records from the "cp_access" table and set policy to "allow":

"%plesk_bin%\dbclient" --direct-sql --sql="delete * from cp_access";
"%plesk_bin%\dbclient" --direct-sql --sql="update misc set val='allow' where param='access_policy'";

After that, access to PP should be available.

Please, see the following article for more information:

http://kb.odin.com/en/1024

Thank you
 
Please, make sure port 8443 is not filtered by server firewall or by the router on ISP.
Check from the outside:
> telnet Plesk server_ip 8443
 
Back
Top