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

IP Removal results in PLESK accessibility problem on internal network only.

GaryThomlinson

New Pleskian
I wonder if someone might be able to shed some light on this for me. Running PLESK 9.5.5 and Win Svr 2008 (Therefore cannot ask Parallels support as its an EOL combo).

PLESK is running a shared hosting server, around 22 IPs on it. A maintenance task was to remove any unused IPs from the panel. IP Addresses section, find any at '0' client usage and remove them. One server in particular presented the list of the remaining 21 IPs with nice red icons next to them, quite rightly frightening the person removing the IP from this server. Clicking RELOAD on the PLESK panel put the IPs to a green status.

All was apparently fine, websites still loading, email etc. Some time later we noted our monitoring software showed this server as DOWN. We also noted that PBAs showed this server as 'Unavailable'.

Why would removing an unused IP, a) make the whole list of IPs go red, and b) when 'reload'ing the IPs via the PLESK panel, would this then result in PBAs and other tools wanting to connect on specific ports, not work?

We've checked the adapter setups, firewalls, restarted services, etc all to no avail, and are a little stumped now... any thoughts?

The PLESK panel will load via an internet browser, connecting via the external network (office ADSL) on 8443, yet, a telnet from the PBAs server on our internal network, will not connect to 8443 on that one server (we can telnet to other shared servers on port 8443).

EDIT:::

Resolved this ourselves. In case anyone else encounters this, the problem stemmed from an IP address on the server lower than the servers own IP. Removal of this IP resolved the problem.
 
Last edited:
Back
Top