T
Twenty2mo ago
MrT

Docker Compose Upgrade Instructions v.033.0 to latest

I am having issues upgrading from v0.33.0 to v0.35.0 or honestly v34. We use docker compose to host our Twenty Instance. The upgrade guide just says to change the tag, and it does download the new image but when I try to login it gives me an error that the workspace doesn't exist. Any help is appreciated.
14 Replies
Raph
Raph2mo ago
@MrT you'll need to update to each version separately. See: https://twenty.com/developers/section/self-hosting/upgrade-guide In otherwords, you won't be able to jump from v33 to v35. It's v33 to v34 (migrations/etc), then from v34 to v35 and so on... I hope that helps
MrT
MrTOP2mo ago
Hi Ralph, thanks for the response. So just to confirm, I first have to do the tag upgrade to the version. And then do the specific version to version upgrade second? That instructions on the link just says to update the tag, to me it’s heavily misleading 😅
ɃØĦɆᵾS
ɃØĦɆᵾS2mo ago
Yes, you have to upgrade version one by one, e.g. if you want to upgrade from 0.32.0 to 0.35.0, you have to upgrade from 0.32.0 to 0.33.0, then from 0.33.0 to 0.34.0 and from 0.34.0 to 0.35.0
MrT
MrTOP2mo ago
@ɃØĦɆᵾS , thank you. That makes sense. All I have done so far is updated the tag to v0.34.0 (i'm on 0.33.0) and now I am getting this error: Even though I don't have this in my .env file
No description
MrT
MrTOP2mo ago
any suggestions?
ɃØĦɆᵾS
ɃØĦɆᵾS2mo ago
What happens if you add those mentioned variables to .env file? E.g.
ACCESS_TOKEN_SECRET=random_string_1234
REFRESH_TOKEN_SECRET=random_string_1234
ACCESS_TOKEN_SECRET=random_string_1234
REFRESH_TOKEN_SECRET=random_string_1234
MrT
MrTOP2mo ago
even when these are set in the .env it still shows as an error not letting the server container to start
ɃØĦɆᵾS
ɃØĦɆᵾS2mo ago
Please delete this image or at least anonymize data
MrT
MrTOP2mo ago
it's going to be rolled back and regenerated this is my test machine
ɃØĦɆᵾS
ɃØĦɆᵾS2mo ago
Let me check if there were any reported issues with that
ɃØĦɆᵾS
ɃØĦɆᵾS2mo ago
From what I see, there are no reported issues similar to yours, although there's one related to upgrading Twenty from 0.33.0 to 0.34.0 https://github.com/twentyhq/twenty/issues/9041
GitHub
Updated to 0.34 and now cannot login - "You're not member of this w...
Bug Description I updated my instance of twenty 0.33.0 to 0.34.0 and then i cannot login... i used to Example: When trying to login, it say this error "You're not member of this workspace....
MrT
MrTOP2mo ago
Thank you. I will look at this and get back to you
Raph
Raph2mo ago
@MrT if you see the upgrade doc you'll see that a new app secret was added. I also ran into a similar issue on #9041 that @bob posted above. In the comments of the issue I explain how I fixed my install.
lucas lima
lucas lima2mo ago
@ɃØĦɆᵾS Heu bob how are yout ? good? Could yuo show to us the process to upgrade into swarm or compose, like, what comands have to be set during this? example: yarn database:migrate:prod yarn command:prod workspace:sync-metadata -f yarn command:prod upgrade-0.XX in this order? these three on server service? thanks and have a happy new year

Did you find this page helpful?