cannot connect to TCP server on CloudFoundry (localhost node.js works fine)
Problem
I have trouble connecting to my TCP server example running on CloudFoundry. When running my app.js file on a local node.js installation, it works just fine. Specifically, when I run the CloudFoundry by using vmc push, the service starts and does not crash. Some IP connects to it, disconnects and as far as I can tell, the service keeps running.
I just cannot connect to it using using neither "telnet" nor "nc" (note both of these work fine when directed towards the localhost node.js server.
This fails:
> nc themagicsandbox2.cloudfoundry.com 8124
This works
> nc localhost 8124
hello from TCP server! (intended reply)
My code is submitted here and the Cloud Foundry stdout.log is submitted below it.
Code:
myTrace('loaded'); // myTrace prepends timestamp to text and sends to console.log
var tcpServer = require('net').createServer(function(sock) { //'connection' listener
sock.on('connect', function() {
myTrace('client ' + sock.remoteAddress + ':' + sock.remotePort +' connected');
sock.write('hello from TCP server!\r\n');
sock.pipe(sock);
});
sock.on('end', function() {
myTrace('client disconnected');
});
});
tcpServer.listen(8124, process.env.VCAP_APP_HOST || "localhost");
tcpServer.on('listening', function() {
myTrace('server is listening - bound!');
});
tcpServer.on('error', function(err) {
myTrace('server err: ' + err);
if (err.code == 'EADDRINUSE') {
myTrace('Address in use, retrying ...');
setTimeout(function() {
tcpServer.close(function (err) {
myTrace('server.close: ' + err);
});
tcpServer.listen(SLIDEIN_TCP_PORT, process.env.VCAP_APP_HOST || "localhost");
}, 1000);
}
});
tcpServer.on('close',
function() {
myTrace('server has closed');
});
stdout.log (CloudFoundry):
Getting file contents... OK
Fri Mar 15 2013 11:59:02 GMT+0000 (UTC) loaded
Fri Mar 15 2013 11:59:02 GMT+0000 (UTC) server is listening - bound!
Fri Mar 15 2013 11:59:03 GMT+0000 (UTC) client 172.30.50.10:31840 connected
Fri Mar 15 2013 11:59:03 GMT+0000 (UTC) client disconnected
stdout (localhost node.js):
Fri Mar 15 2013 12:57:39 GMT+0100 (CET) loaded
Fri Mar 15 2013 12:57:39 GMT+0100 (CET) server is listening - bound!
Fri Mar 15 2013 12:57:53 GMT+0100 (CET) client 127.0.0.1:52260 connected
Fri Mar 15 2013 12:57:59 GMT+0100 (CET) client disconnected
Fri Mar 15 2013 12:58:00 GMT+0100 (CET) client 127.0.0.1:52261 connected
Fri Mar 15 2013 12:58:01 GMT+0100 (CET) client disconnected
Solution
That's because requests are routed to your application using the host header, neither of which netcat or telnet send. When making the request with either of those you will probably get a 504 back from the router.
Discussion
View additional discussion.