Is the "Log in with Google" option available?
Hello there!
Is the log in with Google Option available, I was not able to find any doc.
Thx
27 Replies
yes it should be. Make sure you follow the user guide on environment variables to make it appear !
have look at https://twenty.com/developers/section/self-hosting/setup
in your case: AUTH_GOOGLE_ENABLED=true i think
Thanks @Guillaume , followed your suggestion and I added AUTH_GOOGLE_ENABLED=true in the .env file, should I add it else where too? Cause it is not showing up the LOG WITH GOOGLE opzion still.
you are on the latest twenty update ? 0.42 ? or 0.41 ?
I have installed 0.42.6 atm
In the settings, click advanced mode at the bottom and then make sure you enable google one the security options
I dont see Google mention here, only the enterprise button and Add SSO Identity Provider but both are not clickable, how can I enable it?
Thx
Have you added the ENV variables. ??
@ralfdigitalagency please be careful when you share screen of your
.env
I deleted your previous screen as it contained sensible information
I highly recommend re-generating your secretsI deployed everything from scratch and I managed adding the LOG IN WITH GOOGLE button and it seems working, now email sync is not working, I most likely didn t set the right codes, I found a bit confusing the explaination of this guide, this is the only guide? https://twenty.com/developers/section/self-hosting/setup
It is not specified where to insert determined parameters, I added them in env and docker-compose.yml cause gmail parameters were not loaded automatically in docker-compose.yml.
I added the date for emails but I dont' get, cause nothing changed i sync this gmail account, but has been hours now that says importing and has imported nothing but keeps loading and no error found either...🤷♂️
do you have your worker running?
Yes, it is running:
I am currently experiencing issues with my worker container (twenty-worker-1) while the other containers (twenty-db-1 and twenty-server-1) are functioning normally. Here are the details of my setup:
Containers Running:
twenty-db-1 - Status: Healthy
twenty-server-1 - Status: Healthy
twenty-worker-1 - Status: Experiencing issues
I checked the health status of the containers and confirmed that both twenty-db-1 and twenty-server-1 are healthy. However, the worker container is not functioning correctly.
Here are the specific error messages I found in the logs:
Message Import Exception: Unknown error occurred while importing messages.
Calendar Event Import Exception: Unknown error occurred while importing calendar events.
Additionally, I ran the following command and received this output:
docker inspect twenty-worker-1 | grep -i health
"com.docker.compose.depends_on": "db:service_healty:false,server:service_healthy:false",
It seems there might be a misconfiguration in the docker-compose.yml or .env file, possibly due to the typo in service_healty. Are there any sample configurations available for these files that I can refer to for troubleshooting?
Yes, but I get this error,
docker inspect twenty-worker-1 | grep -i health
"com.docker.compose.depends_on": "db:service_healty:false,server:service_healthy:false",
It could be a misconfiguration of docker-compose.yml or .env? Are there samples of those files with all configurations available?
Do you see any error logs in
twenty-worker-1 container?
If so please share the logsI don't see errors apparently
Oh sorry wait. Mis understood the log. Can you check the logs of ther server and the db? because of this?
"com.docker.compose.depends_on": "db:service_healty:false,server:service_healthy:false"Is this helpful?
If you are just now starting and you don't have any data in the application already. Please try to stop the compose and remove the existing volumes and containers and rerun it. Its should fix it. ( Assuming the issue is due to the data which exist in the database )
DB LOGS
root@ubuntu:~/twenty# docker compose logs db | grep -i error
WARN[0000] The "STORAGE_S3_NAME" variable is not set. Defaulting to a blank string.
WARN[0000] The "STORAGE_S3_REGION" variable is not set. Defaulting to a blank string.
WARN[0000] The "STORAGE_S3_ENDPOINT" variable is not set. Defaulting to a blank string.
WARN[0000] The "STORAGE_S3_ENDPOINT" variable is not set. Defaulting to a blank string.
WARN[0000] The "STORAGE_S3_REGION" variable is not set. Defaulting to a blank string.
WARN[0000] The "STORAGE_S3_NAME" variable is not set. Defaulting to a blank string.
Warning are not an issue. This should not effect the inital start of the applications
You can set it later. Or else you can fall back to localstorage if I am not wrong
You can do somthing like this for now
server-1 | [Nest] 1 - 02/24/2025, 10:55:14 AM ERROR [ExceptionsHandler] Metadata version not found for workspace 3eb63287-74ff-424a-b4d4-f147ff5d5303
server-1 | Error: Metadata version not found for workspace 3eb63287-74ff-424a-b4d4-f147ff5d5303
server-1 | BaseGraphQLError [GraphQLError]: Metadata version not found for workspace 3eb63287-74ff-424a-b4d4-f147ff5d5303
server-1 | at new BaseGraphQLError (/app/packages/twenty-server/dist/src/engine/core-modules/graphql/utils/graphql-errors.util.js:86:9)
server-1 | at generateGraphQLErrorFromError (/app/packages/twenty-server/dist/src/engine/core-modules/graphql/utils/generate-graphql-error-from-error.util.js:14:26)
server-1 | at /app/packages/twenty-server/dist/src/engine/core-modules/graphql/hooks/use-graphql-error-handler.hook.js:38:194
server-1 | at handleResult (/app/packages/twenty-server/dist/src/engine/core-modules/graphql/hooks/use-graphql-error-handler.hook.js:36:66)
server-1 | at onExecuteDone (/app/packages/twenty-server/dist/src/engine/core-modules/graphql/hooks/use-graphql-error-handler.hook.js:73:74)
server-1 | extensions: { code: 'INTERNAL_SERVER_ERROR' }
server-1 | throw er; // Unhandled 'error' event
server-1 | SocketClosedUnexpectedlyError: Socket closed unexpectedly
server-1 | Emitted 'error' event on Commander instance at:
server-1 | at RedisSocket._RedisSocket_onSocketError (/app/node_modules/@redis/client/dist/lib/client/socket.js:218:10)
I see errors in server logs here
I restarted and re run the containers many times but nothing, it could be a mis configuration of the docker-compose.yml or and .env files?
Its failing to query some data which is malformed so the GraphQL seems to be throwing errors. So I suggest you to delete the volumes and compose it again.
Yean just restarting will not delete the volume
it is weired cause here it says sync but it is not
So technically all the data in the database is not refreshed
Yeah It may be due to the worker not running as expected
I run:
docker-compose down -v
&
docker-compose up --build
But nothing changed