The code that is responsible for this behaviour is actually in spring-cloud-turbine-stream. It starts a netty container and sets server.port=-1 to switch off the servlet container if it is present (it might need to be present for Actuator endpoints for example). I don't think we will be fixing this until Spring Boot 2.0 (at which point the servlet container will not be needed), so please use eureka.instance.non-secure-port in the meantime (the sample has been updated).

same issue. awesome answer.
Save me a lot.

@dsyer can you please suggest which property to set if I'm using spring-cloud-consul-discovery. Have same issue here with consul.

Never mind. Setting spring.cloud.consul.discovery.port did the trick.

This module has entered maintenance mode. This means that the Spring Cloud team will no longer be adding new features to the module. We will fix blocker bugs and security issues, and we will also consider and review small pull requests from the community.