Adding Service Nodes

Before you can start providing hosting services, you need to add at least one web hosting service node, as described in the following sections.

If you are deploying service nodes in the Microsoft Azure Cloud, you must configure network address translation before adding each node.

To configure the address translation:

Go to Infrastructure > IP Addresses > IP Translation tab > Add New IP Translation.
Specify the public and the private (internal) IP address of the node and click Submit.

Now you can add service nodes in the Azure Cloud. After you add them, the public IP addresses that you specified in the NAT rules will be used in A records, and for navigation between the Provider Panel, UX1, and Plesk.

If you want to enable users to see public IP addresses in Plesk control panel, configure the IP addresses manually in Plesk: Log in to Plesk as admin and go to Tools & Settings > IP addresses. Note that if there are websites provisioned on Plesk nodes, the manual configuration of IP addresses may result in errors. In such a case, please refer to this KB article and use the resolution method that starts with "Change existing address for the new one where 'new_public_ip' is the new public IP to add..."

Notes:

Be sure to add NAT rules for Plesk-based hosting service nodes before you add the nodes. Otherwise, you will need to update information about the nodes (in Services > WebHosting Plesk > Service Nodes tab > Refresh). Learn more about this and other limitations in Known Issues and Limitations.
Make sure that the public IP address of the service node is attached to the primary IP configuration in the Azure Portal.
If you change the public IP address of a node (as described in step 1), be sure to update the information about the node in Services > WebHosting Plesk > Service Nodes > Refresh.
If you are using external DNS servers to host the DNS zones of branded domains, you need to manually configure the external DNS servers after adding service nodes: point the addresses web<node ID>.<your brand>.<TLD> to the IP address of the UI node.