Community

@mj
I had the same problem and this trick still worked for me! Thanks

I disabled websocket support in config.js

"socket.io": {
  "transports": ["polling"]
}

And the board is back again.
This is ok for me, since websockets never worked with the proxy setup...

Hi,
I tried to upgrade from an v1 weekly build to the 1.4.0. I had to upgrade nodejs to version 4.7.0 to run the upgrade script, but then it worked.
But when I try to startup the server, the following error message shows on the first hit:

20/12 13:32:33 [21369] - info: Enabling 'trust proxy'
20/12 13:32:33 [21369] - info: NodeBB is now listening on: 0.0.0.0:4567
20/12 13:33:06 [21369] - error: TypeError: Cannot read property 'prototype' of undefined
    at Server.onWebSocket (/srv/nodebb/node_modules/engine.io/lib/server.js:358:40)
    at /srv/nodebb/node_modules/engine.io/lib/server.js:343:12
    at completeHybiUpgrade2 (/srv/nodebb/node_modules/ws/lib/WebSocketServer.js:284:5)
    at completeHybiUpgrade1 (/srv/nodebb/node_modules/ws/lib/WebSocketServer.js:309:13)
    at WebSocketServer.handleHybiUpgrade (/srv/nodebb/node_modules/ws/lib/WebSocketServer.js:337:3)
    at WebSocketServer.handleUpgrade (/srv/nodebb/node_modules/ws/lib/WebSocketServer.js:173:26)
    at /srv/nodebb/node_modules/engine.io/lib/server.js:342:13
    at Server.verify (/srv/nodebb/node_modules/engine.io/lib/server.js:142:12)
    at Server.handleUpgrade (/srv/nodebb/node_modules/engine.io/lib/server.js:331:8)
    at Server.<anonymous> (/srv/nodebb/node_modules/engine.io/lib/server.js:451:14)
    at emitThree (events.js:97:13)
    at Server.emit (events.js:175:7)
    at onParserExecuteCommon (_http_server.js:409:14)
    at HTTPParser.onParserExecute (_http_server.js:377:5)
TypeError: Cannot read property 'prototype' of undefined
    at Server.onWebSocket (/srv/nodebb/node_modules/engine.io/lib/server.js:358:40)
    at /srv/nodebb/node_modules/engine.io/lib/server.js:343:12
    at completeHybiUpgrade2 (/srv/nodebb/node_modules/ws/lib/WebSocketServer.js:284:5)
    at completeHybiUpgrade1 (/srv/nodebb/node_modules/ws/lib/WebSocketServer.js:309:13)
    at WebSocketServer.handleHybiUpgrade (/srv/nodebb/node_modules/ws/lib/WebSocketServer.js:337:3)
    at WebSocketServer.handleUpgrade (/srv/nodebb/node_modules/ws/lib/WebSocketServer.js:173:26)
    at /srv/nodebb/node_modules/engine.io/lib/server.js:342:13
    at Server.verify (/srv/nodebb/node_modules/engine.io/lib/server.js:142:12)
    at Server.handleUpgrade (/srv/nodebb/node_modules/engine.io/lib/server.js:331:8)
    at Server.<anonymous> (/srv/nodebb/node_modules/engine.io/lib/server.js:451:14)
    at emitThree (events.js:97:13)
    at Server.emit (events.js:175:7)
    at onParserExecuteCommon (_http_server.js:409:14)
    at HTTPParser.onParserExecute (_http_server.js:377:5)

I already tried to delete the node_modules and reinstalled them with npm install --production but nothing changed.
What can I do?

@Danny-McWilliams
I have no clue why this happens. I guess we have to wait for a fix

@julian Thanks for the answer
I'm using apache 2.2.22 and it seems like there is a bug in that version wich causes the leading slash. I'm upgrading to 2.4 next week hoping this solves the issue...
An other option is the "<If ...>" directive, but thats only available in 2.4, too...

Hi,
I still have problem configurating apache...
With the new configuration (using the RewriteEngine) I get a 404 error instead of the 400.

Here a line from the access_log

[11/Mar/2016:13:25:03 +0100] "GET /ws://127.0.0.1:4567/socket.io/?EIO=3&transport=websocket&sid=Wo9q_vZG6QCSZ7-9AAFN HTTP/1.0" 404 4815 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.75 Safari/537.36"

Any ideas on this?
Thanks

@Danny-McWilliams
Hi,
I think I had the same problem yesterday. But only on mobile. In the browser console I found a 404 error, regarding the compose template.
So I made a copy of "composer.tpl" found in public/templates/ and renamed it "compose.tpl".
It works now, but I think, thats a strange workaround...

Hi,
I noticed that the category description get's too big, when the redactor plugin is used:

When the redactor composer is disabled and instead the markup composer is enabled, everything looks fine:

It seems that the <p> tag gets lost somewhere...