IP access restriction management

[Peter Vermeulen]

l.s.,

(Plesk version 11.09)


Trying to restrict access to plesk control panel to one IP address (fake 66.67.68.69).

When I add the network 66.67.68.69/255.255.255.254 I recieve the following notification:

Error: The access restriction policy and the list of networks are currently configured the way you will not be able to log in with administrator's rights from your IP address '66.67.68.69'.

Now I would like this to be the ONLY ip address from wich i can log in.

Where do I go wrong?

Regards,
Peter

 

[KristianM]

Hi,

try the Subnetmask 255.255.255.255. that should work.

Regards,
Kristian

 

[Peter Vermeulen]

Hello Kristan,

Tried that Subnetmask but unfortunately it is giving me the same response.

Regards,
Peter


ps. I do have root access to the server, would this be usefull in the case that it goes wrong?
Is there a specific file where restrictions are stored?

 

[KristianM]

Hi Peter,

just to be sure, which of the two options did you choose?

- Allowed, excluding the networks in the list. - Denied from the networks that are not listed.

Regards,
Kristian

 

[Peter Vermeulen]

Hello Kristan,

Here follows a 'log' of my actions

1) Server [Panel] -> Restrict Administrative Access
2) Select "Denied from the networks that are not listed."
3) Add new network "66.67.68.69/255.255.255.255"

Error warning appears, I delete the network.

Now, it might be the "SET" option after step 2, but when i hit that before adding a network I am getting the same error warning.

I don't want to risk of locking myself out.

Regards,
Peter

 

[Peter Vermeulen]

Hello Kristan,

Issue has been resolved.

The process of adding a restriction consists of two steps.
1) adding a network
2) selecting 'denied from the networks that are not listed'

No matter the flow I followed, 1,2 or 2,1. The warning about not being able to login from my current address was always presented in between the steps.
That made me hesitate to finish the process.

Finally i just ignored the warning and finished the process resulting in a working IP access restriction policy.

Regards,
Peter