I'm currently developing a site with node.js integration in. After installing node in the way I'm used to I ran a couple of tests to ensure it was working correctly (dblog and broadcast to all users).

Although watchdog (and indeed all other nodejs modules) work as expected, whenver a message is broadcast to all users (either using the nodejs_notify broadcast form or with heartbeat module) I receive the following alert on all user windows.

Only local images are allowed.

This happens to every single user on each tab for every single broadcast message.

After a little debugging, I could find nothing in the watchdog log, nothing in the apache access log, nothing in syslog, nothing in nodejs debug log that matched the same words/(apparent) 404 error.

My config file is as follows:

settings = {
//  scheme: 'http',
  port: 8187,
  host: '',
//  resource: '/socket.io',
  serviceKey: 'servicekeyhere',
  backend: {
    port: 80,
    host: 'www.mysitehere.com',
    scheme: 'http',
    basePath: '',
    messagePath: '/nodejs/message'
  },
  debug: true,
};

Although I'm fairly sure it is not a config issue as all other nodejs functionality works.

As a measure of fullness I followed the README exactly and I receive the same result. I also receive the same result with 4 different versions of node (0.4.12/0.6.8/0.6.12/0.8.16).

I'm at a bit of a loss and would be interested to see if a) people have experienced this themselves and b) how can I fix this!

CommentFileSizeAuthor
nodejs_notify_alert.png101.79 KBadammalone

Comments

mducharme’s picture

Your settings file is a little sparse. Is there a reason you've commented out the schema and resource lines?

As a first test, I would use a more robust config file. A similar discussion for this issue is here:

http://drupal.org/node/1733404

Try using (and tweaking for your own environment) the settings files from that issue. Either #10 or mine: http://drupal.org/node/1733404#comment-6987712

You should also watch the command line output in your terminal running node for clues. Node is not known for being great at debugging since a stack trace is not available in non-blocking io, but I agree that it would be nice to get some better error logging.

If you still have issues, post up your updated nodejs.config.js details.

mducharme’s picture

Issue summary: View changes

fixed image