You are going to hit brick wall after brick wall using the stock HTTP IN node because the port it listens on can not be changed.
This thread talks about this here:
(Stop reading when it gets into the certificate stuff - or not).
So it all depends on what your end goal is here.
The TCP In node might be the better better tool as you can change it to listen to a port above 1024 and then open the groov firewall to match the port number and you will be up and running to some extent.