Failed to parse authentication message

Also getting this issue:
Failed to parse authentication message: {}
I am not using chatroom module currently.

My current nodejs.config file looks like this:
backendSettings = {
'scheme': 'http',
'host': 'hostname',
'port': 9080,
'key': '',
'cert': '',
'resource': '/socket.io',
'publishUrl': '/nodejs/publish',
'serviceKey': '',
'backend': {
'port': 8080,
'host': 'hostname',
'authPath': '/nodejs/auth/'
},
'extensions': [],
'clientsCanWriteToChannels': false,
'clientsCanWriteToClients': false,
'clientsCanWriteToClients': false,
'transports': ['websocket', 'flashsocket', 'htmlfile', 'xhr-polling', 'jsonp-polling'],
'jsMinification': true,
'jsEtag': true,
'logLevel': 1
};

The file I had previously didn't seem to work anymore after the upgrade so I created a new one using the example.

Finally got to the bottom of it.
You will have to edit your nodejs.config.js file, as there are few undocumented changes. First the authPath inside backendSettings.backend is no longer used. You can delete that line and put this one (inside backendSettings.backend):
'messagePath': '/nodejs/message/'

Next, if your serviceKey is empty (ie. if you're on a development machine), you'll have to edit your nodejs.module file's line 427 and replace

if (isset($_POST['messageJson']) && $_POST['authKey']) {

with

if (isset($_POST['messageJson']) && isset($_POST['authKey'])) {

Yeah I'm having the same problem.

Running latest dev release from August 1st on Ubuntu with nginx.
After following Gray Fox's instructions, I'm getting the message:

Started http server.
   info  - socket.io started
   debug - client authorized
   info  - handshake authorized 7832807241390730251
   debug - client authorized
   info  - handshake authorized 516167741612417551
   debug - setting request GET /socket.io/1/flashsocket/7832807241390730251
   debug - set heartbeat interval for client 7832807241390730251
   debug - client authorized for
   debug - flashsocket writing 1::
   debug - flashsocket received data packet 5:::{"name":"authenticate","args":[{                                                                         "authToken":"588882b34361fc51cd3f24c297ae0c94"}]}
Backend authentication url not found.
Backend authentication url not found.

My nodejs.config.js:

backendSettings = {
  'scheme': 'http',
  'host': 'mydomain.com',
  'port': 9000,
  'key': '/path/to/key/file',
  'cert': '/path/to/cert/file',
  'resource': '/socket.io',
  'publishUrl': '/nodejs/publish',
  'serviceKey': 'myservicekey',
  'backend': {
    'port': 80,
    'host': 'mydomain.com',
    'authPath': '/nodejs/auth/',
	'messagePath': '/nodejs/message/'
  },
  'extensions': [],
  'clientsCanWriteToChannels': false,
  'clientsCanWriteToClients': false,
  'clientsCanWriteToClients': false,
  'transports': ['websocket', 'flashsocket', 'htmlfile', 'xhr-polling', 'jsonp-polling'],
  'jsMinification': true,
  'jsEtag': true,
  'logLevel': 3
};

And if anyone cares, my NPM list:

---¬ connect@0.5.10
 --- qs@0.3.0
---¬ express@1.0.7
 --- qs@0.3.0
--- policyfile@0.0.3
---¬ socket.io@0.7.7
  --- bison@1.1.1  extraneous
  --- redis@0.6.0
  ---¬ socket.io-client@0.7.4
    --- uglify-js@1.0.3

Ok, I updated to latest commit.

My backend settings:

backendSettings = {
  'scheme': 'http',
  'host': 'mydomain.com',
  'port': 9000,
  'key': '/path/to/key/file',
  'cert': '/path/to/cert/file',
  'resource': '/socket.io',
  'publishUrl': '/nodejs/publish',
  'serviceKey': 'myservicekey',
  'backend': {
    'port': 80,
    'host': 'mydomain.com',
    'messagePath': '/nodejs/message'
  },
  'extensions': [],
  'clientsCanWriteToChannels': false,
  'clientsCanWriteToClients': false,
  'clientsCanWriteToClients': false,
  'transports': ['websocket', 'flashsocket', 'htmlfile', 'xhr-polling', 'jsonp-polling'],
  'jsMinification': true,
  'jsEtag': true,
  'debug': true,
  'logLevel': 1
};

A new error pops up when trying to start server:

Started http server.
   info  - socket.io started
Authenticating client with key "588882b34361fc51cd3f24c297ae0c94"
Sending message to backend { authToken: '588882b34361fc51cd3f24c297ae0c94',
  messageType: 'authenticate',
  clientId: '1049677100181977363' } { port: 80,
  host: 'mydomain.com',
  headers:
   { 'Content-Length': 172,
     'Content-Type': 'application/x-www-form-urlencoded' },
  agent:
   { options: { host: 'mydomain.com', port: 80 },
     host: 'mydomain.com',
     port: 80,
     socketPath: undefined,
     queue: [],
     sockets: [],
     maxSockets: 5 },
  method: 'POST',
  path: '/nodejs/message' }
Backend authentication url not found, tried using these options:

/var/www/mydomain.com/sites/all/modules/nodejs/server.js:172
        console.log(options);
                    ^
ReferenceError: options is not defined
    at IncomingMessage.<anonymous> (/var/www/mydomain.com/sites/all/modules/nodejs/server.js:172:21)
    at IncomingMessage.emit (events.js:67:17)
    at HTTPParser.onBody (http.js:121:23)
    at Socket.ondata (http.js:1224:22)
    at Socket._onReadable (net_legacy.js:689:27)
    at IOWatcher.onReadable [as callback] (net_legacy.js:177:10)

Thanks! Nodejs running without hitch now.

Just installed the integration module with the notify module, and while it works, node is spitting out the same errors as the OPs:

Started http server.
   info  - socket.io started
Failed to parse authentication message: { stack: [Getter/Setter],
  arguments: [ 'ILLEGAL' ],
  type: 'unexpected_token',
  message: [Getter/Setter] }
Failed to parse authentication message: { stack: [Getter/Setter],
  arguments: [ 'ILLEGAL' ],
  type: 'unexpected_token',
  message: [Getter/Setter] }

I'm running node.js 4.10 and using the versions of connect and express as mentioned in the readme.

My nodejs.config.js is practically default, with 'your.nodejs.server.hostname' changed to 'localhost'.

What exactly do these messages mean?

It turns out my problem was due to the BOM not being stripped out of the JSON reply in authenticateClientCallback(). Evidently this if fixed as of node 0.5.4, but for 0.4.x users you may need to strip it out like so:

      var buffer = chunk.toString();      
      if (buffer.charCodeAt(0) === 0xFEFF) {
        buffer = buffer.slice(1);
      }

Help me Error nodejs beta6
Failed to parse authentication message: { stack: [Getter/Setter],
arguments: [ 'ILLEGAL' ],
type: 'unexpected_token',
message: [Getter/Setter] }
Failed message string:

404 Not Found

The requested URL /index.php was not found on this server.

Additionally, a 404 Not Found
error was encountered while trying to use an ErrorDocument to handle the request.

Thanks

What version of node are you using?

I using node version 0.4.10.

It's probably due to what I mentioned in #18.

The code has changed slightly, but look in authenticateClientCallback in server.js where it calls:

authData = JSON.parse(requestBody);

Right before that, try stripping out the byte order marker if it exists:

if (requestBody.charCodeAt(0) === 0xFEFF) {
  requestBody = requestBody.slice(1);
}

Thanks inolen.But after I add code
if (requestBody.charCodeAt(0) === 0xFEFF) {
requestBody = requestBody.slice(1);
}
there is this error.

Failed to parse authentication message: { stack: [Getter/Setter],
arguments: [],
type: 'unexpected_eos',
message: [Getter/Setter] }
this code Handle authentication call response.
/**
* Handle authentication call response.
*/
var authenticateClientCallback = function (response) {
var requestBody = '';
response.setEncoding('utf8');
response.on('data', function (chunk) {
var requestBody = chunk.toString();
if (requestBody.charCodeAt(0) === 0xFEFF) {
requestBody = requestBody.slice(1);
}
//requestBody += chunk;
});

response.on('end', function () {
if (response.statusCode == 404) {
if (backendSettings.debug) {
console.log('Backend authentication url not found, full response info:', response);
}
else {
console.log('Backend authentication url not found.');
}
// return;
}
var authData = false;

try {
authData = JSON.parse(requestBody);
}
catch (exception) {
console.log('Failed to parse authentication message:', exception);
if (backendSettings.debug) {
console.log('Failed message string: ' + requestBody);
}
// return;
}
console.log('authData = ' , authData);
if (!checkServiceKey(authData.serviceKey)) {
console.log('Invalid service key "', authData.serviceKey, '"');
return;
}
if (authData.nodejsValidAuthToken) {
if (backendSettings.debug) {
console.log('Valid login for uid "', authData.uid, '"');
}
setupClientConnection(authData.clientId, authData, authData.contentTokens);
//console.log('co chay 1 lan roi');
authenticatedClients[authData.authToken] = authData;
}
else {
console.log('Invalid login for uid "', authData.uid, '"');
delete authenticatedClients[authData.authToken];
}
});
}
thanks.

It's now throwing an error because you mutilated the code.

Revert your changes and do exactly what I said in #23 :)

This seems to be still present in the latest .dev version.

Here's my node console output:

Authenticating client with key "2d2b74986ea7318872c82b11ef99ba2d"
Sending message to backend { authToken: '2d2b74986ea7318872c82b11ef99ba2d',
  messageType: 'authenticate',
  clientId: '15230871291326689086' } { uri: 'http://localhost:8082/nodejs/message',
  body: 'messageJson=%7B%22authToken%22%3A%222d2b74986ea7318872c82b11ef99ba2d%22%2C%22messageType%22%3A%22authenticate%22%2C%22clientId%22%3A%2215230871291326689086%22%7D&serviceKey=foobar',
  headers: 
   { 'Content-Length': 179,
     'Content-Type': 'application/x-www-form-urlencoded' } }
Failed to parse authentication message: { stack: [Getter/Setter],
  arguments: [ 'ILLEGAL' ],
  type: 'unexpected_token',
  message: [Getter/Setter] }
Failed message string: undefined
getNodejsSessionIdsFromUid { uid: undefined,
  sessionIds: [ '993864384112155517', '15230871291326689086' ] }

Here's my config, generated by the included tool:

backendSettings = {
  "scheme":"http",
   "host":"localhost",
   "port":8080,
   "key":"\u002Fpath\u002Fto\u002Fkey\u002Ffile",
   "cert":"\u002Fpath\u002Fto\u002Fcert\u002Ffile",
   "resource":"\u002Fsocket.io",
   "publishUrl":"\u002Fnodejs\u002Fpublish",
   "serviceKey":"foobar",
   "backend":{
  "port":8082,
   "host":"localhost",
   "messagePath":"\u002Fnodejs\u002Fmessage"},
   "clientsCanWriteToChannels":false,
   "clientsCanWriteToClients":false,
   "extensions":"",
   "debug":true,
   "transports":[ "websocket",
   "flashsocket",
   "htmlfile",
   "xhr-polling",
   "jsonp-polling" ],
   "jsMinification":true,
   "jsEtag":true,
   "logLevel":1};

I'm using node -v
v0.4.11

I now believe that this is not a problem in the current .dev release. I had made a mistake in my configuration, putting wrong value for "host" for the Drupal site.

Perhaps there should be some targeted error reporting in the node console if it is calling out to a non-existent server?

Having a similar problem than the ones reported previously. Have tried everything I can think of right now, but no joy so far.

Authenticating client with key "d0139c6171652381382a5f78c795d659"
Sending message to backend { authToken: 'd0139c6171652381382a5f78c795d659',
  messageType: 'authenticate',
  clientId: '1461508548898200644' } { uri: 'http://drupal7.local:80/nodejs/message',
  body: 'messageJson=%7B%22authToken%22%3A%22d0139c6171652381382a5f78c795d659%22%2C%22messageType%22%3A%22authenticate%22%2C%22clientId%22%3A%221461508548898200644%22%7D&serviceKey=pass',
  headers: 
   { 'Content-Length': 176,
     'Content-Type': 'application/x-www-form-urlencoded' } }
Failed to parse authentication message: [SyntaxError: Unexpected token u]
Failed message string: undefined

Configuration file:

backendSettings = {
  "scheme":"http",
  "host":"127.0.0.1",
  "port":8080,
  "key":"/path/to/key/file",
  "cert":"/path/to/cert/file",
  "resource":"/socket.io",
  "publishUrl":"/nodejs/publish",
  "serviceKey":"pass",
  "backend":{
  "port":80,
  "host":"drupal7.local",
  "messagePath":"/nodejs/message"},
  "clientsCanWriteToChannels":false,
  "clientsCanWriteToClients":false,
  "extensions":"",
  "debug":true,
  "transports":["websocket",
  "flashsocket",
  "htmlfile",
  "xhr-polling",
  "jsonp-polling"],
  "jsMinification":true,
  "jsEtag":true,
  "logLevel":1};

Node -v:
v0.6.17

Any help would be really appreciated. Thanks!

Didn't find the actual problem, but redoing everything from scratch in a new site and a new nodejs server solved the issue, even though the configuration was exactly the same.

I change the status of the issue back to close(fixed)

Keeping the issue closed but if anybody else runs into this issue:

Make sure any modules you have that control user access using redirects don't run on the path nodejs/message.

@interactivejunky are you saying that modules like redirect or global_redirect should always exclude 'nodejs/message'?

No idea, sorry, post was from too long ago.