-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Incorrect URI schema in the Self-hosted MongoDB document #41894
Labels
Comments
milos-teleport
changed the title
Fix the incorrect URI schema in the Self-hosted MongoDB document
Incorrect URI schema in the Self-hosted MongoDB document
May 22, 2024
ptgott
added a commit
that referenced
this issue
May 22, 2024
Fixes #41894 These were missing, causing errors for users.
github-merge-queue bot
pushed a commit
that referenced
this issue
May 23, 2024
Fixes #41894 These were missing, causing errors for users.
github-actions bot
pushed a commit
that referenced
this issue
May 23, 2024
Fixes #41894 These were missing, causing errors for users.
github-actions bot
pushed a commit
that referenced
this issue
May 23, 2024
Fixes #41894 These were missing, causing errors for users.
github-actions bot
pushed a commit
that referenced
this issue
May 23, 2024
Fixes #41894 These were missing, causing errors for users.
github-merge-queue bot
pushed a commit
that referenced
this issue
May 23, 2024
Fixes #41894 These were missing, causing errors for users.
github-merge-queue bot
pushed a commit
that referenced
this issue
May 23, 2024
Fixes #41894 These were missing, causing errors for users.
github-merge-queue bot
pushed a commit
that referenced
this issue
May 23, 2024
Fixes #41894 These were missing, causing errors for users.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Applies To
https://goteleport.com/docs/database-access/guides/mongodb-self-hosted/
Details
In step 1/3 where the user is asked to create the
/etc/teleport.yaml
, theuri
has a value without the schema prefix:We have had a user reach out to us over slack where he demonstrates that this is the error that they recieve while following the guide verbatim:
How will we know this is resolved?
Have the URI use the
mongodb://
schema prefix for the URI valueThe text was updated successfully, but these errors were encountered: