Local setup frontend crashes without error

I am running twenty local setup in my VM. npx nx start twenty-server runs without any error npx nx worker twenty-server runs without any error npx nx start twenty-front initially runs fine. I am able to initially reach localhost:3001/welcome where my browser stucks for a while and after a while the frontend crashes without any error in terminal. need help to determine what can be the issue for the crash? I am unable to reach localhost:3000 or localhost:3000/rest localhost:3000/graphql works as expected.
No description
No description
No description
12 Replies
Prastoin
Prastoin2mo ago
Hello @DecodersLord ! Hard to say, could it be a VM cpu issue ? It's weird for it to just stop without any logs, do you have anything in your browser console before it crashes ? Have you been able to see the frontend on your browser ?( What do you mean by it crashes exactly)
nade
nade2mo ago
This seems similar to 1313503669785858088
thomast
thomast2mo ago
Hi, what is your VM ram?
DecodersLord
DecodersLordOP2mo ago
Apologies for late response. VM had only 8 GM ram, I upgraded it to 32 GB and it stopped crashing. However, Now when I hit localhost:3001/ it prompts to login with email when I click it, it redirects to localhost:3001/welcome which only displays white screen. No errors on console. Any suggestions what could be the issue?
thomast
thomast2mo ago
what version are you using? did you upgrade recently?
DecodersLord
DecodersLordOP2mo ago
yup... I did fork and pull my repo recently
thomast
thomast2mo ago
what version were you using before and what version are you using now?
DecodersLord
DecodersLordOP2mo ago
I was able to build using WSL and docker in v0.23 and wanted to move to VM setup with latest v0.42. I believe this is the issue. I couldn't find any related issue on github.
No description
DecodersLord
DecodersLordOP2mo ago
No description
charles
charles2mo ago
@DecodersLord are you trying to upgrade or to make a fresh setup?
DecodersLord
DecodersLordOP2mo ago
fresh setup
thomast
thomast2mo ago
but maybe you tried to re-use your existing DB? Your schema is looks not up to date, which makes sense if you were running in v0.23 and you are now in v0.42 you need to either upgrade your DB version one by one until you reach 0.42, either do a fresh install with a new DB

Did you find this page helpful?