• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

IP Access Restriction - suggestion

N

nforde

Guest
Most of us Plesk owners will probably have several different people who need full admin access to Plesk, so I think this would be a very nice feature!

For example, currently the following people need access to Plesk on my server -
1) Myself
2) My tech support who add new clients/domains
3) My sys admins who help out with problems
4) My hosting company who need to install new certificates
5) Subcontractor/Programmer 1 - India
6) Subcontractor/Programmer 2 - USA
7) Subcontractor/Programmer 3 - New Zealand
8) Subcontractor/Programmer 4 - Phillipines

So basically I have at least 8 different IP ranges and as I use different subcontractors I need to remove IP ranges regularly.

THE PROBLEM IS...

That it's difficult to keep track of the various IP ranges and I'm worried that there is always the possibility that an ex-subcontractor may still have access and trash the system.

MY SUGGESTION IS...

It would be great if you could type in a NAME for each IP range so you can easily see who owns what.

Basically the same as what is currently done in the SSL Certificates section where you can name each certificate.

So the columns would be -
IP Address, Subnet Mask, Name/Owner

WHAT DO OTHER PEOPLE THINK? I'd be very interested to hear back from the Plesk programmers about this suggestion.
 
Back
Top