Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you may not be able to execute some actions.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

MongoDB Compass Community configuration

Néstor Llamas Llopis last edited by

Hello,

In order to connect to the MongoDB of my VPS by means of MongoDB Community Compass installed on my PC, I need to provide authentication: username, password and authentication database. Which credentials may I set here? The username admin and the authentication database admin, or the username nodebb and the authentication database nodebb? Also, what must I do with the connection configuration options "SRV Record", "Read Preference" and "SSL"? May I set something here?

Regards,
Néstor Llamas Llopis
Reply Quote 0
1 Reply Last reply

1
Posts

17
Views

Suggested Topics

N

Redis or MongoDB?
Technical Support • • nodeSide

34

0
Votes

34
Posts

8706
Views

S

@scottalanmiller my support forum has pretty low traffic, so it’s not really an issue Actually the version of postgresql I had to install on my server doesn’t seem to be compatible with my install of Plesk either. But it works well, and I don’t have to mess around learning how to support mongodb.
mongodb typeerror
Technical Support • • charles

3

0
Votes

3
Posts

844
Views

@frissdiegurke i went with latest version and got it working. thanks for your help!
mongodb always down
Technical Support • • xidui

25

0
Votes

25
Posts

6419
Views

@AOKP Thank you for your offer. After the change in this issue, my mongo db has not went down until now. It seems to be more stable.
How to divide my community into 2 parts?
Technical Support • • Kosiak

2

0
Votes

2
Posts

37
Views

The closest thing I can think of is essentially cloning your forum (copying the database around) and then disabling certain categories on the specific forums.
NodeBB, Docker-Compose, MongoDB, Nginx - Only showing Login/Register and NodeBB name
Technical Support • • MostHated

4

0
Votes

4
Posts

124
Views

Edit : I gave it a few minutes after restarting Nginx and it looks like using the files from Github was my fix, looks to be that everything is working now! After doing a git clone of the current repo and building with the Dockerfile as opposed to just using the currently available nodebb/docker on docker hub, it looks like those issues went away. It currently isn't displaying anything at all right now, but in the logs I see: nodebb | nodebb | Starting NodeBB nodebb | "./nodebb stop" to stop the NodeBB server nodebb | "./nodebb log" to view server output nodebb | "./nodebb help" for more commands nodebb | nodebb | NodeBB v1.12.0 Copyright (C) 2013-2014 NodeBB Inc. nodebb | This program comes with ABSOLUTELY NO WARRANTY. nodebb | This is free software, and you are welcome to redistribute it under certain conditions. nodebb | For the full license, please visit: http://www.gnu.org/copyleft/gpl.html nodebb | nodebb | Clustering enabled: Spinning up 1 process(es). nodebb | 2019-04-04T22:33:50.921Z [4567/22] - info: Initializing NodeBB v1.12.0 https://forum.mysite.dev nodebb | 2019-04-04T22:33:54.634Z [4567/22] - info: [socket.io] Restricting access to origin: https://forum.mysite.dev:* nodebb | Thu, 04 Apr 2019 22:33:54 GMT hsts deprecated The "includeSubdomains" parameter is deprecated. Use "includeSubDomains" (with a capital D) instead. at node_modules/helmet/index.js:33:28 nodebb | Thu, 04 Apr 2019 22:33:54 GMT hsts deprecated The "setIf" parameter is deprecated. Refer to the documentation to see how to set the header conditionally. at node_modules/helmet/index.js:33:28 nodebb | 2019-04-04T22:33:54.961Z [4567/22] - info: Routes added nodebb | 2019-04-04T22:33:54.969Z [4567/22] - info: NodeBB Ready nodebb | 2019-04-04T22:33:54.976Z [4567/22] - info: Enabling 'trust proxy' nodebb | 2019-04-04T22:33:54.986Z [4567/22] - info: NodeBB is now listening on: 0.0.0.0:4567