DOCSP-34709: connection troubleshooting shared #105
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 8 commits
December 6, 2023 12:22
…ction-troubleshooting-shared
ccho-mongodb
commented
Jan 18, 2024
|
|
||
| An invalid connection string is the most common cause of authentication | ||
| issues when attempting to connect to MongoDB. | ||
| .. replacement:: scram-failure-error |
Contributor
Author
There was a problem hiding this comment.
Cannot address this Vale issue, rule is set to change soon.
ccho-mongodb
commented
Jan 18, 2024
|
|
||
| For more information about connection strings, | ||
| see the :ref:`rust-quick-start-connection-string` guide. | ||
| Error: Error { kind: Authentication { message: "SCRAM failure: bad auth : |
Contributor
Author
There was a problem hiding this comment.
Cannot address this Vale issue, rule is set to change soon.
ccho-mongodb
commented
Jan 18, 2024
| For more information about connection strings, | ||
| see the :ref:`rust-quick-start-connection-string` guide. | ||
| Error: Error { kind: Authentication { message: "SCRAM failure: bad auth : | ||
| authentication failed" }, labels: {}, wire_version: None, source: Some(Error |
Contributor
Author
There was a problem hiding this comment.
Cannot address this Vale issue, rule is set to change soon.
ccho-mongodb
commented
Jan 18, 2024
| Error: Error { kind: Authentication { message: "SCRAM failure: bad auth : | ||
| authentication failed" }, labels: {}, wire_version: None, source: Some(Error | ||
| { kind: Command(CommandError { code: 8000, code_name: "AtlasError", message: | ||
| "bad auth : authentication failed", topology_version: None }), |
Contributor
Author
There was a problem hiding this comment.
Cannot address this Vale issue, rule is set to change soon.
added 3 commits
January 18, 2024 14:17
ccho-mongodb
deleted the
DOCSP-34709-connection-troubleshooting-shared
branch
ccho-mongodb
pushed a commit
that referenced
this pull request
Jan 18, 2024
(cherry picked from commit 24074a4)
ccho-mongodb
pushed a commit
that referenced
this pull request
Jan 18, 2024
(cherry picked from commit 24074a4)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request Info
PR Reviewing Guidelines
JIRA - https://jira.mongodb.org/browse/DOCSP-34709
Staging - Connection Troubleshooting
A few notable differences from the current page:
Vale issues responded to in comments.
Self-Review Checklist