Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Microservices TCP host never used #1967

luisalo7 opened this issue Apr 9, 2019 · 1 comment


Copy link

commented Apr 9, 2019

I'm submitting a...

[ ] Regression 
[ x] Bug report
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead post your question on Stack Overflow.

Current behavior

When I create a Microservice Server and pass the TCPOptions this Microservices not use the host from the TCPOptions and listen on all IP's

Expected behavior

If pass host to the TCPOptions to the Microservices Server use only the IP that I pass.

What is the motivation / use case for changing the behavior?

My server has many IP's for many solutions that I hosted


Nest version: 5.7.4 to 6.0.5

For Tooling issues:
- Node version: 10.15.3
- Platform:  Amazon Linux 2

Sorry for my bad English

This comment has been minimized.

Copy link

commented Apr 10, 2019

Fixed in 6.1.0

Thanks for reporting

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
2 participants
You can’t perform that action at this time.