in firebug the following url is not found:
http://testcommons.dev:8181/socket.io/socket.io.js

how can I determine if nodejs is actually running?

npm ls
├─┬ express@2.5.11
│ ├─┬ connect@1.9.2
│ │ └── formidable@1.0.11
│ ├── mime@1.2.4
│ ├── mkdirp@0.3.0
│ └── qs@0.4.2
├── request@2.9.203
└─┬ socket.io@0.9.11
├── policyfile@0.0.4
├── redis@0.7.3
└─┬ socket.io-client@0.9.11
├─┬ active-x-obfuscator@0.0.1
│ └── zeparser@0.0.5
├── uglify-js@1.2.5
├─┬ ws@0.4.23
│ ├── commander@0.6.1
│ ├── options@0.0.3
│ └── tinycolor@0.0.1
└── xmlhttprequest@1.4.2

here is my config file:

settings = {
scheme: 'http',
port: 8181,
host: 'devserver',
resource: '/socket.io',
serviceKey: 'YourServiceKey',
backend: {
port: 80,
host: 'testcommons.dev',
scheme: 'http',
basePath: '',
messagePath: '/nodejs/message'
},
debug: false,
sslKeyPath: '',
sslCertPath: '',
baseAuthPath: '/nodejs/',
publishUrl: 'publish',
extensions: [],
clientsCanWriteToChannels: false,
clientsCanWriteToClients: false,
transports: ['websocket', 'flashsocket', 'htmlfile', 'xhr-polling', 'jsonp-polling'],
jsMinification: true,
jsEtag: true,
logLevel: 1
};

Comments

adammalone’s picture

A good idea for you would be to use the nodejs configuration module to help write your config file.

For your hosts - you might be wanting addresses (so your browser can talk to socket.io)
ie
host: mywebsite.com (unless of course you have testcommons.dev in /etc/hosts in which case it is fine.)

To check if nodejs is running, when you type 'node server.js' on the command line do you get the following?
Started http server.
info - socket.io started

chidosoft’s picture

Issue summary: View changes

PLS I NEED HELP TO RESOLVE THIS. I CAN SEE THE PROBLEM. BUT I DONT KNOW WERE TO LOCATE IT AND CHANGE IT.

GET http://localhost:8080/socket.io/socket.io.js net::ERR_CONNECTION_REFUSED
domainname.com/:1 Mixed Content: The page at 'https://domainname.com/' was loaded over HTTPS, but requested an insecure script 'http://localhost:8080/socket.io/socket.io.js'. This content should also be served over HTTPS.

bbeellkk’s picture

The error means that you are trying to use not encrypted connection while the page is loaded over https.

You should either add SSL certificate to nodejs configuration and change scheme to https or use http://domainname.com/.

chidosoft’s picture

Pls can you explain further on how to add SSl Certificate to nodejs. i am not too much a guru. Thanks

socialnicheguru’s picture

For original question

make sure that the serviceKey key is defined
also if you have http auth enabled then you should also have httpAuth
Also update to the newest node, follow the instructions, and use the new nodejs.config.js template. The transports are different.

socialnicheguru’s picture

Status: Active » Closed (works as designed)