-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
[Bug]: When deploying Supabase, the Analytics container gives an ERROR. #3380
Comments
I have the same problem, I have tried in previous versions that supabase worked fine and it doesn't work either. |
The variables have been fixed, but the error still persists. Even so, I followed the instructions in this closed issue: Issues 2696, but it didn't solve the problem. |
In version 335 the reported problem persists. |
I'm also facing the same issue. I even added a script to set the password for |
Guys, I found this in the Supabase documentation. I'll try to fix the error, you guys try too, and whoever solves it first, share the step by step here. |
Guys, just run this and restart the degraded services and most of them will work: docker exec -it $(docker ps | grep supabase-db | awk '{print $1}') psql -U postgres -c "ALTER USER supabase_admin WITH PASSWORD '<SERVICE_PASSWORD_POSTGRES>';" use your .env SERVICE_PASSWORD_POSTGRES value to login Now there is another problem, but only in Kong, Rest, Auth, Realtime and Storage. |
docker exec -it $(docker ps | grep supabase-db | awk '{print $1}') psql -U postgres -c "ALTER USER supabase_admin WITH PASSWORD 'SERVICE_PASSWORD_POSTGRES';" docker exec -it $(docker ps | grep supabase-db | awk '{print $1}') psql -U supabase_admin --password use your .env SERVICE_PASSWORD_POSTGRES value to login DROP PUBLICATION logflare_pub; DROP SCHEMA _analytics CASCADE; CREATE SCHEMA _analytics;\q RESTART DEGRADED SERVICES docker exec -it $(docker ps | grep supabase-db | awk '{print $1}') psql -U postgres ALTER ROLE supabase_auth_admin LOGIN;
ALTER ROLE authenticator LOGIN;
ALTER ROLE supabase_storage_admin LOGIN;
ALTER ROLE pgbouncer LOGIN; ALTER ROLE supabase_auth_admin WITH PASSWORD 'SERVICE_PASSWORD_POSTGRES';
ALTER ROLE authenticator WITH PASSWORD 'SERVICE_PASSWORD_POSTGRES';
ALTER ROLE supabase_storage_admin WITH PASSWORD 'SERVICE_PASSWORD_POSTGRES';
ALTER ROLE pgbouncer WITH PASSWORD 'SERVICE_PASSWORD_POSTGRES'; RESTART DEGRADED SERVICES sudo chmod 644 /data/coolify/applications/<id>/volumes/api/kong.yml RESTART DEGRADED SERVICES By doing this, only 3 services are left out, Supabase Auth, Realtime Dev, Minio Createbucket. |
Problema on Supabase Auth
Problema in Realtime Dev
|
Im running non-root user mode with Coolify and I have same issue deploying Supabase From Discord user OzInClouds https://discord.com/channels/459365938081431553/1272785055911247952/1275797493879275572
|
A fix for this issue has been implemented and will be available in an upcoming release. Thank you for your patience. |
Description
I'm on 331, they adjusted the environment variables, but the analytics problem persists. 'failed for user "supabase-admin"'.
Did anyone manage to solve it?
Minimal Reproduction (if possible, example repository)
Exception or Error
Error Postgres
Error Vector:
Error Analytics:
Version
V4.0.0-beta.331
Cloud?
The text was updated successfully, but these errors were encountered: