Technical Support

@julian I guess so, I Manually edit the configuration file finally, and it works. Thanks a million！

My goal is to connect NodeBB to MongoDB only with unix socket. Found here that is possible to use unix socket with mongodb, also this link was helpfull but can't figure out how to solve this error. Why "error: failed to connect to server [%2Ftmp%2Fmongodb-1033.sock:27017]" there is default 27017 port, whats missing in this config? { "url": "http://www.example.net/forum", "secret": "secret", "database": "mongo", "port": [ "/home/forum/webapps/nodebb.sock" ], "mongo": { "uri": "mongodb://user:pass@%2Ftmp%2Fmongodb-1033.sock/db_name", } } 2019-05-24T20:31:32.180Z [/home/forum/webapps//nodebb.sock/10753] - error: uncaughtException: failed to connect to server [%2Ftmp%2Fmongodb-1033.sock:27017] on first connect [Error: getaddrinfo ENOTFOUND %2Ftmp%2Fmongodb-1033.sock at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:60:26) { name: 'MongoError', message: 'getaddrinfo ENOTFOUND %2Ftmp%2Fmongodb-1033.sock' }] MongoError: failed to connect to server [%2Ftmp%2Fmongodb-1033.sock:27017] on first connect [Error: getaddrinfo ENOTFOUND %2Ftmp%2Fmongodb-1033.sock at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:60:26) { name: 'MongoError', message: 'getaddrinfo ENOTFOUND %2Ftmp%2Fmongodb-1033.sock' }] at Pool.<anonymous> (/home/forum/webapps/nodebb/node_modules/mongodb-core/lib/topologies/server.js:336:35) at Pool.emit (events.js:196:13) at Connection.<anonymous> (/home/forum/webapps/nodebb/node_modules/mongodb-core/lib/connection/pool.js:280:12) at Object.onceWrapper (events.js:284:20) at Connection.emit (events.js:196:13) at Socket.<anonymous> (/home/forum/webapps/nodebb/node_modules/mongodb-core/lib/connection/connection.js:189:49) at Object.onceWrapper (events.js:284:20) at Socket.emit (events.js:196:13) at emitErrorNT (internal/streams/destroy.js:91:8) at emitErrorAndCloseNT (internal/streams/destroy.js:59:3) {"error":{"name":"MongoError","message":"failed to connect to server [%2Ftmp%2Fmongodb-1033.sock:27017] on first connect [Error: getaddrinfo ENOTFOUND %2Ftmp%2Fmongodb-1033.sock\n at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:60:26) {\n name: 'MongoError',\n message: 'getaddrinfo ENOTFOUND %2Ftmp%2Fmongodb-1033.sock'\n}]"},"stack":"MongoError: failed to connect to server [%2Ftmp%2Fmongodb-1033.sock:27017] on first connect [Error: getaddrinfo ENOTFOUND %2Ftmp%2Fmongodb-1033.sock\n at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:60:26) {\n name: 'MongoError',\n message: 'getaddrinfo ENOTFOUND %2Ftmp%2Fmongodb-1033.sock'\n}]\n at Pool.<anonymous> (/home/forum/webapps/nodebb/node_modules/mongodb-core/lib/topologies/server.js:336:35)\n at Pool.emit (events.js:196:13)\n at Connection.<anonymous> (/home/forum/webapps/nodebb/node_modules/mongodb-core/lib/connection/pool.js:280:12)\n at Object.onceWrapper (events.js:284:20)\n at Connection.emit (events.js:196:13)\n at Socket.<anonymous> (/home/forum/webapps/nodebb/node_modules/mongodb-core/lib/connection/connection.js:189:49)\n at Object.onceWrapper (events.js:284:20)\n at Socket.emit (events.js:196:13)\n at emitErrorNT (internal/streams/destroy.js:91:8)\n at emitErrorAndCloseNT (internal/streams/destroy.js:59:3)","exception":true,"date":"Fri May 24 2019 22:31:32 GMT+0200 (Central European Summer Time)","process":{"pid":10753,"uid":1003,"gid":100,"cwd":"/home/forum/webapps/nodebb","execPath":"/usr/local/bin/node","version":"v12.1.0","argv":["/usr/local/bin/node","/home/forum/webapps/nodebb/app.js"],"memoryUsage":{"rss":145326080,"heapTotal":101863424,"heapUsed":67882440,"external":37486265}},"os":{"loadavg":[0.060546875,0.142578125,0.166015625],"uptime":33249},"trace":[{"column":26,"file":"dns.js","function":"GetAddrInfoReqWrap.onlookup [as oncomplete]","line":60,"method":"onlookup [as oncomplete]","native":false},{"column":35,"file":"/home/forum/webapps/nodebb/node_modules/mongodb-core/lib/topologies/server.js","function":null,"line":336,"method":null,"native":false},{"column":13,"file":"events.js","function":"Pool.emit","line":196,"method":"emit","native":false},{"column":12,"file":"/home/forum/webapps/nodebb/node_modules/mongodb-core/lib/connection/pool.js","function":null,"line":280,"method":null,"native":false},{"column":20,"file":"events.js","function":"Object.onceWrapper","line":284,"method":"onceWrapper","native":false},{"column":13,"file":"events.js","function":"Connection.emit","line":196,"method":"emit","native":false},{"column":49,"file":"/home/forum/webapps/nodebb/node_modules/mongodb-core/lib/connection/connection.js","function":null,"line":189,"method":null,"native":false},{"column":20,"file":"events.js","function":"Object.onceWrapper","line":284,"method":"onceWrapper","native":false},{"column":13,"file":"events.js","function":"Socket.emit","line":196,"method":"emit","native":false},{"column":8,"file":"internal/streams/destroy.js","function":"emitErrorNT","line":91,"method":null,"native":false},{"column":3,"file":"internal/streams/destroy.js","function":"emitErrorAndCloseNT","line":59,"method":null,"native":false}]} 2019-05-24T20:31:32.180Z [/home/forum/webapps//nodebb.sock/10753] - error: failed to connect to server [%2Ftmp%2Fmongodb-1033.sock:27017] on first connect [Error: getaddrinfo ENOTFOUND %2Ftmp%2Fmongodb-1033.sock at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:60:26) { name: 'MongoError', message: 'getaddrinfo ENOTFOUND %2Ftmp%2Fmongodb-1033.sock' }] {"name":"MongoError"} 2019-05-24T20:31:32.181Z [/home/forum/webapps//nodebb.sock/10753] - info: [app] Shutdown (SIGTERM/SIGINT) Initialised. 2019-05-24T20:31:32.182Z [/home/forum/webapps//nodebb.sock/10753] - error: Server is not running.

