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]: Possibly not escaping special characters in MongoDB password correctly during backups #4978

Closed
real-nickallen opened this issue Jan 27, 2025 · 1 comment · Fixed by #5051

Comments

@real-nickallen
Copy link

real-nickallen commented Jan 27, 2025

Error Message and Logs

Hi there,

I noticed an issue when setting a custom password for a MongoDB connection in Coolify. Passwords containing special characters (e.g., (, ), >, or others) can cause errors during the S3 backup setup. I think this has to do with url encoding maybe?

I noticed this when I was setting up backups for one my databases. I had randomly generated a password that included a ')' and it kept failing with:

bash: line 2: syntax error near unexpected token ')'

I also tried with a couple other such as '>' and got similar errors which I believe is the same problem!

This is my first time submitting an issue, so I’m not sure if this is a bug or just something to keep in mind when creating MongoDB user passwords. Either way, I really appreciate Coolify and wanted to share this just in case it’s something worth noting.

Thanks!
Nick

Steps to Reproduce

  1. Create a new MongoDB instance
  2. Update the password to include a special character such as '(' or '>'
  3. Save and restart the deployment
  4. Try perform a database backup through the Coolify UI

Example Repository URL

No response

Coolify Version

v4.0.0-beta.389

Are you using Coolify Cloud?

No (self-hosted)

Operating System and Version (self-hosted)

Ubuntu 20.04.6 LTS

Additional Information

No response

@real-nickallen real-nickallen added 🐛 Bug Reported issues that need to be reproduced by the team. 🔍 Triage Issues that need assessment and prioritization. labels Jan 27, 2025
@andrasbacsai andrasbacsai added 🐞 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 Feb 3, 2025
@andrasbacsai
Copy link
Member

Thanks for reporting. This will be fixed in the upcoming version.

@andrasbacsai andrasbacsai linked a pull request Feb 3, 2025 that will close this issue
@github-actions github-actions bot removed 🐛 Bug Reported issues that need to be reproduced by the team. 🐞 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 Feb 4, 2025
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.

2 participants