Help Needed: Can't Sign Up with Supabase on Published URL in WeWeb

I’m facing an issue with my published WeWeb project. Everything works fine in preview mode, but when I test the published URL, I get this error in the browser console when trying to sign up or log in:

i get this message in my console when trying to sign up
chunk-common.8742bf62.js:1 Error: Invalid Supabase Auth configuration.
at Object.signInEmail (chunk-common.8742bf62.js:1:179003)
at ke (chunk-common.8742bf62.js:1:68039)
at Le (chunk-common.8742bf62.js:1:52662)
at Le (chunk-common.8742bf62.js:1:53053)
at async Ce (chunk-common.8742bf62.js:1:51471)

I’ve double-checked my Supabase credentials (URL and anon key) in WeWeb’s environment variables, and they seem correct. I’ve also ensured the redirect URLs in Supabase match my published URL, also i have changed my site url to the published URL.

Is there something specific I might be missing in configuring authentication for the published environment? Any help or advice would be greatly appreciated! :blush:

Thanks in advance!

Hi @Williams :wave:

Apologies for the late reply.

I’ve also ensured the redirect URLs in Supabase match my published URL, also i have changed my site url to the published URL. - An issue with this would have been my guess but it sounds like you covered it.

Are you using email + password as Supabase Auth or working with OAuth?

I have exactly the same problem. It is just a simple app with Supabase auth. In the editor mode, everything works fine, but in production.

Hi @Omazon :waving_hand:

One thing that could explain this is if you have a link to the editor in the Supabase URL Configuration but not the link to the app in production.

Can you check?

I have the same exact issue.

Hi @ccoombe :waving_hand:

Can you try removing a * at the end of the redirect URL? ** is not a valid wildcard.

Hi - I changed to one and it still did not work

Demonstration of Unresponsive Feature and Feedback
Watch Video

Hi @Joyce! I have the same problem. Do you know what it is? I even tried to put more urls.

I’m still facing this problem. I updated to host and bought a subdomain but I can’t sign in when I’m production but I can sign in when I’m on stage.

CC: @Joyce

1 Like

Hi people, I have the same problem. I am following this issue for any solution !! thanks!!

Did you find a solution?

Hi guys, how exactly does the issue happen to you? Where do you get stuck? Are you trying to sign up with OAuth or basic authentication? Did you disable Email verification in Supabase? Are both plugins connected? I think we will need to go through the project of each user. Let me know if you can share that in the support chat.

1 Like