The issue in this case is not the result of changing the port number, rather the result of changing from HTTP to HTTPS. An MPS server instance must be specifically configured in order to work using HTTPS. Specifically, to use HTTPS you much generate a certificate chain and private key for your server instance, and then place these PEM files into the appropriate directories as detailed in the doc link here:
If you are running multiple servers on the same machine, the same* certificate (self-signed or CA) can be used across multiple MPS instances *as the Fully Qualified Domain Name goes into the certificate (thus the identifier for that particular physical machine will be a part of the certificate).
If you are doing this on a larger scale with multiple machines and do not want to have to go through the trouble of setting up a certificate for each machine, or are looking to migrate existing HTTP servers to HTTPS then you could also choose to use a Load Balancer. This would mean that the only externally visible end-point would be that of the Load Balancer, and you could configure your MPS servers to just use HTTP. By then setting the Load Balancer's endpoint to HTTPS, you could still maintain the same secure layer between the client and the Load Balancer. This topology works best if all the instances are deploying the same CTF, but even if they do not, then a LB can still be configured and used mostly for authentication.
Best Answer