Scram authentication error when running seed-jaffle.sh
See original GitHub issueDescribe the bug
I was following the guide on https://github.com/lightdash/lightdash/blob/main/.github/CONTRIBUTING.md#setup-development-environment, when I tried to run ./docker/scripts/seed-jaffle.sh
I got the following error
However, the version of libpq is on 13.5
I found this post about the same issue
There it suggests to downgrade the version of libpq in pip , that fixed the issue for me too.
pip install psycopg2-binary==2.8.6
However, it says it might affect performace, so this fix requires a bit more investigation.
To Reproduce
- Follow the CONTRIBUTING guide and build a new dev environment
- Run docker compose
- Follow the guide until you reach
./docker/scripts/seed-jaffle.sh
- See error
Expected behavior
./docker/scripts/seed-jaffle.sh
should run without errors
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
How can I solve Postgresql SCRAM authentication problem?
Step 3: Open command line (cmd,cmder,git bash...) and run psql -U postgres then enter your password when installed postgres sql; Step 4: Then ......
Read more >PostgreSQL 14 and Recent SCRAM Authentication Changes
The reason for these errors is the defaults for password encryption are changed in new versions of PostgreSQL to SCRAM authentication.
Read more >Cannot do SCRAM authentication when using auth_query
Hi, I'm testing new SCRAM support in version 1.14, and a unexpected behavior occurs with an auth_query configuration.
Read more >Unable to authenticate using mechanism "SCRAM-SHA-1"
You are connecting to localhost:27004. If no mongo is running there, your command will always failed. Jason_Hernandez ...
Read more >Troubleshoot issues when using Amazon MSK cluster with ...
Your Amazon MSK cluster has Simple Authentication and Security Layer (SASL)/Salted Challenge Response Mechanism (SCRAM) authentication enabled.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This has happened to me as well. To remind myself for next time, from the bash prompt in the docker image:
Have also just experienced this issue. downgrading libpq in pip also worked for me