Auth.signUp Error in Local Env with Supabase CLI

[alteredorange]

Bug report

Describe the bug

supabase.auth.signup on local setup gives 'Database error finding user'.

A clear and concise description of what the bug is.

Installed supabase cli, set up a local project, and then tried to do a simple user signup. On signup I get a status: 500 with message: Database error finding user.

To Reproduce

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

1. supabase init
2. localhost:8000
3. postgres port 5477 (only thing different from default)
4. create index.js with the following:

import { createClient } from '@supabase/supabase-js'
const SUPABASE_URL = 'http://localhost:8000'
const SUPABASE_ANON_KEY = 'key-here'
const supabase = createClient(SUPABASE_URL, SUPABASE_ANON_KEY)

const main = async () => {
  const { user, session, error } = await supabase.auth.signUp({
    email: 'hi@gmail.com',
    password: 'superpasswordtighty',
  })
  console.log(user)       //null
  console.log(session)  //null
  console.log(error)     //{ message: 'Database error finding user', status: 500 }
}
main()

Expected behavior

A user would be created in the database. I can connect to postgres just fine, and it looks like everything is there (as far as I know). I also tried the auth.signIn method, and I get the same error (which makes sense since there's no user yet). Not sure if the signUp method is getting it's wires crossed with singIn?

Screenshots

postgres database:

System information

• OS: Windows running Ubuntu and Docker Desktop through WSL2

• Version of supabase-js: 1.7.6, cli: 0.3.3

• Version of Node.js: 15.6.0

[KrisCoulson]

I raised a similar issue here. supabase/supabase#1023

Although I am not sure I have the auth.users table in my local db.

[kiwicopple]

@soedirgo Looks like it's here:

cli/src/templates/init/docker/docker-compose.yml

Line 29 in 5666b4d

DATABASE_URL: 'postgres://postgres:postgres@db:5432/postgres?sslmode=disable'

If the port is something other than 5432 I guess GoTrue can't connect

[KrisCoulson]

@kiwicopple just following up here. I did run init on port 5432, so it is a little different. But when running supabase start it doesn't seem any of the supabase tables were created in the database.

[kiwicopple]

Thanks for the follow up @KrisCoulson - let us investigate 👍

[awalias]

there should be some more specific error messages from the gotrue logs in docker, it is almost definitely the case that gotrue either:

• cannot connect to the database
• cannot see or access the auth.users table
• some trigger is causing the insert transaction to fail (seen this a couple of times in the wild)

@KrisCoulson can you try checking or tailing the gotrue logs

[soedirgo]

These are the logs for me:

time="2021-04-01T08:45:39.729628Z" level=debug msg="Set log level to: debug"
time="2021-04-01T08:45:39Z" level=info msg="GoTrue API started on: 0.0.0.0:9999"
time="2021-04-01T08:46:35Z" level=info msg="request started" component=api method=POST path=/signup referer="http://localhost:3000/" remote_addr="172.31.0.2:51926" request_id=90b5f6be-2d6e-40f1-a774-700e1e538b01
time="2021-04-01T08:46:35Z" level=error msg="500: Database error finding user" component=api error="error finding user: ERROR: relation \"users\" does not exist (SQLSTATE 42P01)" method=POST path=/signup referer="http://localhost:3000/" remote_addr="172.31.0.2:51926" request_id=90b5f6be-2d6e-40f1-a774-700e1e538b01
time="2021-04-01T08:46:35Z" level=info msg="request completed" component=api duration=68992000 method=POST path=/signup referer="http://localhost:3000/" remote_addr="172.31.0.2:51926" request_id=90b5f6be-2d6e-40f1-a774-700e1e538b01 status=500

Maybe relevant: auth isn't in search_path, but auth.users exists.

Edit: tried again with auth in search_path, doesn't seem to change anything.

[awalias]

I can also replicate - debugging now

[alteredorange]

Tried a few more times with different settings, still had the same problem. I deleted .supabase and tried again with port: 5432. Interestingly enough, supabase init gives me the exact same credentials each time. Still got the same error, so created an entirely new directory, deleted the docker group, and tried supabase init again with the defaults. Still got the same credentials, and the same Database error finding user.

[soedirgo]

@alteredorange this should be fixed in #12 (you'll have to remove .supabase and re-init). I'll just merge it in now - let me know if it works! Feel free to reopen if it doesn't.

[github-actions]

🎉 This issue has been resolved in version 0.3.4 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[alteredorange]

Yes, I can sign in now, thanks for getting that sorted!!