bug: I just installed the site but I have this error there #101

New Issue

2026-02-16T12:51:27-05:00

yindo commented

2026-02-16 12:51:27 -05:00

Originally created by @MisterSuki on GitHub (May 2, 2025).

What happened?

Originally created by @MisterSuki on GitHub (May 2, 2025). ### What happened? ![Image](https://github.com/user-attachments/assets/5b8fa417-5e3f-418e-b13b-185a9f6286fc)

yindo added the bug label 2026-02-16 12:51:27 -05:00

yindo closed this issue

2026-02-16 12:51:27 -05:00

yindo commented

2026-02-16 12:51:27 -05:00

@DeclanChidlow commented on GitHub (May 2, 2025):

We'll need significantly more information to be able to take any action. Please share your logs, details about your server, versions, etc.

@DeclanChidlow commented on GitHub (May 2, 2025): We'll need significantly more information to be able to take any action. Please share your logs, details about your server, versions, etc.

yindo commented

2026-02-16 12:51:27 -05:00

@MisterSuki commented on GitHub (May 3, 2025):

I made the installations you had provided in your docs the database does not reread or this

@MisterSuki commented on GitHub (May 3, 2025): I made the installations you had provided in your docs the database does not reread or this

yindo commented

2026-02-16 12:51:27 -05:00

@JonLloydDev commented on GitHub (May 3, 2025):

I don't know if this is helpful, and I'm not familiar with Mongo DB myself, but in attempting to troubleshoot the same symptoms, I've had some success:

First, running docker logs revolt-database-1, I found a message that my Zimaboard's CPU wasn't compatible with MongoDB 5+! Checking the instructions, Mongo 4.4 is suggested for older CPUs. So I adjusted compose.yml to use docker.io/mongo:4.4 for the database service, and that helped (I also cleared out the data/db folder that Mongo uses - just in case), but the health check still failed.

Looking at the logs again, I didn't see anything wrong! Next, I was suspicious of the healthcheck. I was able to comment out all the healthcheck and dependency lines in compose.yml to keep the database running and drop into a shell (using docker exec -it revolt-database-1 bash) to figure out the test command...

First off, mongosh doesn't appear to exist in the Mongo 4.4 container. But the mongo command works! Stumbling my way through, simply changing the healthcheck test from:
echo 'db.runCommand("ping").ok' | mongosh localhost:27017/test --quiet
to
echo 'db.runCommand("ping").ok' | mongo localhost:27017/test --quiet
...appears to do the trick! It returns 1 if the database is ready.

From there, I had to undo some of my earlier test changes in compose.yml and Revolt.toml, but docker compose up -d works! (Now I just need to figure out invite-only mode.)

@JonLloydDev commented on GitHub (May 3, 2025): I don't know if this is helpful, and I'm not familiar with Mongo DB myself, but in attempting to troubleshoot the same symptoms, I've had some success: First, running `docker logs revolt-database-1`, I found a message that my Zimaboard's CPU wasn't compatible with MongoDB 5+! Checking the instructions, Mongo 4.4 *is* suggested for older CPUs. So I adjusted `compose.yml` to use `docker.io/mongo:4.4` for the database service, and that helped (I also cleared out the data/db folder that Mongo uses - just in case), but the health check still failed. Looking at the logs again, I didn't see anything wrong! Next, I was suspicious of the healthcheck. I was able to comment out all the healthcheck and dependency lines in `compose.yml` to keep the database running and drop into a shell (using `docker exec -it revolt-database-1 bash`) to figure out the test command... First off, `mongosh` doesn't appear to exist in the Mongo 4.4 container. But the `mongo` command works! Stumbling my way through, simply changing the healthcheck test from: `echo 'db.runCommand("ping").ok' | mongosh localhost:27017/test --quiet` to `echo 'db.runCommand("ping").ok' | mongo localhost:27017/test --quiet` ...appears to do the trick! It returns `1` if the database is ready. From there, I had to undo some of my earlier test changes in `compose.yml` and `Revolt.toml`, but `docker compose up -d` works! (Now I just need to figure out invite-only mode.)

yindo commented

2026-02-16 12:51:27 -05:00

@MisterSuki commented on GitHub (May 3, 2025):

If I take you access to my machine you want to help me?

@MisterSuki commented on GitHub (May 3, 2025): If I take you access to my machine you want to help me?

yindo commented

2026-02-16 12:51:27 -05:00

@JonLloydDev commented on GitHub (May 3, 2025):

Sorry, my time is limited and I'm still trying to figure out Revolt myself.

Hopefully something in there can help though! Or if you can post more details about your config and logs, someone might be able to spot the issue.

@JonLloydDev commented on GitHub (May 3, 2025): Sorry, my time is limited and I'm still trying to figure out Revolt myself. Hopefully something in there can help though! Or if you can post more details about your config and logs, someone might be able to spot the issue.

yindo commented

2026-02-16 12:51:27 -05:00