T
Twenty4w ago
Alex

Docker 1-click/manual self-hosting fails

Hello, I have been trying to self-host using docker following the instructions here: https://twenty.com/developers/section/self-hosting/docker-compose While both 1-click and manual instructions create the docker containers and start them up just fine, when try to access http://localhost:3000, I get the following error:
server-1 | [
server-1 | Error: Boolean cannot represent a non boolean value: ""
server-1 | at completeLeafValue (/app/node_modules/@graphql-tools/executor/cjs/execution/execute.js:620:19)
server-1 | at completeValue (/app/node_modules/@graphql-tools/executor/cjs/execution/execute.js:451:16)
server-1 | at completeValue (/app/node_modules/@graphql-tools/executor/cjs/execution/execute.js:434:27)
server-1 | at /app/node_modules/@graphql-tools/executor/cjs/execution/execute.js:327:49
server-1 | at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
server-1 | at async /app/node_modules/@graphql-tools/executor/cjs/execution/promiseForObject.js:18:35
server-1 | at async Promise.all (index 2) {
server-1 | path: undefined,
server-1 | locations: undefined,
server-1 | extensions: {
server-1 | code: 'INTERNAL_SERVER_ERROR',
server-1 | response: 'Boolean cannot represent a non boolean value: ""'
server-1 | }
server-1 | }
server-1 | ]
server-1 | [
server-1 | Error: Boolean cannot represent a non boolean value: ""
server-1 | at completeLeafValue (/app/node_modules/@graphql-tools/executor/cjs/execution/execute.js:620:19)
server-1 | at completeValue (/app/node_modules/@graphql-tools/executor/cjs/execution/execute.js:451:16)
server-1 | at completeValue (/app/node_modules/@graphql-tools/executor/cjs/execution/execute.js:434:27)
server-1 | at /app/node_modules/@graphql-tools/executor/cjs/execution/execute.js:327:49
server-1 | at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
server-1 | at async /app/node_modules/@graphql-tools/executor/cjs/execution/promiseForObject.js:18:35
server-1 | at async Promise.all (index 2) {
server-1 | path: undefined,
server-1 | locations: undefined,
server-1 | extensions: {
server-1 | code: 'INTERNAL_SERVER_ERROR',
server-1 | response: 'Boolean cannot represent a non boolean value: ""'
server-1 | }
server-1 | }
server-1 | ]
I'd appreciate any insight into why this happens and how to fix it.
7 Replies
thomast
thomast3w ago
Hi @Alex , this is a bit hard to debug with only the error Error: Boolean cannot represent a non boolean value: "". It may come from env variables that are strings instead of boolean. Or data in your database if you are not using the one we seed by default
Alex
AlexOP3w ago
Hi @thomast -- I haven't changed any of the env variables, and I am using the seeded db. I get this result when doing the 1-click setup, and nothing was changed there at all. I'm using the .env.example file under packages/twenty-docker/.env.example and when setting it up manually, I only added my own APP_SECRET and PGPASSWORD_SUPERUSER values. None of the env variables provided appear to be booleans. I have not changed the db set up or the docker-compose.yml file at all.
ddino
ddino3w ago
We are having the smae issue. any insight would be appreciated cc @thomast 🙂
Duc Vu
Duc Vu3w ago
Problem can be resolved by setting SIGN_IN_PREFILLED=false in .env file.
thomast
thomast3w ago
can be yes! Are any boolean env variables that are set to "" or empty
Paul
Paul3w ago
In my case I found it was the s3 storage options that were blank. I am not using those but I set them to dummy values and it got past this problem.# storage options cannot be blank - get a login error STORAGE_S3_REGION=eu-west3 STORAGE_S3_NAME=my-bucket STORAGE_S3_ENDPOINT=0
Alex
AlexOP3w ago
These helped fix the issue. Thanks everyone!

Did you find this page helpful?