supabase: Kong Error Invalid authentication credentials

Bug report

  • I confirm this is a bug with Supabase, not with my own application.
  • I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug

I have followed all setup (here) and I keep having the follwing error after login : Kong Error Invalid authentication credentials.

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

  1. Go to my proxy URL ‘https://supabase.<mydomain>.com/’ (in .env is the value of SITE_URL)
  2. Enter credentials (DASHBAOARD_USERNAME and DASHBOARD_PASSWORD)
  3. See error Kong Error Invalid authentication credentials.

Expected behavior

Access to the Dashboard.

Screenshots

If applicable, add screens supabase1 supabase2 hots to help explain your problem.

System information

Additional context

Here is the docker compose ps result : NAME IMAGE COMMAND SERVICE CREATED STATUS PORTS realtime-dev.supabase-realtime supabase/realtime:v2.25.35 "/usr/bin/tini -s -g -- /app/limits.sh sh -c '/app/bin/migrate && /app/bin/realtime eval 'Realtime.Release.seeds(Realtime.Repo)' && /app/bin/server'" realtime 4 hours ago Up 17 minutes (healthy) supabase-analytics supabase/logflare:1.4.0 "sh run.sh" analytics 4 hours ago Up 17 minutes (healthy) 0.0.0.0:4000->4000/tcp, :::4000->4000/tcp supabase-auth supabase/gotrue:v2.125.1 "gotrue" auth 4 hours ago Up 17 minutes (healthy) supabase-db supabase/postgres:15.1.0.117 "docker-entrypoint.sh postgres -c config_file=/etc/postgresql/postgresql.conf -c log_min_messages=fatal" db 4 hours ago Up 17 minutes (healthy) 0.0.0.0:5432->5432/tcp, :::5432->5432/tcp supabase-edge-functions supabase/edge-runtime:v1.29.1 "edge-runtime start --main-service /home/deno/functions/main" functions 4 hours ago Up 17 minutes supabase-kong kong:2.8.1 "bash -c 'eval \"echo \\\"$(cat ~/temp.yml)\\\"\" > ~/kong.yml && /docker-entrypoint.sh kong docker-start'" kong 4 hours ago Up 17 minutes (healthy) 0.0.0.0:8000->8000/tcp, :::8000->8000/tcp, 8001/tcp, 0.0.0.0:8443->8443/tcp, :::8443->8443/tcp, 8444/tcp supabase-meta supabase/postgres-meta:v0.75.0 "docker-entrypoint.sh npm run start" meta 4 hours ago Up 17 minutes (healthy) 8080/tcp supabase-rest postgrest/postgrest:v11.2.2 "postgrest" rest 4 hours ago Up 17 minutes 3000/tcp supabase-storage supabase/storage-api:v0.43.11 "docker-entrypoint.sh node dist/server.js" storage 4 hours ago Up 17 minutes (healthy) 5000/tcp supabase-studio supabase/studio:20231123-64a766a "docker-entrypoint.sh node apps/studio/server.js" studio 4 hours ago Up 17 minutes (unhealthy) 3000/tcp supabase-vector timberio/vector:0.28.1-alpine "/usr/local/bin/vector --config etc/vector/vector.yml" vector 4 hours ago Up 17 minutes (healthy)

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Reactions: 4
  • Comments: 24

Most upvoted comments

This workaround worked for me:

  1. Open the Supabase dashboard with the username and password in the URL. This takes you to the dashboard, but none of the data loads properly. eg: https://username:password@your-supabase-dashboard-domain.com

  2. Close that tab, and then open a new tab without the username and password. Now the data should load! eg: https://your-supabase-dashboard-domain.com

This issue still occurs, why was it closed? why don’t they fix it? why the work arounds? there is obviously something wrong here.

This workaround worked for me:

1. Open the Supabase dashboard **with the username and password in the URL**.
   This takes you to the dashboard, but none of the data loads properly.
   _eg: https://username:password@your-supabase-dashboard-domain.com_

2. Close that tab, and then open a _new_ tab **without** the username and password.
   Now the data should load!
   _eg: https://your-supabase-dashboard-domain.com_

works, I swear man such a bs issue, I respect everyone but imagine a noob like me trying to do something in life only to get to this seemingly, easily, fixable problem; but waste hours to troubleshoot.

Ran into this github pages, I have to tell you guys to chill. It is simple authentication, like, really simple that it read the cookies first. If your cookies are ‘invalid password’ cookies, then it will always show invalid authentication. WHY? Because it read the cookies before taking in your input (password).

Clear the cookies for the supabase (usually localhost:8000), close the browser, reopen the browser and go back to your supabase (usually localhost:8000) and this time make sure to input it correctly.

You are welcome.

Seems like you can get around it by putting the login credentials in the url: https://stackoverflow.com/questions/50528467/how-to-add-login-credentials-to-url i.e. http://username:password@127.0.0.1:8000/

Well, this is a false start for me with Supabase. I don’t have the time to deal with this kind of issue. UPDATE: Gave it another try. The issue occurs when I change the credentials. I tried adding the credentials in the Kong file rather than the .env file, but the same problem persists. What junk! …an we are 1 year later!

Thanks for the temporary workaround.

Why was this closed as completed? What was changed?

Changing credentials in the kong.yml and let credentials blank in .env is make it work.

The problem I have is that there’s no way to clear this error. I actually did enter wrong credentials, but the page offers no way to try again, and clearing browser data associated with localhost doesn’t clear it.

So now there’s no way to access the dashboard.

This is still a mess. I have cleared cookies, restarted browser, and I can’t get it to allow me on the login page, just because I screwed up typing in the credentials one single time. Please fix this!

Or, better yet, why not have an actual normal login screen?