• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be 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.

Question Component attaching IP to configuration files

dmetallidis

New Pleskian
Plesk is deployed in a VM inside an AWS topology. This VM uses to IPs, one private and one public, thus when I made the according to changes to the configuration files in order for the Plesk to be functional webmail is not reachable. The cause of that is the file located in /etc/nginx/plesk.conf.d/webmails/schoox.com_webmail.conf.
IP in the file had the public IP value but what i needed was the private IP to be in place, thus i change them with the private IP and everything worked fine.
My question goes to the part of which is the according component that attaches the IP to that file when someone gives the reconfigure-server option or in general when plesk re-builds its files.
Is there a way I can change the procedure so it will attach the private IP and not the public IP?
Plesk version: Onyx 17.8.11 and OS ubuntu 14.4
 
Back
Top