The error suggests a 404 page may be getting served, try going to that url, what do you see? Perhaps you need to rebuild NodeBB?

It's possible, but not easy. There are a few options: create a theme for NodeBB, render NodeBB in an iframe and embed that in your page render NodeBB templates in an angular component and embed that in your page interface directly with the NodeBB rest API, creating a frontend in angular

@scottalanmiller said in MongoDB crashes sometimes: I know it has been a while, but what did your investigation find? Ha! I was just about to necro bump this thread to query same

@julian Cool thanks, yea poor ns-embed is not happy in 1.12.2 - I and others already flagged in that thread, still, A Great plugin! Ok SMTP/EMAIL is fixed! Some deeper DNS/MX work seems to have made the difference and using "encrypted" setting - initially I was using StartTLS as per email provider SMTP guide, which specified TLS - tested it again and StartTLS broke it. Encrypted works.

Hope your backups are good I'd recommend setting up static file serving on nginx, but I bet you do that already.

It's a little difficult to explain, but at a high level, we're a single page app, which means when you click on an anchor, we request the JSON for the new page, render the html on the user browser, empty everything in #content, and inject it into #content. The overlay is a transition that makes this process a little smoother. We use a templating engine called Benchpress to render templates on both server and client-side.

Got me scared there for a sec

Probably executed it by mistake... @Kinchtwck how are you starting NodeBB?

@Rasmus said in Restrict guest access to forum: signing up as guest I think this might be the crux of your problem. You can't sign up as a guest, you're a guest when you don't log in.

Not a NodeBB specific test, but a NodeJS one, and just an isolated example, but suggests that Node at least is far faster on Linux. Now keep in mind this is old so pretty much worthless as a test. I'm interested to do some real testing, though. http://josephbill.com/node-js-performance-benchmark-on-windows-vs-linux/

@baris said in Badges not showing: You can turn on multiple badges at /admin/settings/group oh nice, didn't even think about that as we've had badges for so long Just turned it on for us, too.

@baris, I can’t reproduce it with short post content — in this case versioning works fine.

@julian said in Cannot start nodebb with systemd: /opt/nodebb/logs/output.log Hi julian, sorry for my delay response. I changed the services as you suggested, essentially this was my first implementation. I removed the file output.log, then I rebooted the system and started the services, when I went in the logs folder the file output.log was empty. UPDATE: I used journalctl -fu nodebb.service to see the log of the service, and I discovered a nice thing: [image: xJaqGyY.jpg] Any idea? UPDATE 2 [FIXED] Okay, so after spending some times on this, I discovered what is the cause of the problem. Essentially, I have installed nodebb as root account (which is wrong, my bad), and the systemd service was configured to run nodebb as the user "sfarzoso", but that user was not the owner of nodebb folder, so when I started the service using systemd, a permission problem happen. For fix this, I chowned the "opt" folder for "sfarzoso", which is the folder that I need to install nodebb, then I cloned the repo of nodebb and launched the setup again. All works now. Thanks for the attention, king regards.

@PitaJ said in email notifications for post queue: Just so everyone knows, there's a search bar in the ACP, that searches the ACP. If you're looking for a setting that may be a good place to start. Oh, I've never seen that. It's in all that "Dead space" way up top that I scroll past before it even loads because there is so much wasted space. Good to know that that is there. Would be nice to see that area compressed a bit, so much empty space up there.

@PitaJ said in "csrf-invalid": @PatheticMustan please try removing the config.json socket.io option. It's dangerous. More information here: https://community.nodebb.org/topic/13388/faq-websockets-not-working-due-to-misconfigured-origins Thanks for the tip! I have since removed it, and it still works

Hello ! On this forum (and also mine...), there is no pagination-block visible when we are on /recent or /popular for example. Is there a simple way to make it working on my forum ? Thanks in advance.

@PitaJ said in Private Git for install plugins: @Joykiller there's no easy way to keep the links with npm, but yarn is better at not killing them. Ah ok, well ill put up with it. Till I write some bash that checks to make sure the links there or something and if not replaces it after some trigger. I'll look into it later.