Broken app after trying to upgrade

[StoffelCPR]

Hey,

I was last running on version 4.2 and tried to upgrade. I followed your guide and upgraded to v4.4.3 that worker fine.

I then upgraded to the latest 5.X version and am now stuck. I tried upgrading further to see if that resolves problems but it doesn't.

This is what the page shows.. Logging out doesn't work. I believe it's broken right now because I've migrations of the newer version before I rolled back.

ryot     | [backend] 2024-10-10T21:16:45.500728Z  INFO ryot: Running version: 5.5.6
ryot     | [proxy] {"level":"info","ts":1728595005.5262313,"msg":"using provided configuration","config_file":"/etc/caddy/Caddyfile","config_adapter":""}
ryot     | [proxy] {"level":"warn","ts":1728595005.5276299,"logger":"admin","msg":"admin endpoint disabled"}
ryot     | [proxy] {"level":"warn","ts":1728595005.5277565,"logger":"http.auto_https","msg":"automatic HTTPS is completely disabled for server","server_name":"srv0"}
ryot     | [proxy] {"level":"info","ts":1728595005.527907,"logger":"tls.cache.maintenance","msg":"started background certificate maintenance","cache":"0xc0003f0880"}
ryot     | [proxy] {"level":"info","ts":1728595005.5284219,"logger":"http.log","msg":"server running","name":"srv0","protocols":["h1","h2","h3"]}
ryot     | [proxy] {"level":"info","ts":1728595005.5285854,"msg":"autosaved config (load with --resume flag)","file":"/home/ryot/.config/caddy/autosave.json"}
ryot     | [proxy] {"level":"info","ts":1728595005.528595,"msg":"serving initial configuration"}
ryot     | [proxy] {"level":"info","ts":1728595005.5287166,"logger":"tls","msg":"cleaning storage unit","description":"FileStorage:/home/ryot/.local/share/caddy"}
ryot     | [proxy] {"level":"info","ts":1728595005.5287488,"logger":"tls","msg":"finished cleaning storage units"}
ryot     | [backend] 2024-10-10T21:16:45.556941Z  INFO sea_orm_migration::migrator: Applying all pending migrations
ryot     | [backend] 2024-10-10T21:16:45.560058Z  INFO sea_orm_migration::migrator: Applying migration 'm20240415_is_v5_migration'
ryot     | [backend] 2024-10-10T21:16:45.560090Z  INFO sea_orm_migration::migrator: Migration 'm20240415_is_v5_migration' has been applied
ryot     | [backend] 2024-10-10T21:16:45.560628Z  INFO sea_orm_migration::migrator: Applying migration 'm20240416_change_json_to_generic_json'
ryot     | [backend] 2024-10-10T21:16:45.575220Z  INFO sea_orm_migration::migrator: Migration 'm20240416_change_json_to_generic_json' has been applied
ryot     | [backend] 2024-10-10T21:16:45.575465Z  INFO sea_orm_migration::migrator: Applying migration 'm20240425_add_created_by_user_id_column_to_execise'
ryot     | [backend] 2024-10-10T21:16:45.611640Z  INFO sea_orm_migration::migrator: Migration 'm20240425_add_created_by_user_id_column_to_execise' has been applied
ryot     | [backend] 2024-10-10T21:16:45.611858Z  INFO sea_orm_migration::migrator: Applying migration 'm20240503_update_user_to_entity_to_recalculate'
ryot     | [backend] 2024-10-10T21:16:45.614153Z  INFO sea_orm_migration::migrator: Migration 'm20240503_update_user_to_entity_to_recalculate' has been applied
ryot     | [backend] 2024-10-10T21:16:45.614360Z  INFO sea_orm_migration::migrator: Applying migration 'm20240504_add_columns_for_state_changes'
ryot-db  | 
ryot     | [backend] 2024-10-10T21:16:45.615617Z  INFO sea_orm_migration::migrator: Migration 'm20240504_add_columns_for_state_changes' has been applied
ryot     | [backend] 2024-10-10T21:16:45.615848Z  INFO sea_orm_migration::migrator: Applying migration 'm20240506_0_add_done_collection_for_existing_users'
ryot     | [backend] 2024-10-10T21:16:45.618228Z  INFO sea_orm_migration::migrator: Migration 'm20240506_0_add_done_collection_for_existing_users' has been applied
ryot     | [backend] 2024-10-10T21:16:45.618429Z  INFO sea_orm_migration::migrator: Applying migration 'm20240506_1_add_entities_to_done_collection_for_existing_users'
ryot     | [backend] 2024-10-10T21:16:45.693610Z  INFO sea_orm_migration::migrator: Migration 'm20240506_1_add_entities_to_done_collection_for_existing_users' has been applied
ryot     | [backend] 2024-10-10T21:16:45.693881Z  INFO sea_orm_migration::migrator: Applying migration 'm20240507_0_remove_visibility_from_collection'
ryot     | [backend] 2024-10-10T21:16:45.710935Z  INFO sea_orm_migration::migrator: Migration 'm20240507_0_remove_visibility_from_collection' has been applied
ryot     | [backend] 2024-10-10T21:16:45.711175Z  INFO sea_orm_migration::migrator: Applying migration 'm20240508_set_state_changes_to_null'
ryot-db  | PostgreSQL Database directory appears to contain a database; Skipping initialization
ryot-db  | 
ryot-db  | 2024-10-10 23:16:45.108 CEST [1] LOG:  starting PostgreSQL 16.4 on x86_64-pc-linux-musl, compiled by gcc (Alpine 13.2.1_git20240309) 13.2.1 20240309, 64-bit
ryot-db  | 2024-10-10 23:16:45.108 CEST [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
ryot-db  | 2024-10-10 23:16:45.108 CEST [1] LOG:  listening on IPv6 address "::", port 5432
ryot-db  | 2024-10-10 23:16:45.280 CEST [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
ryot-db  | 2024-10-10 23:16:45.348 CEST [29] LOG:  database system was shut down at 2024-10-10 23:16:34 CEST
ryot-db  | 2024-10-10 23:16:45.434 CEST [1] LOG:  database system is ready to accept connections
ryot     | [frontend] [remix-serve] http://localhost:3000 (http://172.20.0.3:3000)

That's my current log

[IgnisDa]

Can you try deleting all cookies? If that doesn't work, please send me a dump of your database.

[IgnisDa]

Closing due to inactivity. Feel free to ping me here.