i've set it to Header set X-Frame-Options "ALLOW-FROM http://keen.wtf/" and it works now 🙂
nope, only the first time it worked 😞
NodeBB crashes for me on all requests with the following error messages. It was working fine last night and I have changed nothing. Anyone experience anything similar?
TypeError: object is not a function
at Object.SocketMeta.updateHeader (/NodeBB/src/socket.io/meta.js:46:3)
at executeHandler (/NodeBB/src/socket.io/index.js:155:39)
at Socket.<anonymous> (/NodeBB/src/socket.io/index.js:162:6)
at Socket.EventEmitter.emit [as $emit] (events.js:95:17)
at SocketNamespace.handlePacket (/NodeBB/node_modules/socket.io/lib/namespace.js:335:22)
at Manager.onClientMessage (/NodeBB/node_modules/socket.io-wildcard/index.js:11:42)
at WebSocket.Transport.onMessage (/NodeBB/node_modules/socket.io/lib/transport.js:387:20)
at Parser.<anonymous> (/NodeBB/node_modules/socket.io/lib/transports/websocket/hybi-16.js:39:10)
at Parser.EventEmitter.emit (events.js:95:17)
at finish (/NodeBB/node_modules/socket.io/lib/transports/websocket/hybi-16.js:288:16)
Looks like this may be a browser cache issue... I'm curious to see if your cache buster is working. Can you view the source of your NodeBB and paste me some of the
<script> tags? They should all have a
?v= at the end of the URL.
For an immediate workaround, have everybody clear their browser cache. Obviously this is not an ideal solution, so there's an underlying issue here... if client-side scripts are updated, the cache buster should change, and the browser should not be requesting cached copies (as the URL would have changed)...
Clearing the cache solved the problem immediately.