yup fix just went out!

Sorry about that everyone. Login is fixed now.

did you work this out? if it's working for you in Curl but not JS double check headers are right and the method too. Do you have an HTTP proxy on your machine? That might cause an issue too

Are you using jQuery?

var settings = {
  "url": "https://YOURSUPABASEURL.supabase.co/rest/v1/YOURTABLENAME?select=*",
  "method": "GET",
  "timeout": 0,
  "headers": {
    "Content-Type": "application/json",
    "apikey": "YOUR.PUBLICAPI.KEY-HERE"
  }
};

$.ajax(settings).done(function (response) {
  console.log(response);
});

That should work

Sometimes you need to make sure that you've added this header:

"Content-Type": "application/json"

I'm getting this error message upon logging into app.supabase.io, does anyone have the same issue?

This is it for me...

It has changed to this now

It should be up now

Sorry for the disruption everyone

Working now. Thanks @User

Hello! What are the recommended tools to integrate caching with supabase?

Hello. What are the current easy options to deploy supabase in Kubernetes?

I'm trying to figure out an appropriate local development setup. How do you handle authentication locally? I have github auth turned on and it's giving me an error locally. I also have magic email link turned on but it doesn't seem to send locally (this is using the supabase cli

supabase init

and

supabase start

Locally I get this message for github: "Unsupported provider: Provider is not enabled"

I'm also getting the message "The table

public.TABLE_NAME

does not exist in the current database." when I try to run the app locally

Hello, I'm testing around and I noticed that the response to a signup requests returns user data if the account already exists, like confirmation date and last sign in

{
  "id": "3f70b1fc-dd02-4c00-a7b0-3aa3aff432d9",
  "aud": "authenticated",
  "role": "authenticated",
  "email": "[CENSORED]",
  "email_confirmed_at": "2021-11-15T23:03:18.261849619Z",
  "phone": "",
  "confirmation_sent_at": "2021-11-15T23:03:18.261849619Z",
  "confirmed_at": "2021-11-15T23:03:18.261849619Z",
  "recovery_sent_at": "2021-11-15T21:21:02.274531Z",
  "last_sign_in_at": "2021-11-15T23:03:18.261849619Z",
  "app_metadata": {
    "provider": "email",
    "providers": [
      "email"
    ]
  },
  "user_metadata": {},
  "identities": [],
  "created_at": "2021-11-15T23:03:18.261849619Z",
  "updated_at": "2021-11-15T23:03:18.261849619Z"
}

Is this normal? How can I disable it?

The ID is different from the actual account id, but the mention information is accurate

User data when account already exists

How do I import CSV file into table us when I create tables using SQL command 'CREATE'? (I can import when table is first created using dashboard. )

I’m quite new to this sort of development environment. Would anyone happen to know which credentials I need to input into a SQL client in order to show my Supabase tables?

there’s quite a few credentials floating around the web app and i can’t seem to get a combo that works

It has just come to my attention that there’s a whole page dedicated to doing this exact thing. Forgive me for being unable to read

Has anyone been having problems with storage going offline for a few minutes at a time?

I have a bucket set to public but still get access denied when trying to get publicURL. Any ideas?

Hi, I need some help. I'm trying to query my database with supabase, I am able to query the example tables created with example next.js, but when I create my own table and add data I can't query it. I get no error message and it returns 200, but the data returning is empty..

most of the time people run into this it is the RLS is on but not set or not set correctly.

That's weird, because I have 3 tables, message, message_group and profiles. I can query profiles but not the other two tables, and they both have RLS on

Should you create tables via SQL or can you use table editor to create the schema?