D
_dk3880_
Guest
In short:
It appears to me that, although Plesk allows admins to manage several IPs on one server, the firewall module itself does NOT allow server-IP-based rules. Is that correct? Which workaround do you suggest?
Long version:
Plesk allows admins to manage several IPs per server and to assign them to certain domains.
Now I want to run IMAP,POP,FTP, and a couple of other, custom public services on the first IP, and make all HTTP(S) publically available on the other.
Due to the default configuration of many services that Plesk maintains by itself (e.g. Courier), they are all offered on ANY IP of the system.
I would prefer not to mess around too much in the configs of the Plesk-maintained packages, therefore I thought I should choose a firewall-based approach:
- set up rules to enable IMAP etc. and deny HTTP on the one IP
- set up rules to enable HTTP(S) and deny the rest on the second IP.
So far so good.
But is it actually possible to make such settings using the Plesk firewall module???
Thanks.
It appears to me that, although Plesk allows admins to manage several IPs on one server, the firewall module itself does NOT allow server-IP-based rules. Is that correct? Which workaround do you suggest?
Long version:
Plesk allows admins to manage several IPs per server and to assign them to certain domains.
Now I want to run IMAP,POP,FTP, and a couple of other, custom public services on the first IP, and make all HTTP(S) publically available on the other.
Due to the default configuration of many services that Plesk maintains by itself (e.g. Courier), they are all offered on ANY IP of the system.
I would prefer not to mess around too much in the configs of the Plesk-maintained packages, therefore I thought I should choose a firewall-based approach:
- set up rules to enable IMAP etc. and deny HTTP on the one IP
- set up rules to enable HTTP(S) and deny the rest on the second IP.
So far so good.
But is it actually possible to make such settings using the Plesk firewall module???
Thanks.