Enabling HTTPS on the Cluster Manager or the nodes follows the same principles. Several properties can be used to configure the communication options. In order to enable HTTPS with TLS data encryption over the wire, you need to set the TLS property.
You will also need to provide the paths to the private key and the certificate files:
When HTTPS is enabled on the cluster nodes, the standard HTTPS port 443 is then used as the default instead of port 80. As with the port 80, you will need to start grb_rs with elevated privileges. Otherwise, you will get a permission error. On Linux, you'd see an error message like the following:
fatal : Gurobi Remote Services terminated, listen tcp :443: bind: permission denied
As explained in the installation section, you can change the port using the PORT property. Note that you cannot mix nodes using HTTP and nodes using HTTPS in the same cluster. If you wish to use HTTPS, all of the nodes must be configured in the same way. HTTPS will be used for communication between the nodes.
If you enable HTTPS, you will need to use the prefix https:// to access the nodes of your cluster:
> grbcluster nodes ADDRESS STATUS TYPE LICENSE PROCESSING #Q #R JL IDLE %MEM %CPU https://server1:61000 ALIVE COMPUTE VALID ACCEPTING 0 0 2 46h59m 9.79 0.50 https://server2:61000 ALIVE COMPUTE VALID ACCEPTING 0 0 2 46h46m 8.75 0.00