node.js iisnode https 500 HRESULT 0x6d subStatus 1013

Question

I'm currently working on a realtime chat with socket.io and node.js. On my development machine everything works fine. I can call my socket.io-server on port 888.

The same port is free and reachable on my production server.

I can't figure out why IIS raises an 500 error. Has anyone an idea?

Following error is thrown:

HRESULT: 0x6d
HTTP status: 500
HTTP subStatus: 1013
HTTP reason: Internal Server Error

Hi, would you mind sharing your web.config that allowed you to use socket.io on a production server? I cannot get it to work. — laptou, Jun 01 '17 at 23:13

score 3 · Accepted Answer · answered May 29 '15 at 06:45

3

My problem was that my IIS hosted site run on 443 https. On node.js I wanted also to use https with the same .pfx file. This doesn't seem to work.

Also there is no need to use https for node.js if the site is hosted in SSL environment. The connection runs over wss and is secured.

Instead of require('https') I came up with require('http').

answered May 29 '15 at 06:45

webprogrammer

792
15
26

Thank you! This helped me!! – pix1289 Jul 19 '16 at 12:19

node.js iisnode https 500 HRESULT 0x6d subStatus 1013

1 Answers1