Workspace not found for multi workspace

[urban star]

Tested the exact same config on my local and works fine, the only difference is that this is hosted on a vps and have server url points to the ip. if multi workspace is disable there's no issues.

Anyone having the same problem?

When testing locally it does have the same workspace not found error, but the one on the vps just keeps refreshing the page every second.

[formal elk]

Are you running Twenty behind a proxy?

[urban star]

no

havent setup proxy or domain yet

[naive sand]

[help me please]

Even adjusting .env didn't work.

What is the .env path to activate multi-workspace? Is there a specific folder? Or is it in the application root?

I use cloudflare, and I had created a wildcard domain. Is this really necessary?

Will I have to adjust nginx? If so, does anyone have an example of what it would look like?

[prisma ether]

You need to update your .env file

[naive sand]

what is the .env path to enable multi workspace? twenty/packages/twenty-server
/.env

on the panel, it is not editable, is this normal? Is it possible to activate it via the panel so that I don't need to manipulate .env on the server?

[naive sand]

Yes, I adjusted the .env file in the project root. I'm using Docker. Are there other folders with .env files that I can edit?

It's not editable on the panel. Is this normal? Is it possible to activate it via the panel so that I don't have to manipulate .env on the server?

[prisma ether]

Please update your one click install .env file ( sibling to your docker-compose.yml )

And restart your containers

It's not editable on the panel. Is this normal?
Yes that's an, few next weeks, upcoming feature

[naive sand]

Forgive my ignorance, I'm still learning.

Would that be it, directly in docker-compose.yml?

[prisma ether]

That's all right

You should edit the .env file next to your docker-compose.yml
Then restart or even re-create your container, using docker GUI or docker-compose down && docker-compose up

[naive sand]

I did it as you said, but it still hasn't activated... :((

[prisma ether]

Sorry for the delay @naive sand !
You also need to bind the docker-compose entry to be consuming the .env entry
Such as

    environment:
      PG_DATABASE_URL: postgres://${PG_DATABASE_USER:-postgres}:${PG_DATABASE_PASSWORD:-postgres}@${PG_DATABASE_HOST:-db}:${PG_DATABASE_PORT:-5432}/default
      SERVER_URL: ${SERVER_URL}
      REDIS_URL: ${REDIS_URL:-redis://redis:6379}
      DISABLE_DB_MIGRATIONS: "true" # it already runs on the server

      STORAGE_TYPE: ${STORAGE_TYPE}
      STORAGE_S3_REGION: ${STORAGE_S3_REGION}
      STORAGE_S3_NAME: ${STORAGE_S3_NAME}
      STORAGE_S3_ENDPOINT: ${STORAGE_S3_ENDPOINT}

      APP_SECRET: ${APP_SECRET:-replace_me_with_a_random_string}

      IS_MULTIWORKSPACE_ENABLED: ${IS_MULTIWORKSPACE_ENABLED}

[urban star]

Is this solved yet?

[prisma ether]

Hello @urban star
Have you tried any of the above suggestions ?

[urban star]

Hi, actually I've already solved all the issues I had before in this post

[prisma ether]

Mhm nevermind I think @naive sand kinda hijacked this issue

[urban star]

Easiest way is to put 'IS_MULTIWORKSPACE_ENABLED: true` in docker-compose , under server and worker environment

[urban star]

I think this will work too

[naive sand]

done, but it didn't work.