#No logs after launch

1 messages · Page 1 of 1 (latest)

hot geyser
#

Hello

I use the same docker file from github, without any specific parameters. I have logs when all services are launched, but nothing after. I tried to add LOG_LEVEL: debug in the docker-compose and other stuff like that, but no improvement.

`$docker-compose logs -f server

codex-server | [Nest] 1 - 07/21/2025, 9:22:50 PM LOG [DatabaseConfigDriver] [INIT] Loading initial config variables from database
codex-server | [Nest] 1 - 07/21/2025, 9:22:50 PM LOG [DatabaseConfigDriver] [INIT] Config variables loaded: 0 values found in DB, 53 falling to env vars/defaults
codex-server | [Nest] 1 - 07/21/2025, 9:22:50 PM LOG [GraphQLModule] Mapped {/metadata, POST} route
codex-server | [Nest] 1 - 07/21/2025, 9:22:50 PM LOG [GraphQLModule] Mapped {/graphql, POST} route
codex-server | [Nest] 1 - 07/21/2025, 9:22:50 PM LOG [NestApplication] Nest application successfully started`

Twenty works, I can use it. But I need to track an error which occurs when I try to create a worskpace ("An error occured" in the front).

Any idea how I can have logs? I use last 1.1.1 version

Thanks

old spindle
#

Hello ! Please share the error in the graphql response body in your browser console

hot geyser
#

Hi Prastoin. No error in the console, just the error message in bottom right corner and nothing happening when I do the new workspace

old spindle
#

Please check network tab

#

It seems like a graphql req is responding 200 with data but also an error response field

#

Could be related to your other HELP thread regarding version issue

#

We should handle the version first

hot geyser
#

Got it :

{ "errors": [ { "message": "New workspace setup is disabled", "extensions": { "subCode": "SIGNUP_DISABLED", "userFriendlyMessage": "An error occurred.", "code": "FORBIDDEN" } } ], "data": null }

Any idea why I don't get those errors in the server logs?

old spindle
#

Are you trying to do multi workspace self hosted instance ?

hot geyser
#

yes!

old spindle
#

Then you need to configure your instance

#

I'm searching for the docs section Seems like env variable pages has been removed

#

IS_MULTIWORKSPACE_ENABLED you need to setup this env variable to true

hot geyser
#

OK, I try that, Indeed, the former "IS_SIGN_UP_DISABLED" variable seemed to be deprecated/removed

old spindle
#

Indeed IS_SIGN_UP_DISABLED does not seem to exist anymore

hot geyser
#

OK, so I added:

IS_MULTIWORKSPACE_ENABLED=true
in my .env and

IS_MULTIWORKSPACE_ENABLED: ${IS_MULTIWORKSPACE_ENABLED:-true}

But same error

old spindle
#

Have you restarted ?

hot geyser
#

sure

old spindle
#

Please double check the env variable value in your twenty-server

#

env | grep IS_MULTIWORKSPACE_ENABLED

hot geyser
#

OK, it seems that I need to add a subdomain "app" (ie app.server.domain)
I created the CNAME entry in DNS, updated nginx and certbot. I just have to wait for DNS propagation and I test again

hot geyser
#

OK it works! the wildcard redirection and certificates were tricky

But I still haven't any logs !

old spindle
#

Congrats
What's the value of the log env var in your twenty-server container ?

hot geyser
#

I don't see any LOG variable:

/app/packages/twenty-server $ env NODE_VERSION=22.17.0 HOSTNAME=2343b7ece333 YARN_VERSION=1.22.22 REACT_APP_SERVER_BASE_URL= SHLVL=1 IS_MULTIWORKSPACE_ENABLED=true HOME=/home/node DISABLE_CRON_JOBS_REGISTRATION= PG_DATABASE_URL=postgres://xxxxxx@db:5432/default NODE_PORT=3000 STORAGE_TYPE=local TERM=xterm APP_SECRET=XXXX PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin SIGN_IN_PREFILLED=false DISABLE_DB_MIGRATIONS= SERVER_URL=https://xxxxxx PWD=/app/packages/twenty-server REDIS_URL=redis://codex-redis:6379 APP_VERSION=v1.1.1

#

I added "LOG_LEVELS: log" in my docker compose, now I have
LOG_LEVELS=log in the env of my twenty server container.

Still no log updates

old spindle
#

What logs are you searching for to see ?

hot geyser
#

connections requests, logging failure, access to data, updates, etc

#

even the error message for the workspace creation problem!

west temple
#

wrt/ log levels: I was able to increase the loglevel when investigating on issues I faced by setting the environment variable as:

LOG_LEVELS=log,error,warn,debug