Using Appsmith with external Mongodb container Replica Set error | Appsmith | Page 1

tender star Dec 12, 2023, 1:25 PM

#

Hi Appsmith community.
For days i'm trying to configure appsmith to work with external mongodb, because the machine i'm trying to deploy has a celeron processor, and i readed here https://community.appsmith.com/solution/appsmith-synology-docker-keeps-restarting, that's appsmith internal mongodb doesn't works with this processor.
In the images i can give an ideia what i tried to work around.
depending the configuration i can see that appsmith is authenticating on mongodb but replica set verification still getting error, i tried to enable but i'm not managing to enable correctly.
Can someone help me? i'm using paid version of appsmith.

fringe sparrowBOT Dec 12, 2023, 1:27 PM

#

Hello! I'm CodeSmith, your Appsmith support bot, ready to assist you with your
MongoDB configuration issues. To address your MongoDB replica set configuration,
let's start with a step-by-step approach: 1. Make sure that your MongoDB
instance is running and accessible from the machine where Appsmith is installed.
2. Verify that you have created a replica set for your MongoDB instance. If you
haven't set up a replica set, this is a necessary step because Appsmith requires
a MongoDB replica set to function correctly. 3. Ensure that the MongoDB user
you've created for Appsmith has the necessary permissions and that the user
credentials are correctly configured in the Appsmith environment variables. 4.
If Appsmith is authenticating but the replica set verification is failing,
double-check the replica set name and configuration details. 5. Check the
MongoDB logs to see if there are any error messages that can help pinpoint the
issue. If you need further help, please provide more specific information about
your MongoDB configuration, such as the Appsmith environment variables you have
set for MongoDB, the commands you used to set up the replica set or any error
logs you've received. This will help pinpoint the exact problem you're facing.
If any of this information is sensitive, consider redacting it before sharing.
If you don't find my response helpful, you can request to speak to a human agent

tender star Dec 12, 2023, 1:29 PM

#

how to correctly configure replica set on docker compose mongodb instance??

fringe sparrowBOT Dec 12, 2023, 1:32 PM

#

Configuring a replica set with MongoDB running in Docker can be done by
following these general steps: 1. Define a service for MongoDB in your
docker-compose.yml file. 2. Set the command to start MongoDB with the
--replSet option, specifying your replica set name. 3. Start the MongoDB
service using Docker Compose. 4. Connect to your MongoDB instance using the
MongoDB shell. 5. Initiate the replica set using the rs.initiate() command in
the MongoDB shell. 6. Update your Appsmith configuration to use the MongoDB
instance, specifying the replica set name. Here is an example snippet to include
in your docker-compose.yml file: version: '3' services: mongo: image: mongo command: --replSet rs0 ports: - "27017:27017" volumes: - mongo-data:/data/db volumes: mongo-data: After starting MongoDB with Docker
Compose, connect to the MongoDB instance and initiate the replica set: docker exec -it mongo Once connected to the MongoDB shell, initiate the
replica set: rs.initiate() Update your Appsmith configuration to use
this MongoDB instance and specify the replica set name (rs0 in this case). For
your specific situation on the Appsmith platform, you may also need to configure
the APPSMITH_MONGODB_URI environment variable to include the replica set name
as a query parameter, like this: mongodb://username:password@host:port/database?replicaSet=rs0 Please keep in
mind to replace username, password, host, port, and database with your
actual MongoDB credentials and details. Remember, it's important that you
replace these placeholders with your actual MongoDB configuration. Also ensure
that the MongoDB container has a volume attached for data persistence. Try these
steps and let me know if you encounter any issues! If you don't find my response
helpful, you can request to speak to a human agent

tender star Dec 12, 2023, 1:43 PM

#

Replica set config is asking for security file, how to disable it?

fringe sparrowBOT Dec 12, 2023, 1:47 PM

#

If MongoDB is asking for a security key file as part of the replica set
configuration, it implies that the replica set is being configured with keyfile
authentication for inter-node communication. If this is not desired or necessary
for your environment, you can disable this security feature. To run a MongoDB
replica set without keyfile authentication, you simply avoid including the
--keyFile option when starting mongod. Here is how you modify your
docker-compose.yml file to not use a keyfile for the replica set: ```yaml
version: '3' services: mongo: image: mongo command: mongod --replSet rs0 ports:

"27017:27017" volumes: - mongo-data:/data/db volumes: mongo-data: Then, verify that the MongoDB configuration file (usually named `mongod.conf`) does not include any security settings related to keyfile authentication. The configuration should not have an entry similar to this:yaml security:
keyFile: /path/to/keyfile If such a configuration exists, you need to remove or comment it out. Once you have ensured that keyfile authentication is disabled, restart your MongoDB instance:bash docker-compose up -d After the instance is running, you can initiate your replica set without keyfile authentication by connecting to MongoDB and running `rs.initiate()`:bash
docker exec -it mongo rs.initiate() ``` Make sure to update the Appsmith
configuration accordingly, without including any keyfile reference. Please
ensure that your MongoDB instance is secure and only accessible from authorized
hosts, especially if you're disabling authentication features. External MongoDB
deployments should be secured appropriately to prevent unauthorized access. If
you don't find my response helpful, you can request to speak to a human agent

tender star Dec 13, 2023, 1:48 PM

#

which mongodb version appsmith latest version uses?

fringe sparrowBOT Dec 13, 2023, 1:53 PM

#

The latest version of Appsmith recommends using MongoDB v5.0.14. This version is
also used for Appsmith's cloud offering【41†source】. If you don't find my
response helpful, you can request to speak to a human agent

tender star Dec 13, 2023, 2:08 PM

#

i want know version of internal appsmith mongodb, i'm evaluating the alternative of changing the PC that will run appsmith...

fringe sparrowBOT Dec 13, 2023, 2:11 PM

#

The internal MongoDB version that Appsmith uses from v1.9.0 onwards is version 5
or higher【52†source】. If you're evaluating the option of changing the computer
that will run Appsmith, make sure it is compatible with MongoDB version 5 or
above. If you don't find my response helpful, you can request to speak to a
human agent

fringe sparrowBOT Dec 16, 2023, 1:26 PM

#

Hello, we are closing this ticket as we haven't heard back from you in a while.
If your issue has not yet been resolved, you can reply to this thread to have it
re-opened.

fringe sparrowBOT Jan 9, 2024, 9:27 PM

#

It appears you've uploaded multiple files, but there was no specific question or
context provided regarding how you need assistance with them. Could you please
let me know what exactly you need help with? Are you facing issues with
deploying Appsmith, building apps on the platform, or resolving errors?
Providing more information will allow me to assist you better. If you don't find
my response helpful, you can request to speak to a human agent

#Using Appsmith with external Mongodb container Replica Set error