Problem loading login page after fresh install
I had a working system that I built recently, I believe it was a version 0.35 but I'm not sure, it was whatever was current in github at the time. (3 weeks ago)
I refreshed the project files from git and now I can't get to the login page. it just comes up as a blank page.
I'm getting an error in the browser - see next post
I'm not where to look next on this, I've gone through the troubleshooting section and nothing has helped so far.
I ran yarn and reset the database, both with seed and no seed (this is for test so no data to worry about yet)
the system is Ubuntu server 24.04
local install of twenty using a local postgres and redis on alternate ports (to not conflict with a docker install)
I appreciate any ideas. thanks
5 Replies
Uncaught Error: Snapshot has already been released.
err index.js:16
retain index.js:3820
useRecoilSnapshot index.js:5774
useRecoilSync index.js:356
RecoilURLSync index.js:2156
React 11
workLoop scheduler.development.js:266
flushWork scheduler.development.js:239
performWorkUntilDeadline scheduler.development.js:533
js scheduler.development.js:571
js scheduler.development.js:633
require2 chunk-LK32TJAX.js:18
js index.js:6
require2 chunk-LK32TJAX.js:18
React 2
require2 chunk-LK32TJAX.js:18
js React
require2 chunk-LK32TJAX.js:18
js React
__require2 chunk-LK32TJAX.js:18
<anonymous> react-dom_client.js:39
index.js:16:16
And one in the server console:
ForbiddenException: Forbidden resource
at canActivateFn (/home/dev1/twenty/node_modules/@nestjs/core/helpers/external-context-creator.js:157:23)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at target (/home/dev1/twenty/node_modules/@nestjs/core/helpers/external-context-creator.js:73:31)
at Object.currentUser (/home/dev1/twenty/node_modules/@nestjs/core/helpers/external-proxy.js:9:24)
at field.resolve (/home/dev1/twenty/node_modules/@envelop/on-resolve/cjs/index.js:36:42)
at /home/dev1/twenty/node_modules/graphql-yoga/node_modules/@graphql-tools/executor/cjs/execution/promiseForObject.js:18:35
at async Promise.all (index 0) {
path: undefined,
locations: undefined,
extensions: { code: 'INTERNAL_SERVER_ERROR', response: 'Forbidden resource' }
Some further info on this, I updated to the latest commit in git (0.40 it looks like) and reset the database again, and ran the update commands from v0.34 to 0.35 yarn database:migrate:prod and yarn command:prod upgrade-0.35
and now I'm able to login, and it created a workspace, which looks good. However I still get these react errors when clicking on things, it seems random which things. When I get these errors the page goes completely blank and I have to refresh to get back to anything.
Is there a step I'm missing when updating this way?
This is the error in the browser:
The above error occurred in the <RecoilURLSync> component:
RecoilURLSync@http://apple.localhost:3001/@fs/home/dev2/twenty/node_modules/.vite/packages/twenty-front/deps/recoil-sync.js?v=df07c325:4831:23
RecoilURLSyncJSON@http://apple.localhost:3001/@fs/home/dev2/twenty/node_modules/.vite/packages/twenty-front/deps/recoil-sync.js?v=df07c325:4955:7
RecoilRoot_INTERNAL@http://apple.localhost:3001/@fs/home/dev2/twenty/node_modules/.vite/packages/twenty-front/deps/chunk-L5UCSPRO.js?v=df07c325:2793:29
RecoilRoot@http://apple.localhost:3001/@fs/home/dev2/twenty/node_modules/.vite/packages/twenty-front/deps/chunk-L5UCSPRO.js?v=df07c325:2914:7
App
Consider adding an error boundary to your tree to customize error handling behavior.
Visit https://reactjs.org/link/error-boundaries to learn more about error boundaries. suppress-nextjs-warning.ts:7:20
More info on this, I've found a post in facebook github that deals with the same error message, that problem came down to a timeout value in firefox.
So I tried using chromium and I don't have the problem there, so this may be specific to firefox. I'm new to this and I'm not sure how this applies to twenty, but for now I can use chromium.
Here is the post I found in case it helps anyone:
https://github.com/facebookexperimental/Recoil/pull/2243
Summary:
This pull request addresses an issue regarding the functioning of setTimeout in Firefox, which behaves slightly differently from Chrome. The previous solution utilized a setTimeout delay of 10ms, but after conducting tests, I discovered that nested timeouts provide a more optimal approach, eliminating crashes and improving compatibility with Firefox.
Fixes: #1994
GitHub
Fix: Snapshot has already been released (#1994) by cjvnjde · Pull R...
Summary:
This pull request addresses an issue regarding the functioning of setTimeout in Firefox, which behaves slightly differently from Chrome. The previous solution utilized a setTimeout delay o...
It's because Firefox (and Safari and few others) uses their own engine rather than Chromium which Chrome is built on top of, so that's nothing unusual, if you can, please report this issue with attached video of mentioned behaviour
What version of Postgresql you installed ? I installed locally on rocky linux. When installed latest postgreql failing for pgvector extension and others. These extension not available for latest posgesql 17 .
I'm using postgresql 16.6, I had to install pgvector manually, but that worked fine. I haven't looked at trying 17 yet.