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]: MongoDB backups are failing due to connection issue #5428

Closed
isokosan opened this issue Mar 26, 2025 · 7 comments · Fixed by #5416
Closed

[Bug]: MongoDB backups are failing due to connection issue #5428

isokosan opened this issue Mar 26, 2025 · 7 comments · Fixed by #5416

Comments

@isokosan
Copy link

Error Message and Logs

Mongodb backups started failing since yesterday and I was wondering if anyone else is having isues? My database is healthy and reachable, yet the backup is failing.

2025-03-26T07:30:48.852+0000    Failed: can't create session: failed to connect to mongodb://root:YBABz2JykNt9CJLT00m2T6KsWnnQcfMvIAroTPgtpLRAnqLW2nOcjgZ8nse1vQUP@ec08w0o4sggookk04w4k0wkg:27017/?directConnection=true&tls=true: server selection error: server selection timeout, current topology: { Type: Single, Servers: [{ Addr: ec08w0o4sggookk04w4k0wkg:27017, Type: Unknown, Last error: EOF }, ] }

Have found a similar issue, eg that missing ?ssl=true causes this kind of issue, though we have tls=true.

Steps to Reproduce

  1. Create a mongo:7 daabase in coolify cloud
  2. Do not make it publicly available
  3. Create a scheduled backup
  4. Try backing up now

Note: I tried various backups for the same database, but do not have another coolify cloud instance to test this issues reproducability.

Example Repository URL

No response

Coolify Version

v4.0.0-beta.399

Are you using Coolify Cloud?

Yes (Coolify Cloud)

Operating System and Version (self-hosted)

No response

Additional Information

No response

@isokosan isokosan added 🐛 Bug Reported issues that need to be reproduced by the team. 🔍 Triage Issues that need assessment and prioritization. labels Mar 26, 2025
@isokosan
Copy link
Author

I noticed that the v4.0.0-beta.399 release yesterday introduced full database SSL support, I guess this might be related to this change?

@andrasbacsai
Copy link
Member

Found the issue and it will be fixed in the next version.

@andrasbacsai andrasbacsai added 🚧 Next Issues and PRs planned for the next release. 🐞 Confirmed Bug Verified issues that have been reproduced by the team. ✅ Done Issues that are fixed and a PR is ready to be merged. and removed 🔍 Triage Issues that need assessment and prioritization. labels Mar 26, 2025
@github-actions github-actions bot removed 🐛 Bug Reported issues that need to be reproduced by the team. 🚧 Next Issues and PRs planned for the next release. 🐞 Confirmed Bug Verified issues that have been reproduced by the team. ✅ Done Issues that are fixed and a PR is ready to be merged. labels Mar 27, 2025
@aelmiger
Copy link

The issues regarding “connection error” seems fixed, but now I get the following error during backup:

Failed: can't create session: error configuring the connector: error configuring client, can't load CA file: open /etc/mongo/certs/ca.pem: no such file or directory

@johannesspohr
Copy link

The issues regarding “connection error” seems fixed, but now I get the following error during backup:

Failed: can't create session: error configuring the connector: error configuring client, can't load CA file: open /etc/mongo/certs/ca.pem: no such file or directory

same here

@isokosan
Copy link
Author

The issues regarding “connection error” seems fixed, but now I get the following error during backup:

Failed: can't create session: error configuring the connector: error configuring client, can't load CA file: open /etc/mongo/certs/ca.pem: no such file or directory

+1

@rovnyart
Copy link

+1

@edersilva78
Copy link

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants