Errors after changing VIKUNJA_API_URL and VIKUNJA_SERVICE_FRONTENDURL (or restarting containers) #1502

New Issue

Olivetree · 2023-04-21T11:48:32Z

Olivetree commented

2023-04-21 11:48:32 +00:00

Description

I needed to change the domain where I host vikunja so I changed VIKUNJA_API_URL and VIKUNJA_SERVICE_FRONTENDURL and restarted the containers. After clearing cookies on my browser and trying to login, it says the user doesn't exist.
Also, if I run docker exec vikunja_api /app/vikunja/vikunja user list I get the following output:

2023/04/21 11:37:08 No config file found, using default or config from environment variables.
2023-04-21T11:37:08.349666637Z: INFO    ▶ migration/Migrate 04e Ran all migrations successfully.
2023-04-21T11:37:08.349987819Z: INFO    ▶ models/RegisterReminderCron 04f Mailer is disabled, not sending reminders per mail
2023-04-21T11:37:08.350137109Z: INFO    ▶ models/RegisterOverdueReminderCron 050 Mailer is disabled, not sending overdue per mail
2023-04-21T11:37:08.352993469Z: CRITICAL        ▶ cmd/func12 0ae Error getting users: pq: column "default_list_id" does not exist

Using psql on the db container I can see the users in the users table.

Finally, changing back the URLs and clearing cookies, vikunja still doesn't find the usernames. Password is given by password manager, it's very unlikely to be incorrect input.

Vikunja Frontend Version

0.20.5 (actually latest from dockerhub)

Vikunja API Version

v0.20.4

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

No response

### Description I needed to change the domain where I host vikunja so I changed VIKUNJA_API_URL and VIKUNJA_SERVICE_FRONTENDURL and restarted the containers. After clearing cookies on my browser and trying to login, it says the user doesn't exist. Also, if I run `docker exec vikunja_api /app/vikunja/vikunja user list` I get the following output: ``` 2023/04/21 11:37:08 No config file found, using default or config from environment variables. 2023-04-21T11:37:08.349666637Z: INFO ▶ migration/Migrate 04e Ran all migrations successfully. 2023-04-21T11:37:08.349987819Z: INFO ▶ models/RegisterReminderCron 04f Mailer is disabled, not sending reminders per mail 2023-04-21T11:37:08.350137109Z: INFO ▶ models/RegisterOverdueReminderCron 050 Mailer is disabled, not sending overdue per mail 2023-04-21T11:37:08.352993469Z: CRITICAL ▶ cmd/func12 0ae Error getting users: pq: column "default_list_id" does not exist ``` Using psql on the db container I can see the users in the users table. Finally, changing back the URLs and clearing cookies, vikunja still doesn't find the usernames. Password is given by password manager, it's very unlikely to be incorrect input. ### Vikunja Frontend Version 0.20.5 (actually latest from dockerhub) ### Vikunja API Version v0.20.4 ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots _No response_

Olivetree added the

kind/bug

label 2023-04-21 11:48:32 +00:00

konrad commented

2023-04-24 06:18:44 +00:00

Does the error only happen when you try to list users?

Did you update to unstable at some point? (Even if briefly)

Does the error only happen when you try to list users? Did you update to unstable at some point? (Even if briefly)

Olivetree commented

2023-04-24 09:55:48 +00:00

It also happens on create.

Oh! Now that you mention it, while trying to find some feature I saw mentioned on the forums, I did switch to unstable for some minutes. Everything works again. Thanks!

It also happens on create. Oh! Now that you mention it, while trying to find some feature I saw mentioned on the forums, I did switch to unstable for some minutes. Everything works again. Thanks!

Olivetree closed this issue

2023-04-24 09:55:48 +00:00

konrad commented

2023-04-24 10:49:54 +00:00

Yeah there have been breaking changes to the structure recently which are not backwards compatible.

konrad referenced this issue from a commit

2024-02-07 14:00:31 +00:00

chore(deps): update typescript-eslint monorepo to v5.11.0 (#1502)

Sign in to join this conversation.