Error Accessing Self-Hosted Twenty CRM via Docker - "Object metadata collection not found
i Twenty CRM Support Team,
I'm facing an issue with my self-hosted Twenty CRM instance running on Docker. When accessing the app, I get this error:
Object metadata collection not found for workspace d6d76632-c15f-44b4-90b6-64d29499ba5b
The logs show the following stack trace:
BaseGraphQLError [GraphQLError]: Object metadata collection not found for workspace d6d76632-c15f-44b4-90b6-64d29499ba5b
at new BaseGraphQLError (/app/packages/twenty-server/dist/src/engine/core-modules/graphql/utils/graphql-errors.util.js:86:9)
at generateGraphQLErrorFromError (/app/packages/twenty-server/dist/src/engine/core-modules/graphql/utils/generate-graphql-error-from-error.util.js:14:26)
at /app/packages/twenty-server/dist/src/engine/core-modules/graphql/hooks/use-graphql-error-handler.hook.js:38:194
at Array.map (<anonymous>)
at handleResult (/app/packages/twenty-server/dist/src/engine/core-modules/graphql/hooks/use-graphql-error-handler.hook.js:36:66)
at handleStreamOrSingleExecutionResult (/app/node_modules/@envelop/core/cjs/utils.js:113:5)
at onExecuteDone (/app/packages/twenty-server/dist/src/engine/core-modules/graphql/hooks/use-graphql-error-handler.hook.js:73:74)
at /app/node_modules/@envelop/core/cjs/orchestrator.js:391:42
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async YogaServer.getResultForParams (/app/node_modules/graphql-yoga/cjs/server.js:304:26) {
path: undefined,
locations: undefined,
extensions: { code: 'INTERNAL_SERVER_ERROR' }
}
Details:
Self-hosted Twenty CRM on Docker.
Error occurs when accessing the app, tied to workspace ID d6d76632-c15f-44b4-90b6-64d29499ba5b.
Steps to Reproduce:
Start Twenty CRM via Docker.
Access the web interface.
Error appears with the log entry.
Can you help identify and fix this issue? Let me know if you need more details.
Thanks,
Daniel Gonçalves
2 Replies
I had similar issues, have you updraded to the latest metadata version?
since Im running in ECS, I connect to the image with a ssh tunnel and with
aws ecs run the commandsome error where it looks for this workspace d6d76632-c15f-44b4-90b6-64d29499ba5b that does not exist in the database
The correct workspace is workspace_cpvzrzk9fbxkppv3xc2vjqee3
