sim [BUG] Failed to create account

Describe the bug When I attempt to register, it gives me err: Failed to create account

To Reproduce Steps to reproduce the behavior:

Load the browser and ip addres
Click on 'Sign up'
Scroll down to 'attempt to create an account by filling the form.'
See error

Expected behavior it should let me create the account

Screenshots

Additional context do have to say I adjusted the prod yml file and .env file but I don't think the sign up page is even coming from my server itself

Sep 04 '25 03:09 ivanjrt

I have exactly the same issue

Sep 04 '25 09:09 OlivierMagnier

same issue how to resolve it

Sep 04 '25 16:09 csesanram

just FYI, I was able to resolve this issue by starting a new VM, with 12GB of RAM.. cause if we look at the docker compose is already asking for 8GB , which is pretty drastic coming to think of it 🤔 anyways with that amount of ram then i was able to sucessfully login to another ERROR lol, (still not sure if it was the RAM or something with Docker, or even in the code, as this time I left it mint condition except for the OLLMAURL pointing to my ollama server).

Here's the next error: "Application error: a client-side exception has occurred (see the browser console for more information)."

yet checked all three containers and they all look Healthy.
I did it in incognito mode
I used another browser
tested on https just for kicks same outcome.

Anyway, I shut down the VM for now until someone can fix the issue or they update the repos?!

Sep 05 '25 00:09 ivanjrt

When i tried to use docker (not localhost) IP using plain http this happens. If you see the debug console, there's issue with crypto.randomUUID() that is not a function. If you try to call it in an insecure context (plain http:// on a remote host), the API (crypto.randomUUID()) will be undefined.

Tunelling out to https using cloudflare, so far no issue.

Just dont forget to set the environments in docker compose files and everything will be smooth.

Sep 05 '25 08:09 bimantoromaesa

I configured the https setup successfully via a Cloudflare tunnel after multiple attempts. To avoid triggering the original "failed to create account" issue, I reused an existing password created under the http version (as creating a new one would revert to the same error). I’ve now reached the next stage.

Current Issue: However, when attempting to select any option from the provided blocks (e.g., Agetn, API, Condition...t, etc.), I encounter a "Deprecation" error regardless of the choice. This is unexpected and blocks further progress.

Sep 05 '25 18:09 ivanjrt

I configured the https setup successfully via a Cloudflare tunnel after multiple attempts. To avoid triggering the original "failed to create account" issue, I reused an existing password created under the http version (as creating a new one would revert to the same error). I’ve now reached the next stage.

Current Issue: However, when attempting to select any option from the provided blocks (e.g., Agetn, API, Condition...t, etc.), I encounter a "Deprecation" error regardless of the choice. This is unexpected and blocks further progress.

You need to change the env SOCKET_SERVER_URL in docker compose file. I can see in the pictures that you've still use localhost:3002.

Sep 06 '25 08:09 bimantoromaesa

I'm glad to see that others above are attempting to resolve the current issue -PR.

Despite a massive amount of attempts to correct the .env file, I encountered repeated loop errors related to Auth and menu functionality issues even under tunnel usage.

I came across launching Chrome in this specific manner: chrome_proxy.exe --unsafely-treat-insecure-origin-as-secure=http://SERVER-IP:3000 - seems to have yielded success for navigating menus. Nonetheless, I've found that only half of the available options function properly when utilizing SSO services. Another bug remains unresolved; however, this will be a separate issue for further investigation...."

PROS: The GUI looks amazing! Better than other workflow competitors, this is hands down. 💯 CONS: there's a learning curve just as the others, and it seems that options are very limited, and it looks like this one will cost me because this is more pointing to AI so...., also I couldn't tell if it has an option to run py or terminal scripts. bummer!

Sep 08 '25 02:09 ivanjrt

In my case, I somehow am able to create an account, but then I can't login because my email is not verified, lol. But I'm obviously not receiving any email to verify my address because there is no email provider configured 😑 I don't even know how to setup SSO properly, since even if I create GOOGLE_CLIENT_ID (& secret), I don't know the vars for the callback URL for example.

There is 0 documentation for self-hosting this...

Also, if anyone else can confirm... Which vars are for inter-container communication, and which ones are for public-facing information? For example... I guess BETTER_AUTH_URL and NEXT_PUBLIC_APP_URL the public-facing URL? But then SOCKET_SERVER_URL should be internal (just for inter-docker communication), right? Or is that variable used on the browser somewhere (in which case it needs to be public-facing as well?). I guess NEXT_PUBLIC_SOCKET_URL is the public socket URL that's passed to the front-end?

Sep 21 '25 14:09 Chinoman10

Describe the bug When I attempt to register, it gives me err: Failed to create account

To Reproduce Steps to reproduce the behavior:
1. Load the browser and ip addres

2. Click on 'Sign up'

3. Scroll down to 'attempt to create an account by filling the form.'

4. See error
Expected behavior it should let me create the account

Screenshots

Additional context do have to say I adjusted the prod yml file and .env file but I don't think the sign up page is even coming from my server itself

I do have a same issued here's... How to solve?

Sep 23 '25 02:09 ataraxianusa

I'm still unsure about the exact issue, but I found a workaround: navigating to the browser's binary folder, such as Chrome's, open Terminal, and run the command:

chrome_proxy.exe --unsafely-treat-insecure-origin-as-secure=http://SERVER-IP:3000

chage IP and port*

I wouldn't recommend using this in a production environment, but it helped me get started. I try it out. At this point, I've decided to put this on hold. Perhaps in the future this approach will be more stable—until then, I'll continue using other services

Sep 27 '25 02:09 ivanjrt

Any updates on this issue?