mirror of
https://github.com/supabase/supabase.git
synced 2026-10-14 13:49:09 +03:00
Charis
83a6b6695e
Update apps/docs/content/troubleshooting/supabase--your-network-ipv4-and-ipv6-compatibility-cHe3BP.mdx Update supa-mdx-lint/Rule003Spelling.toml
106 lines
4.0 KiB
Plaintext
106 lines
4.0 KiB
Plaintext
---
|
|
title = "Dashboard errors when managing users"
|
|
github_url = "https://github.com/orgs/supabase/discussions/21247"
|
|
date_created = "2024-02-14T04:26:37+00:00"
|
|
topics = [ "auth", "studio" ]
|
|
keywords = [ "users" ]
|
|
database_id = "c5d8260b-c17a-4f6c-ab20-801f953f6c94"
|
|
|
|
[api]
|
|
sdk = [ "auth-signup" ]
|
|
|
|
[[errors]]
|
|
message = "Failed to send magic link: failed to make magiclink request: Error sending magic link"
|
|
|
|
[[errors]]
|
|
message = "Failed to delete user: Database error deleting user"
|
|
|
|
[[errors]]
|
|
message = "Failed to create user: Database error creating new user"
|
|
|
|
[[errors]]
|
|
http_status_code = 500
|
|
message = "Database error saving new user"
|
|
---
|
|
|
|
## PROBLEM
|
|
|
|
### Receiving the following or _similar_ error messages in the Dashboard when managing users.
|
|
|
|
> ... Database error
|
|
> ... Error sending
|
|
|
|
<img
|
|
width="243"
|
|
src="https://github.com/supabase/supabase/assets/91111415/91732e7d-0e83-4bc8-8ce3-57ebd871d981"
|
|
/>
|
|
<img
|
|
width="271"
|
|
src="https://github.com/supabase/supabase/assets/91111415/30f4cd9f-3736-40ae-8606-2f060cfac0d0"
|
|
/>
|
|
<img
|
|
width="271"
|
|
src="https://github.com/supabase/supabase/assets/91111415/50961019-b461-44cb-9e4b-f1361aa3ad5d"
|
|
/>
|
|
|
|
### Or, receiving a comparable 500 error from the Auth REST API:
|
|
|
|
> Database error ...
|
|
|
|
<img
|
|
width="496"
|
|
alt="Screenshot 2024-02-13 at 10 59 17 PM"
|
|
src="https://github.com/supabase/supabase/assets/91111415/cd151dda-5160-415c-925c-cea332887641"
|
|
/>
|
|
|
|
## SOLUTION 1 (trigger related)
|
|
|
|
Check if the auth schema contains any triggers in the [Dashboard's trigger section](https://supabase.com/dashboard/project/_/database/triggers). Remove all triggers by dropping their functions with a CASCADE modifier:
|
|
|
|
```sql
|
|
DROP FUNCTION <function name>() CASCADE;
|
|
|
|
-- If you'd prefer, you can drop the trigger alone with the following query:
|
|
-- DROP TRIGGER <trigger_name> on auth.<table_name>;
|
|
```
|
|
|
|
Then recreate the functions with a [security definer](https://supabase.com/docs/guides/database/functions#security-definer-vs-invoker) modifier before recreating the triggers.
|
|
|
|
The [SQL Editor](https://supabase.com/dashboard/project/_/sql/) contains a template for [User Management](https://supabase.com/dashboard/project/_/sql/quickstarts). Within it, there is a working example of how to setup triggers with security definer that may be worth referencing:
|
|
|
|
```sql
|
|
create table profiles (
|
|
id uuid references auth.users on delete cascade not null primary key,
|
|
updated_at timestamp with time zone,
|
|
username text unique,
|
|
full_name text,
|
|
avatar_url text,
|
|
website text,
|
|
|
|
constraint username_length check (char_length(username) >= 3)
|
|
);
|
|
|
|
create function public.handle_new_user()
|
|
returns trigger as $$
|
|
begin
|
|
insert into public.profiles (id, full_name, avatar_url)
|
|
values (new.id, new.raw_user_meta_data->>'full_name', new.raw_user_meta_data->>'avatar_url');
|
|
return new;
|
|
end;
|
|
$$ language plpgsql security definer;
|
|
|
|
create trigger on_auth_user_created
|
|
after insert on auth.users
|
|
for each row execute procedure public.handle_new_user();
|
|
```
|
|
|
|
### EXPLANATION
|
|
|
|
One of the most common design patterns in Supabase is to add a trigger to the `auth.users` table. The database role managing authentication (supabase_auth_admin) only has the necessary permissions it needs to perform its duties. So, when a trigger operated by the supabase_auth_admin interacts outside the auth schema, it causes a permission error.
|
|
|
|
A security definer function retains the privileges of the database user that created it. As long as it is the `postgres` role, your auth triggers should be able to engage with outside tables.
|
|
|
|
## SOLUTION 2 (constraint related)
|
|
|
|
If you did not create a trigger, check if you created a foreign/primary key relationship between the auth.users table and another table. If you did, then ALTER the [behavior](https://stackoverflow.com/questions/5383612/setting-up-table-relations-what-do-cascade-set-null-and-restrict-do) of the relationship and recreate it with a less [restrictive constraint](https://stackoverflow.com/questions/3359329/how-to-change-the-foreign-key-referential-action-behavior).
|