Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bug: Unable to use external mongo database. #88

Closed
dillfrescott opened this issue Jun 29, 2024 · 3 comments
Closed

bug: Unable to use external mongo database. #88

dillfrescott opened this issue Jun 29, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@dillfrescott
Copy link

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

@dillfrescott dillfrescott added the bug Something isn't working label Jun 29, 2024
@dillfrescott
Copy link
Author

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

@jquiaios
Copy link

jquiaios commented 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.

@insertish
Copy link
Member

README was updated to include new configuration instructions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Archived in project
Development

No branches or pull requests

3 participants