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

Error: "authentication credentials incorrect", when they should be correct #275

Closed
staltz opened this issue Nov 13, 2021 · 5 comments · Fixed by #308
Closed

Error: "authentication credentials incorrect", when they should be correct #275

staltz opened this issue Nov 13, 2021 · 5 comments · Fixed by #308
Labels
Bug Something isn't working

Comments

@staltz
Copy link
Member

staltz commented Nov 13, 2021

Huge fan of the project!

Got a room set up, made the first admin user, went to login with password, and got this error:

  • The supplied authentication credentials (username or password) are incorrect.

Tried adding the user again with a simpler password (thought maybe I was entering it incorrectly the first time around), but still getting the same error.

I've attached the logs, not really sure what else to try.

Thanks for your help!

ssb_room_error_logs

@staltz staltz added the Bug Something isn't working label Nov 19, 2021
@Count042
Copy link

Count042 commented Dec 1, 2021

I'm having the same issue, having recently deployed a room for an organization I run.

Is there a way I can get a room up and running if I can't login to it as an administrator to configure? Is there a known working version I can deploy in the meantime?

Thanks!

@geoah
Copy link

geoah commented Dec 24, 2021

Just a hint in case it helps anyone who finds this issue: Make sure you are using the correct -repo path. The insert-user tool will not complain if you give it the wrong path. If you're using the docker-compose instructions, make sure you have uncommented the REPO= line in your .env file as it assumes you did so.

@decentral1se
Copy link
Member

decentral1se commented Apr 5, 2022

@geoah do you think we could make insert-user more robust if it 1. made sure the -repo directory existed and/or did some validation 2. ensured that the REPO=... env var is present in the env? That might catch some of these issues & are small & easy fixes.

@decentral1se
Copy link
Member

Also worth noting in case it is not clear, you'll want to use your pubkey as username:

image

image

Seems to me like we might want to rename "username" in the UI to be "public key"?

@staltz
Copy link
Member Author

staltz commented Apr 6, 2022

Seems to me like we might want to rename "username" in the UI to be "public key"?

Agreed!

decentral1se pushed a commit to decentral1se/go-ssb-room that referenced this issue Apr 6, 2022
decentral1se pushed a commit to decentral1se/go-ssb-room that referenced this issue Apr 6, 2022
decentral1se pushed a commit to decentral1se/go-ssb-room that referenced this issue Apr 6, 2022
decentral1se pushed a commit to decentral1se/go-ssb-room that referenced this issue Apr 6, 2022
decentral1se pushed a commit to decentral1se/go-ssb-room that referenced this issue Apr 6, 2022
staltz pushed a commit that referenced this issue Apr 6, 2022
staltz pushed a commit that referenced this issue Apr 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working
Projects
None yet
4 participants