bug: Unable to use external mongo database. #62

Closed
opened 2026-02-16 12:51:18 -05:00 by yindo · 3 comments
Owner

Originally created by @dillfrescott on GitHub (Jun 29, 2024).

What happened?

I have correctly set all the strings and its saying:

api-1      |  INFO  revolt_config > Starting revolt-delta@0.7.12
api-1      |  INFO  revolt_database::models::admin_migrations::ops::mongodb > Migrating the database.
api-1      | thread 'main' panicked at 'Failed to fetch database names.: Error { kind: ServerSelection { message: "Server selection timeout: No available servers. Topology: { Type: Unknown, Servers: [ { Address: database:27017, Type: Unknown, Error: could not resolve address `(\"database\", 27017)` }, ] }" }, labels: {}, wire_version: None, source: None }', crates/core/database/src/models/admin_migrations/ops/mongodb.rs:23:14
api-1      | note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
api-1      |  INFO  revolt_config > Starting revolt-delta@0.7.12
api-1      |  INFO  revolt_database::models::admin_migrations::ops::mongodb > Migrating the database.

Over and over with no fix

Originally created by @dillfrescott on GitHub (Jun 29, 2024). ### What happened? I have correctly set all the strings and its saying: ``` api-1 | INFO revolt_config > Starting revolt-delta@0.7.12 api-1 | INFO revolt_database::models::admin_migrations::ops::mongodb > Migrating the database. api-1 | thread 'main' panicked at 'Failed to fetch database names.: Error { kind: ServerSelection { message: "Server selection timeout: No available servers. Topology: { Type: Unknown, Servers: [ { Address: database:27017, Type: Unknown, Error: could not resolve address `(\"database\", 27017)` }, ] }" }, labels: {}, wire_version: None, source: None }', crates/core/database/src/models/admin_migrations/ops/mongodb.rs:23:14 api-1 | note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace api-1 | INFO revolt_config > Starting revolt-delta@0.7.12 api-1 | INFO revolt_database::models::admin_migrations::ops::mongodb > Migrating the database. ``` Over and over with no fix
yindo added the bug label 2026-02-16 12:51:18 -05:00
yindo closed this issue 2026-02-16 12:51:18 -05:00
Author
Owner

@dillfrescott commented on GitHub (Jun 29, 2024):

This has happened to me weeks apart with two separate clean installs of revolt

@dillfrescott commented on GitHub (Jun 29, 2024): This has happened to me weeks apart with two separate clean installs of revolt
Author
Owner

@jquiaios commented on GitHub (Jul 6, 2024):

@dillfrescott A wild guess would be that maybe you've changed your URLs and variables in the .env file and not in the Revolt.toml config file (The config strategy and now uses Revolt.toml instead - see the cryptic message here, last paragraph).

Here's how I mounted the Revolt.toml in the self-hosted environment, in which I modified my URLs the same way I had previously done in my .env file, and it fixed my issue.

@jquiaios commented on GitHub (Jul 6, 2024): @dillfrescott A wild guess would be that maybe you've changed your URLs and variables in the `.env` file and not in the `Revolt.toml` config file (The config strategy and now uses Revolt.toml instead - see the cryptic message [here](https://github.com/revoltchat/self-hosted?tab=readme-ov-file#errata-notice), last paragraph). [Here's how I mounted the Revolt.toml](https://github.com/revoltchat/self-hosted/issues/87) in the self-hosted environment, in which I modified my URLs the same way I had previously done in my `.env` file, and it fixed my issue.
Author
Owner

@insertish commented on GitHub (Oct 2, 2024):

README was updated to include new configuration instructions

@insertish commented on GitHub (Oct 2, 2024): README was updated to include new configuration instructions
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: stoatchat/self-hosted#62