Problem logging in after upgrade
I use the selfhosted docker version of twenty. I upgraded to the latest image 20h ago. And my former account that used to work is now outlocked
this is the message that I've got
15 Replies
I rolled back the versions to v0.42.18 and it worked to login. How is this rollover to RBAC tended to be implemented in a smooth way??
I believe you've found this error as you didn't update the database as there are no upgrade commands yet
On newest version I can confirm that this column exists in database thus when new version will be released and commands for upgrading the database schema will be presented, you probably won't find this error
Okey! Thanks! I will try the following route https://twenty.com/developers/section/self-hosting/upgrade-guide#(option-2)-database-migration
and see if I can make it work going from 0.42.18 to 0.43.x
Otherwise I will start a fresh install using postgres:16. I’m just playing around with twenty right now to build up customers needs for smb market and to build reports and analysis with Metabase based on data fetched from twenty’s great API’s
Are you sure it should be here?
Its dummy data only!! Just to show the playground in metabase 😉
It’s the data from the API’s but from my dev environment based on dummy data. I would never show real data
detected something in the documentation under option 2 when copying the dump-file. it should be this command docker cp twenty-db-1:/home/postgres/databases_backup.sql . instead of docker cp twenty-db-1:/databases_backup.sql .
In which place?
the last line
Could you create a PR with change?
I'm not that used to contribute through github, but if you tell me how I can do it. I'm used to github and git, but have never contributed to any group yet
Basically fork a repo, edit this file https://github.com/twentyhq/twenty/blob/main/packages%2Ftwenty-website%2Fsrc%2Fcontent%2Fdevelopers%2Fself-hosting%2Fupgrade-guide.mdx, commit changes and create a pull request with clear title and some context in description
PR #10608 is added now