• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

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