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
The listen() call never rejects and always listens on 0.0.0.0 #84
Comments
This fix breaks my use case where my FTP is deployed behind a TCP Router which reroutes client connection to it (like a load balancer). In my case, the hostname I provide while starting the server is the public IP of the TCP Router, which is sent back to the client when he wants to push files. {"message":"listen EADDRNOTAVAIL ", Would it be posible to configure 2 kind of hostnames ?
|
@sbstnbr Thank you for your report, I was worried there would be broken builds. I apologize for it. I think I have a solution:
What do you think? |
Works for me ! 👍 |
listen() never rejects
The callback to
(net | tls).server.listen
will not receive an error argument, but is instead attached as a callback to the "listening" event. When there is a binding errorlistening
will never be dispatched and the promise is dead and will never reject nor resolve.See https://nodejs.org/api/net.html#net_server_listen
listen() always listens to 0.0.0.0
No host is passed on to the
net.server.listen()
, as such the default0.0.0.0
is always bound.The text was updated successfully, but these errors were encountered: