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

Incorrect URI schema in the Self-hosted MongoDB document #41894

Closed
milos-teleport opened this issue May 22, 2024 · 0 comments · Fixed by #41929
Closed

Incorrect URI schema in the Self-hosted MongoDB document #41894

milos-teleport opened this issue May 22, 2024 · 0 comments · Fixed by #41929
Assignees

Comments

@milos-teleport
Copy link

milos-teleport commented May 22, 2024

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, the uri has a value without the schema prefix:

  --uri=mongo.example.com:27017 \

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:

MongoServerSelectionError: error connecting to the database
    error parsing uri: scheme must be "mongodb" or "mongodb+srv"

How will we know this is resolved?

Have the URI use the mongodb:// schema prefix for the URI value

@milos-teleport 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 ptgott self-assigned this 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
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants