Hi everyone, I’m using Supabase auth and I can successfully sign up a user from the Weweb editor. I deployed my website using a custom URL (bought via Vercel, DNS provided by Cloudflare) and when I go through the same sign up flow, I get a “page not found” error.
Here is what I see in the console:
It’s traced back to an index file variable called var webpack_modules. Any help would be greatly appreciated!
Can you share a video of how things are setup? Ideally, it’d be great if you could walk us through the signup flow inside the editor and then the live app so we can better understand what might be going on.
Thanks a lot!
Hi @Joyce ,
I’m facing the exactly same issue described above.
I recorded the signup process in editor and the same on the live app, and you can view this comparison here:
Attached below is a screenshot illustrating the problem. It appears to be related to a JavaScript function called getPagePath. This function attempts to locate a page identifier, but it seems unable to find it.
I’m not fully aware of the entire code context or why this function is being triggered, particularly in relation to the Supabase authentication process. However, it might be worth investigating since the error seems to originate from the front-end side, specifically within the WeWeb platform.
Could we possibly look into this?
Thanks in advance!
Hi both 
Thanks for taking the time to record the video @RianTavaresDev, appreciate it! I’m trying to reproduce the issue on my side and will rope in the tech team if I can’t figure it out.
In the meantime, I noticed that in the Sign Up action of your workflow, there’s no Email redirect to page selected:
It doesn’t seem to be triggering an error here (maybe it should?) but might want to check it out anyway because you’ll want users to receive a signup email with a link to the login page.
Hey sorry I didn’t get back here! I resolved the issue just by getting rid of a bunch of global workflows that I didn’t need and were messing up a bunch of redirects post auth.
Hi @Joyce
Thank you so much for pointing out the missing selection in the Sign Up action. I’ve updated that field by selecting a page, and it seems to have resolved the authentication issue we were facing. It’s interesting how such a small detail can have a big impact!
Also, I think it might be beneficial for WeWeb to consider making this field mandatory or at least provide a clearer warning when it’s left unconfigured.
Thanks again for your keen observation and support!
Hey @marketplacebuilder ,
I’m glad to hear you found a solution and It’s great that you resolved the issue on your own, and it’s exactly insights like yours that can be tremendously helpful to others facing similar challenges. Sharing such fixes not only helps individuals but strengthens the entire community and enriches our collective knowledge base.
It would be fantastic if you could detail a bit more about your approach in this thread. Also, marking @Joyce 's response as a solution might help others who are scrolling through the thread looking for a fix.
Agreed! I’ll create a product ticket 
Noting this also happens when you set the “email redirect to” a page that is in draft mode.
Since drafts are accessible in the editor, it does not throw an error in the editor.
However, on staging / production it does throw the error because the page wasn’t published (I guess that means the uuid isn’t available to the code that handles the “email redirect to,” therefore throwing a “page not found” error).
I would assume there are other mappings this same thing would happen on, so maybe a UI warning “Make sure to set the draft page live otherwise this will throw an error” anytime you have a page in draft mode that’s used in something like “email redirect to”. However, it is important that we can still map to draft pages because oftentimes that page is being worked on by someone else (or yourself later) and will be fixed before publish.
