Server keeps saying: Invalid service key "", expecting "..."

Can be put also in the version 6X

Changed status, 'because for 6.x version it's not fixed.

Also, changing these lines don't affect the bug and is still reproducible(in D6). I think JSON is empty.

Just commited on the 6.x branch. #0ac5049
@carnau after this commit i'm not able to reproduce this issue, but after reading up @ #1, can you confirm me that it's fixed?

Yes, I'm still having this issue. I'll try to trace it.

Also, I provide a patch because in the last version, host and port nodejs variables in nodejs_get_config() are wrong, and always is using default values.

Well, I see the problem here.

In nodejs.module we get the serviceKey value like this:

'serviceKey' => variable_get('nodejs_config_serviceKey', ''),

This variable isn't from this module, but nodejs_config. So, if you don't enable this extra module and also fill the admin form, it always return blank because the variable not exists.

Also, I found another bug in nodejs_config admin form. The first value says:

Specify the host name or IP address that the node.js server should listen on. Leave blank to listen for any host name. Otherwise, the server will only respond to names that match the IP address given (or resolved from the given name).

So, if you want to leave this field blank you can't, because the required option is TRUE. Should be FALSE.

One question about this. I'm getting this error on nodejs side :

Backend authentication url not found.

If I enter the url nodejs/message with my browser, it shows:

{ "error": "Invalid service key." }

I found that nodejs_message_handler() function is who returns this message:

  if (!isset($_POST['serviceKey']) || !nodejs_is_valid_service_key($_POST['serviceKey'])) {
    drupal_json(array('error' => 'Invalid service key.'));
    exit();
  }

So, the question is, ¿Where $_POST['serviceKey'] is initialized? I dumped it but returns NULL.

Are you using the 6.x-1.x-dev branch or the 6.x-1.0 ?
I confirm that to use the service key feature, you need to set it correctly in both the js config file and also in the Drupal backend settings form.
if you get this error from the server:

Backend authentication url not found.

It may come from a wrong config file, like your drupal hostname.

Yes, it was a bad configuration file, damn virtualhosts... It's working now.

Now I'm using the dev version, and I can't reproduce the 'Invalid service key' message on the nodejs side, so I assume it's working now.

I'm still working on find why I recive the "{ "error": "Invalid service key." }" if I enter directly from the browser to the 'nodejs/message' path.

Hello Carnauro

What steps did you take to resolve the Invalid Service Key issue? I am able to see the messages being pushed to the server in the logs, but am unable to see them inside the chatroom and I am wondering if it is because of this error.

I have maintained the same service key in the nodejs config file and in drupal backend settings.

Would appreciate a quick reply!

Thanks,
Sahithya

Hi beejeebus

I am getting the "Invalid Service Key" error and have been unable to resolve it. I have maintained the service key in settings.php as well.
My configurations are as below :

settings = {
scheme: 'http',
port: 5000,
host: '127.0.0.1',
resource: '/socket.io',
serviceKey: 'xyz',
backend: {
port: 80,
host: '127.0.0.1',
scheme: 'http',
basePath: '',
messagePath: '/nodejs/message/'
},
debug: false,
sslKeyPath: '',
sslCertPath: '',
sslCAPath: '',
baseAuthPath: '/nodejs/',
publishUrl: 'publish',
kickUserUrl: 'user/kick/:uid',
logoutUserUrl: 'user/logout/:authtoken',
addUserToChannelUrl: 'user/channel/add/:channel/:uid',
removeUserFromChannelUrl: 'user/channel/remove/:channel/:uid',
addChannelUrl: 'channel/add/:channel',
removeChannelUrl: 'channel/remove/:channel',
setUserPresenceListUrl: 'user/presence-list/:uid/:uidList',
addAuthTokenToChannelUrl: 'authtoken/channel/add/:channel/:uid',
removeAuthTokenFromChannelUrl: 'authtoken/channel/remove/:channel/:uid',
toggleDebugUrl: 'debug/toggle',
contentTokenUrl: 'content/token',
publishMessageToContentChannelUrl: 'content/token/message',
extensions: [],
clientsCanWriteToChannels: false,
clientsCanWriteToClients: false,
transports: ['websocket', 'flashsocket', 'htmlfile', 'xhr-polling', 'jsonp-polling'],
jsMinification: true,
jsEtag: true,
logLevel: 1
};

It would be great if you could let me know what exactly could be causing this issue. I am able to see that the messages are being pushed correctly through the logs, however, I am unable to view the messages inside the chatroom. Are the issues tied?

Would really appreciate a quick reply!

Thanks,
Sahithya

I needed to use quotes:

"serviceKey":"my service key",