If you are running Coldfusion 2016 Enterprise Instance Manager and have a Tomcat connector for the primary cfusion instance running TLS, you won't be able to start new instances.
As it turns out, this happens because the instance manager creating the new instance doesn't know how to handle a TLS connector port of 8443 and mostly clones it verbatim.
When trying to manually start the new instance, you will see something like this :
Starting ColdFusion 2016 server ...
The ColdFusion 2016 server is starting up and will be available shortly.
Some other server/application is using the port 8443
Change the server connector port in the file /opt/coldfusion2016/cfusion1/runtime/conf/server.xml and start the server.
Ex: <Connector port="8502"
The solution is to modify the Instance's TLS port to an available one :
<Connector scheme="https" keyAlias="test" useServerCipherSuiteOrder="true" secure="true" protocol="org.apache.coyote.http11.Http11Nio2Protocol" SSLEnabled="true" port="8601" ciphers="TLS_RSA_WITH_AES_128_CBC_SHA256,TLS_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_25 6_CBC_SHA256,TLS_RSA_WITH_AES_256_CBC_SHA,SSL_RSA_WITH_RC4_128_SHA" keystoreFile="/etc/ssl/certs/keystore.jks" sslEnabledProtocols="TLSv1,TLSv1.1,TLSv1.2" keystorePass="somepass" maxThreads="150" clientAuth="false"/>