You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[BUG] Seeing a blank page for local development #1726
I switched to tag v0.4.23 same issue cc: @waleedlatif1@icecrasher321, seeing the same recursive button error The above error occurred in the <button> component. It was handled by the <ErrorBoundary> error boundary., also I see basic requirements like zustand missing in package.json, is there some other branch I should use?
@NuDheeraj its hard to tell, but the blank screen is usually the result of the browser going out of sync with the database. If you've logged into the platform on the same URL and have a different DB connected to it now than when you logged in, the session cookie in your browser is for a different DB and this may be causing issues. To absolve this, you need to open DevTools in the browser > application > cookies > delete the corresponding cookies from the old DB's session. Then you can try logging in again from scratch and see if this fixes the blank screen
@waleedlatif1 I have tried everything by now :), I have tried clearing cache, cleared application site data, installed on a new system from scratch, logged in as new user, tried a new machine, docker exec'd into the db to see if the user has permissions for the workspace and workflow.
Also I notices some weird bugs like when we first start the server, it complains and exits about many missing packages, like Zustand, loadash, etc. Also I am seeing some 404 errors when we are trying to open a canvas for the newly created users(as the graph is empty and backend throws error). I guess there are some seeding scripts or pre installation scripts that are not opensourced, hence you might not be seeing it.
Because of the above I think at this point the dev flow for external contributors is completely broken, it would be great help if you can fix the dev flow for us or suggest me what changes are needed.
I was having similar issues, here's how I got local dev working. I'm using dockered postgres and ollama. Follow the instructions normally with these deviations. You'll still have to install ollama, bun, docker, etc.
You need to edit both .env files
The .env.example file in sim/apps/sim/app/ should actually be in sim/apps/sim. It seems to be in the WRONG directory.
cd sim
cp apps/sim/app/.env.example apps/sim/.env
and should look something like this
# Database (Required)
DATABASE_URL="postgresql://postgres:your_password@localhost:5432/simstudio"# PostgreSQL Port (Optional) - defaults to 5432 if not specified# POSTGRES_PORT=5432# Authentication (Required)
BETTER_AUTH_SECRET=your_secret_key # Use `openssl rand -hex 32` to generate, or visit https://www.better-auth.com/docs/installation
BETTER_AUTH_URL=http://localhost:3000
# NextJS (Required)
NEXT_PUBLIC_SOCKET_URL="http://192.168.4.105:3002"
NEXT_PUBLIC_APP_URL=http://"http://192.168.4.105:3000# Security (Required)ENCRYPTION_KEY=your_encryption_key # Use `openssl rand -hex 32` to generate, used to encrypt environment variablesINTERNAL_API_SECRET=your_internal_api_secret # Use `openssl rand -hex 32` to generate, used to encrypt internal api routes# Email Provider (Optional)# RESEND_API_KEY= # Uncomment and add your key from https://resend.com to send actual emails # If left commented out, emails will be logged to console instead# Local AI Models (Optional)OLLAMA_URL=http://localhost:11434 # URL for local Ollama server - uncomment if using local models
If you have a dev server using it's ip address seems necessary or you get some CORs weirdness.
you should also edit apps/sim/next.config.ts and add your ip address to "allowedDevOrigins"
And then the other steps are more or less the same. This is by no means a production setup but should get you going for local dev. Replace 192.168.4.105 with you boxes LOCAL ip (don't point this thing to the internet).
I was able to make an account, log in, and build a simple chatbot.
Activity
NuDheeraj commentedon Oct 25, 2025
I switched to tag v0.4.23 same issue cc: @waleedlatif1 @icecrasher321, seeing the same recursive button error
The above error occurred in the <button> component. It was handled by the <ErrorBoundary> error boundary., also I see basic requirements like zustand missing in package.json, is there some other branch I should use?[-][BUG] Seeing a blank page on localhost[/-][+][BUG] Seeing a blank page for local development[/+]elviromercic23-cmyk commentedon Oct 26, 2025
NuDheeraj commentedon Oct 27, 2025
@emir-karabeg @waleedlatif1 any pointers on how to resolve this?
Hung392001 commentedon Oct 28, 2025
I also have the same issue with @NuDheeraj , I did some debug logs in backend
frontend:
backend:
waleedlatif1 commentedon Oct 28, 2025
@NuDheeraj its hard to tell, but the blank screen is usually the result of the browser going out of sync with the database. If you've logged into the platform on the same URL and have a different DB connected to it now than when you logged in, the session cookie in your browser is for a different DB and this may be causing issues. To absolve this, you need to open DevTools in the browser > application > cookies > delete the corresponding cookies from the old DB's session. Then you can try logging in again from scratch and see if this fixes the blank screen
NuDheeraj commentedon Oct 29, 2025
@waleedlatif1 I have tried everything by now :), I have tried clearing cache, cleared application site data, installed on a new system from scratch, logged in as new user, tried a new machine, docker exec'd into the db to see if the user has permissions for the workspace and workflow.
Also I notices some weird bugs like when we first start the server, it complains and exits about many missing packages, like Zustand, loadash, etc. Also I am seeing some 404 errors when we are trying to open a canvas for the newly created users(as the graph is empty and backend throws error). I guess there are some seeding scripts or pre installation scripts that are not opensourced, hence you might not be seeing it.
Because of the above I think at this point the dev flow for external contributors is completely broken, it would be great help if you can fix the dev flow for us or suggest me what changes are needed.
0x7575 commentedon Nov 24, 2025
I was having similar issues, here's how I got local dev working. I'm using dockered postgres and ollama. Follow the instructions normally with these deviations. You'll still have to install ollama, bun, docker, etc.
You need to edit both .env files
The .env.example file in sim/apps/sim/app/ should actually be in sim/apps/sim. It seems to be in the WRONG directory.
cd sim cp apps/sim/app/.env.example apps/sim/.envand should look something like this
If you have a dev server using it's ip address seems necessary or you get some CORs weirdness.
you should also edit apps/sim/next.config.ts and add your ip address to "allowedDevOrigins"
And then the other steps are more or less the same. This is by no means a production setup but should get you going for local dev. Replace 192.168.4.105 with you boxes LOCAL ip (don't point this thing to the internet).
I was able to make an account, log in, and build a simple chatbot.