https://community.cloudera.com/t5/Support-Questions/Why-won-t-HandleHTTPRequest-bind-to-a-secure-SSL-port/m-p/204660#M166649 <P>I have HandleHTTPRequest running without encryption on port 80. This works fine.</P><P>I would like another HandleHTTPRequest running on 443, using my signed certificate. I have verified to the best of my ability that the certificate store is valid, and the SSLContextService is happy to start with it. Additionally, the NiFi interface is being served over HTTPS on port 8443 without issue.</P><P>When I try to start the processor, it "starts" with repeated errors every few seconds starting that it failed to start. Looking in the log, it says the port is in use. A NetStat shows the NiFi process as the one listening on 443.</P><P>Things checked/tried:</P><P>* port is not in use before starting NiFi processor</P><P>* ports other than 443 also fail</P><P>* disabling secure web interface doesn't have an impact</P><P>* fresh instance booted from 1.3.0 Docker image has no impact</P><P>* context service won't start if known invalid data is entered (it's able to read the certificate store when given correct password and starts without issue).</P><P>What would cause it to open a listener on a port and then immediately fail to bind the processor to that port? Is there anything I'm missing?</P> Sat, 10 Jun 2017 05:00:24 GMT jrittenh 2017-06-10T05:00:24Z