T
Twentyβ€’2d ago
Caspersonn

Missing Admin panel v0.50.3

Hey there. As title states our admin panel is missing when upgrading to v0.50.3. Our database exsists since v0.12.0 and we have had a lot of issues since then. This issue is still going on https://discord.com/channels/1130383047699738754/1348588157662138421. Some extra info: Running in docker containers with Nixos modules Current twenty version v0.50.3 Nixos version 24.11 Postgres version 16.8 So my question is. What is the best solution to our situation? And is there a possibility we could fix our database?
No description
17 Replies
Caspersonn
CaspersonnOPβ€’2d ago
No description
Prastoin
Prastoinβ€’2d ago
Hello @Caspersonn, please double check your user has admin settings and impersonate access in db Seems like you missed an actor composite field type migration But unless I'm mistaken can't see a link between this errors and not having the admin panel displayed Have you upgraded minor by minor ? createdBy source and createdbyContext is a migration made either in 0.42 or 0.43 @Caspersonn when would you be available for a call today ?
Caspersonn
CaspersonnOPβ€’2d ago
Hey @Prastoin. My user has access in Database with admin rights. Are these migration commands documented somewhere? I have upgrade my version minor by minor but some upgrade had issues and to run the commands twice after a docker restart. I made backups for version v0.35.0 until v0.41.0, so i will probably try again today from version v0.41.0. Sure πŸ™ƒ
Prastoin
Prastoinβ€’2d ago
Are these migration commands documented somewhere?
Yes here https://twenty.com/developers/section/self-hosting/upgrade-guide I think that's the best way let me know if you encounter any blocking point upgrading from your backup
Caspersonn
CaspersonnOPβ€’2d ago
Yeah. I used those commands to upgrade, right i am trying again maybe i made a user error. I'l let you know if it worked!
Prastoin
Prastoinβ€’2d ago
Sounds good !
Caspersonn
CaspersonnOPβ€’2d ago
Okay @Prastoin. I encounterd my first issue when upgrading from v0.40.3 to v0.41.5. Most times i run both upgrade commands and restart and run them again. But is that the correct way?
No description
Prastoin
Prastoinβ€’2d ago
Why would you run them twice ?
Caspersonn
CaspersonnOPβ€’2d ago
Like this:
docker exec -it twenty-worker yarn command:prod upgrade-0.41
docker exec -it twenty-worker yarn database:migrate:prod

systemctl restart docker-twenty-worker.service docker-twenty.service docker-redis.service

docker exec -it twenty-worker yarn command:prod upgrade-0.41
docker exec -it twenty-worker yarn database:migrate:prod
docker exec -it twenty-worker yarn command:prod upgrade-0.41
docker exec -it twenty-worker yarn database:migrate:prod

systemctl restart docker-twenty-worker.service docker-twenty.service docker-redis.service

docker exec -it twenty-worker yarn command:prod upgrade-0.41
docker exec -it twenty-worker yarn database:migrate:prod
Don't know. It thought it would build the tables and such
Prastoin
Prastoinβ€’2d ago
I can't attest that those old commands are 100% idempotent tbh One should be enough Have you had any errors at the very first upgrade run ?
Caspersonn
CaspersonnOPβ€’2d ago
Yes
Prastoin
Prastoinβ€’2d ago
The ones in the screenshot ?
Caspersonn
CaspersonnOPβ€’2d ago
Jep, exactly the same i think
Prastoin
Prastoinβ€’2d ago
I have to finish few things before, checking in an hour. Will have a look to mcmas command definition and also would be looking for hostname migration in anterior migration πŸ€”
Caspersonn
CaspersonnOPβ€’2d ago
Alright. I am open to call, if you prefer that? πŸ˜„
Prastoin
Prastoinβ€’2d ago
Yes lets setup a call for 4pm Paris TZ if you're also available, please let me know
Caspersonn
CaspersonnOPβ€’2d ago
Sure, that sounds good to me!

Did you find this page helpful?