Created a signup on my website but it appears to hang and give me a

[tomwattsuk]

Hi there,

I have a sign up and i appear to be getting these errors in the console logs via Supabase:

index-D8wcLzCL.js:142  Auth Error (signup): {message: 'Request timed out. Please try again.', code: undefined, status: undefined, details: {…}, timestamp: '2025-02-21T23:54:31.712Z'}
Nt @ index-D8wcLzCL.js:142
P2 @ index-D8wcLzCL.js:142
index-D8wcLzCL.js:142  Auth Error (signup_catch): {message: 'Request timed out. Please try again.', code: undefined, status: undefined, details: undefined, timestamp: '2025-02-21T23:54:31.713Z'}

The Supabase logs themselves show a 500 error with:

POST | 500 | 31.94.10.69 | 915aaeaf39b394a5 | https://.supabase.co/auth/v1/signup?redirect_to=https%3A%2F%2Fapp.gamefolio.com%2Faccount | Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/133.0.0.0 Safari/537.36 Edg/133.0.0.0

The only issue i see above is that the url for the redirect is encoded so ive checked the redirect url in the supabase settings and it's not encoded so that might just be what supabase sends back?

Any helps, greatly appreciated!

[GaryAustin1]

Not very clear what you have going on here.
Check your dashboard auth and Postgres logs for more error info.
It is very common for new users to get a 500 error because their auth.users insert trigger function for a public table is not working.
No idea from your info if that is the case or not.

[tomwattsuk]

Hi there, apologies if I was not very clear on what I’m doing, basically I’m using resend (or trying too) via Supabase to auth users via an email, however, I’m not sure what I’m doing wrong to set it up. I have checked Postgres logs, no errors in there upon sign up expect a warning log: { "event_message": "PgBouncer auth request: supabase_storage_admin", "id": "0a2f3675-cc6c-4d06-8f3d-13d3a49f8f81", "metadata": [ { "file": null, "host": "db-jtltfipzywkiiejzjeps", "metadata": [], "parsed": [ { "application_name": "Supavisor auth_query", "backend_type": "client backend", "command_tag": "SELECT", "connection_from": "2600:1f18:2e13:9d00:561a:678b:d622:c165:40478", "context": "PL/pgSQL function pgbouncer.get_auth(text) line 3 at RAISE", "database_name": "postgres", "detail": null, "error_severity": "WARNING", "hint": null, "internal_query": null, "internal_query_pos": null, "leader_pid": null, "location": null, "process_id": 294597, "query": null, "query_id": -2227272355416136200, "query_pos": null, "session_id": "67b9d234.47ec5", "session_line_num": 4, "session_start_time": "2025-02-22 13:33:40 UTC", "sql_state_code": "01000", "timestamp": "2025-02-22 13:33:40.334 UTC", "transaction_id": 0, "user_name": "pgbouncer", "virtual_transaction_id": "12/6334" } ], "parsed_from": null, "project": null, "source_type": null } ], "timestamp": 1740231220334000 } On 22 Feb 2025, at 01:20, GaryAustin1 ***@***.***> wrote: Not very clear what you have going on here. Check your dashboard auth and Postgres logs for more error info. It is very common for new users to get a 500 error because their auth.users insert trigger function for a public table is not working. No idea from your info if that is the case or not. — Reply to this email directly, view it on GitHub<#33781 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ALDIXRWAI6UARN5BOMZR3UL2Q7GHLAVCNFSM6AAAAABXUKFWZKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMRYGI4TGNY>. You are receiving this because you authored the thread.Message ID: ***@***.***>