Network access denied to external node.js socket -

-

i have 2 servers running on amazon's ec2. 1 standard web server running lamp (this behind elastic load balancer), other node.js server express , socket.io installed. on node server have server.js file (this file automatically loaded on server start).

var app = require('express')(); var server = require('http').server(app); var io = require('socket.io')(server);  server.listen(8080);   io.on('connection', function (socket) {      socket.on('join', function() {         console.log('joined');     } }

on lamp server, clients connect external server by:

<script src="https://cdn.socket.io/socket.io-1.3.4.js"></script>  var socket = io.connect('http://url_here:8080'); socket.on('connect', function() {     socket.emit('join', room_id); });

the problem, though, console spits out err_network_access_denied continuously, suggesting access port blocked. however, inbound rules node server follows:

custom tcp rule -- tcp -- 8080 -- 0.0.0.0/0 (anywhere) http            -- tcp -- 80   -- ip https           -- tcp -- 443  -- ip

i have tried sorts more or less opening inbound ports, no avail. may worth nothing way people access client script (the lamp server) through load balancer - cannot directly access lamp server. load balancers inbound rules follows:

custom tcp rule -- tcp -- 8080 -- 0.0.0.0/0 (anywhere) http            -- tcp -- 80   -- 0.0.0.0/0 (anywhere) https           -- tcp -- 443  -- 0.0.0.0/0 (anywhere)

and lamp server's rules:

custom tcp rule -- tcp -- 8080 -- sg-elb_id http            -- tcp -- 80   -- sg-elb_id https           -- tcp -- 443  -- sg-elb_id ... other irrelevant rules (shh, mysql, ...)

has idea why i'd getting access denied error? node server isn't behind load balancer - it's in effect external process. of security groups not restricted in regards outbound rules.

turns out reason couldn't find globally installed express or socket.io modules. doing cd /var/www/html , sudo npm link socket.io sudo npm link express resolved issue.


Comments

Post a Comment

Popular posts from this blog

c++ - No viable overloaded operator for references a map -

-
i trying use map can make tag names reference number. when try , use it, in code error (6 in total every time reference map): src/main.cpp:25:45: error: no viable overloaded operator[] type 'std::map<std::string, std::string>' const char* idcs = node.child_value(tagmap[3]); this code: #include "pugi/pugixml.hpp" #include <iostream> #include <string> #include <map> int main() { pugi::xml_document doca, docb; std::map<std::string, pugi::xml_node> mapa, mapb; std::map<std::string, std::string> tagmap {{"1", "data"}, {"2", "entry"}, {"3", "id"}, {"4", "content"}}; if (!doca.load_file("a.xml") || !docb.load_file("b.xml")) { std::cout << "can't find input files"; return 1; } (auto& node: doca.child(tagmap[1]).children(tagmap[2])) { co
Read more

java - Custom OutputStreamAppender not run: LOGBACK: No context given for <MYAPPENDER> -

-
i wish write custom appender on basis of outputstreamappender . wrote following class package tests; import java.io.ioexception; import java.io.outputstream; import ch.qos.logback.core.outputstreamappender; public class myappender<e> extends outputstreamappender<e> { public myappender() { system.out.println("myappender created"); setoutputstream(new outputstream() { @override public void write(int b) throws ioexception { throw new unsupportedoperationexception(); } }); } } then wrote following runner: package tests; import org.slf4j.loggerfactory; import ch.qos.logback.classic.logger; public class runner { private static final logger log = (logger) loggerfactory.getlogger(runner.class); public static void main(string[] args) { //log.addappender(new myappender<iloggingevent>()); log.info("hello world"); } } finall
Read more

java - Cannot secure connection using TLS -

-
i'm trying establish secure socket connection between java client applet (built jdk 1.7.0_75-b13) , vc++ server application. as test vehicle, used vc++ client/server sample found in msdn forums, modified use schannel , able establish socket using cipher suite tls_rsa_with_aes_128_cbc_sha. works of tls 1.0/1.1/1.2. when try opening socket java applet same server application, connection rejected server reporting following: tls 1.0 acceptsecuritycontext failed: 0x80090327 tls 1.1 acceptsecuritycontext failed: 0x80090331 tls 1.2 acceptsecuritycontext failed: 0x80090331 this java code used create socket: debugprint("setting secure connection"); sslsocketfactory sslsocketfactory = (sslsocketfactory) sslsocketfactory.getdefault(); sslsocket sslsocket = (sslsocket) sslsocketfactory.createsocket("127.0.0.1", socketnumber); debugprint("starting handshake"); sslsocket.settcpnodelay(true); sslsocket.setsolinger(false, 0); sslsocket.s
Read more