Hello @pnordmann An app update is available now to fix this issue.

My experience with ChatGPT has been.. spotty at best. I'm glad you figured it out!

yes that might be worth asking upstream at the app to maybe improve this UI for better usability and predictability.

Hi all, another iOs client for Vikunja, also supports off-line mode: https://marco308.github.io/mdone/ https://community.vikunja.io/t/mdone-a-native-ios-and-macos-app-for-vikunja/4548

The manual fix worked for me. I ran the following in the web terminal (repair mode): psql $CLOUDRON_POSTGRESQL_URL ALTER TABLE webhooks ADD COLUMN IF NOT EXISTS project_id bigint NULL; INSERT INTO migration (id) VALUES ('20260224215050'); \q After restarting the app, migrations ran successfully and Vikunja 2.2.0 is up and running. Thanks for the help!

@james Thanks for the quick fix. I can confirm it's working now on Windows desktop v.2.1.0.

Hello @bytepartner Please see: https://docs.cloudron.io/packages/vikunja With the config file you can control e.g.: self-registration (which is disabled by default when using the Cloudron user management). As far as I know, Vinkunja does not have Admin accounts, you will have to use the vinkunja cli => https://vikunja.io/docs/cli/ You can open the Web Terminal of your Vinkunja Cloudron app and just do e.g.: vikunja user create --help Create a new user. Usage: vikunja user create [flags] Flags: -a, --avatar-provider string The avatar provider of the new user. Optional. -e, --email string The email address of the new user. -h, --help help for create -p, --password string The password of the new user. You will be asked to enter it if not provided through the flag. -u, --username string The username of the new user.

Hello @archos Don't delete the "old" app until your new app is fully migrated and confirmed working. Install a new @vikunja app under a different location and in this new app, restore from a backup of your production @vikunja. Old backups are not cleaned up immediately but will be cleaned up according to your retention policy.

@james Thanks for explaining how to package how own version, that's really good to know in general! @shrey Just to say, I don't think the dev doesn't favour stable versions. Most versions are stable on the repo, it's just that there is major update coming (v1.0) and so they've released a few RC before release it stable, but that's pretty standard practice.

The new app package has the default folder set to /app/data so the cli now works out of the box

Love it! Solved for me

thanks, https://git.cloudron.io/packages/vikunja-app/-/merge_requests/16

Yeah I agree, the UI could be improved a bit in the app.

@joseph said in issue with update to 1.6.6?: @uwcrbc said in issue with update to 1.6.6?: I am also wondering why the logs are showing a time that is neither the one set in the Cloudron server settings nor the one from the server. Cloudron server time is always UTC. This timezone is an implementation detail but it's easier if all logs and db fields are in standard time. Cloudron Time zone is used for cron job schedules (https://docs.cloudron.io/settings/#timezone) The times you see in the UI like the logs, eventlog are from the browser timezone . So.. I guess your browser is in UTC+1 ? This also makes sense - I have a fairly locked down browser security wise, which explains the difference between local time and the time displayed in the browser. I will try to remember this. Many thanks again @joseph

Should be fixed with latest package now.

this should be fixed with the latest package now.

@BetterWP awesome, thanks for updating with the solution!

Haven't tried this but have asked @vladimir-d to take a look.

This may be related to default timezone and language settings for users created with the previous package version containing a broken setting. Latest package is fixed, but unfortunately those users already created with the broken package version have to be recreated.