Hello, I am trying to setup nodebb with haproxy instead of nginx as frontend. Everything seam to be working however I am getting lots of 403 on /socket.io/ requests. frontend http-in mode http bind 0.0.0.0:80 redirect scheme https code 301 if !{ ssl_fc } frontend https-in bind 0.0.0.0:443 ssl crt /etc/letsencrypt/live/test/test.pem http-response set-header strict-transport-security "max-age=31536000; includeSubDomains" http-response set-header Content-Security-Policy "default-src 'self' wss: https: *.startech-rd.tk/*; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://code.jquery.com; style-src 'self' 'unsafe-inline' https:; img-src 'self' https://casper.ghost.org/ https://www.gravatar.com/ data:; font-src 'self' https:" http-response set-header X-XSS-Protection "1; mode=block" http-response set-header X-Content-Type-Options "nosniff" http-response set-header Referrer-Policy "no-referrer" reqadd X-Forwarded-Proto:\ https acl is_websocket hdr(Upgrade) -i WebSocket acl is_websocket path_sub -i /socket.io/ use_backend bk_ws if is_websocket acl acl_comments path_beg -i /comments use_backend comments if acl_comments backend comments mode http balance leastconn timeout connect 1s timeout server 600s timeout queue 600s option redispatch retries 3 acl is_woff capture.req.uri -m sub .woff acl is_ttf capture.req.uri -m sub .ttf acl is_eot capture.req.uri -m sub .eot http-response set-header Cache-Control public if is_eot or is_woff or is_ttf http-response set-header Expires -1 if is_eot or is_woff or is_ttf http-response set-header Pragma cache if is_eot or is_woff or is_ttf cookie nodebb insert indirect nocache secure server node1 10.160.125.81:4567 cookie nodebb_node1 check inter 1000 fastinter 500 rise 2 fall 1 server node2 10.160.125.82:4567 cookie nodebb_node2 check inter 1000 fastinter 500 rise 2 fall 1 backend bk_ws option redispatch balance roundrobin option forwardfor option httpclose server node1 10.160.125.81:4567 maxconn 30000 weight 10 cookie ws_node1 check server node2 10.160.125.82:4567 maxconn 30000 weight 10 cookie ws_node2 check``` I have tried to connect directly without haproxy and the websockets are connecting correctly. However I've seen that using the haproxy the websocket protocol changed from wss to https. Any suggestions on how to fix this?

@Peter-Zoltan-Keresztes Not to my knowledge... we're still using it here on this site Perhaps ping @psychobunny ...?

Hello @Peter-Zoltan-Keresztes, I apologize that your post may have been overlooked. If you cannot access your phone or your 2fa backup codes, you should still be able to disassociate your account by writing directly to the database, as the plugin does here, by deleting the keys and backup codes for your uid. The Mongo commands should be: db.objects.update({_key: "2factor:uid:key"},{$unset: {"youruidhere": 1}} db.objects.remove({_key: "2factor:uid:youruidhere:backupCodes"}} replacing youruidhere with your uid

@pichalite Got it thank you.

@julian I confirm. It is fixed.

Latest version of NodeBB doesn't require this dep anymore, so maybe try pulling the latest master?

I can live for now with what we have. I am waiting for 0.7 to be released then I hope my issue will be fixed. I just thought you guys want to know about the issue I am experiencing.

That's an unrelated bug check here https://github.com/NodeBB/NodeBB/issues/2711

Pinging @psychobunny for support reasons.

As I mentioned earlier it was working just fine until 0.5.5

Nope is not working, I am getting the same error. without the domain for session cookie set.

Yes, nice catch @a_5mith. Incompatible themes requiring outdated versions of the vanilla theme often cause npm to abort. It's not a pretty sight

@Peter-Zoltan-Keresztes said: I have tried with both copying the old files and also install it as new Nodebb and at I run the npm install script then ./nodebb setup and made sure that I have selected the old db. Both are giving the same invalid csrf token error. Noone has any idea how to fix the issues on hand?

@psychobunny I'm using current version of nodebb, but i can't find public folder in it, any way i find direct template folder but html i'm giving not working. Please tell me how i have to add header above the nodebb menubar Thanks

I have upgraded to mongodb 2.6.4, I have run the following command to upgrade the mongodb to v5 mongos --configdb 127.0.0.1:27017 --upgrade with no error, I have clicked on reindex the database. when I search I get the following stuff in the cli MongoError: Unable to execute query: error processing query: ns=0.search limit=50 skip=0 Tree: $and key == "topic" TEXT : query=cool, language=, tag=NULL Sort: {} Proj: {} planner returned error: need exactly one text index for $text query at Object.toError (/nodebb/node_modules/mongodb/lib/mongodb/utils.js:114:11) at /nodebb/node_modules/mongodb/lib/mongodb/cursor.js:700:54 at Cursor.close (/nodebb/node_modules/mongodb/lib/mongodb/cursor.js:983:5) at commandHandler (/nodebb/node_modules/mongodb/lib/mongodb/cursor.js:700:21) at /nodebb/node_modules/mongodb/lib/mongodb/db.js:1847:9 at Server.Base._callHandler (/nodebb/node_modules/mongodb/lib/mongodb/connection/base.js:445:41) at /nodebb/node_modules/mongodb/lib/mongodb/connection/server.js:478:18 at MongoReply.parseBody (/nodebb/node_modules/mongodb/lib/mongodb/responses/mongo_reply.js:68:5) at null.<anonymous> (/nodebb/node_modules/mongodb/lib/mongodb/connection/server.js:436:20) at EventEmitter.emit (events.js:95:17)

apparently this error is caused by the cookies which are saved in the browser. Ones I cleared the cache and cookies I was able to login with no issue.

@Ted nope, not working but the error from cli has disappeared

@julian I am running the nodebb on development mode. when I upload a picture, No matter what type I get the following error after the upload count get's to 100% even if I have stopped all other apps. [image: T1i24H7.png] and in the console just this: warn: Route requested but not found: /api/post/upload

@julian said: Need more info. I can't work with "not working", sorry Look at the code above, this is what I get on the browser. I have run the ./nodebb dev but I don't get any information in the console, so kind of this is all I have.

@Paweł-Nowak You should register for an account on Transifex. Then you can contribute translations to NodeBB for everybody to enjoy It does not require coding whatsoever