starred/karakeep

Fork 0

mirror of https://github.com/karakeep-app/karakeep.git synced 2026-04-25 07:56:05 +03:00

[GH-ISSUE #766] Help! After installation, the user can't be registered when clicked. #500

New issue

Open

opened 2026-03-02 11:50:23 +03:00 by kerem · 4 comments

kerem commented

2026-03-02 11:50:23 +03:00

Owner

Originally created by @planet3x on GitHub (Dec 26, 2024).
Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/766

Describe the Bug

Help! After installation, the user can't be registered when clicked. The error message shows "no such table: user".

Steps to Reproduce

"no such table: user".

Expected Behaviour

What's the cause of this problem? And how can I solve it?

Screenshots or Additional Context

Device Details

Synology 918+

Exact Hoarder Version

v0.20.0

Originally created by @planet3x on GitHub (Dec 26, 2024). Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/766 ### Describe the Bug Help! After installation, the user can't be registered when clicked. The error message shows "no such table: user". ### Steps to Reproduce "no such table: user". ### Expected Behaviour What's the cause of this problem? And how can I solve it? ### Screenshots or Additional Context <img width="431" alt="PixPin_2024-12-26_21-19-05" src="https://github.com/user-attachments/assets/a7a04536-7ea3-4f4e-b5ad-244fbf7051bc" /> ### Device Details Synology 918+ ### Exact Hoarder Version v0.20.0

kerem added the

question

label

2026-03-02 11:50:23 +03:00

kerem commented

2026-03-02 11:50:24 +03:00

Author

Owner

@MohamedBassem commented on GitHub (Dec 26, 2024):

This means that the database migrations didn't run. Did you by any chance wipe the database (or change the data dir) after starting the container? Anyways, restarting the container should re run the database migration and should hopefully fix the issue

@MohamedBassem commented on GitHub (Dec 26, 2024): This means that the database migrations didn't run. Did you by any chance wipe the database (or change the data dir) after starting the container? Anyways, restarting the container should re run the database migration and should hopefully fix the issue

kerem commented

2026-03-02 11:50:24 +03:00

Author

Owner

@planet3x commented on GitHub (Dec 27, 2024):

Thank you for your reply. There might be something wrong with my network environment. Docker Compose didn't work successfully. I deployed it using Docker pull and it ran successfully, but then this issue occurred. I'm not quite sure about it. Could you please help me check what the reason is? Thank you.

@planet3x commented on GitHub (Dec 27, 2024): <img width="369" alt="PixPin_2024-12-27_10-15-12" src="https://github.com/user-attachments/assets/b868ff06-2b26-405f-b804-a8337fc49e12" /> <img width="446" alt="PixPin_2024-12-27_10-18-05" src="https://github.com/user-attachments/assets/fb9acc38-d18b-4456-8e82-57fbd1e6383c" /> Thank you for your reply. There might be something wrong with my network environment. Docker Compose didn't work successfully. I deployed it using Docker pull and it ran successfully, but then this issue occurred. I'm not quite sure about it. Could you please help me check what the reason is? Thank you.

kerem commented

2026-03-02 11:50:24 +03:00

Author

Owner

@MohamedBassem commented on GitHub (Dec 28, 2024):

Ah, if you didn't use the docker compose, then you're probably missing the DATA_DIR env. Add an env variable DATA_DIR=/data and restart the container. That should help.

@MohamedBassem commented on GitHub (Dec 28, 2024): Ah, if you didn't use the docker compose, then you're probably missing the `DATA_DIR` env. Add an env variable `DATA_DIR=/data` and restart the container. That should help.

kerem commented

2026-03-02 11:50:24 +03:00

Author

Owner

@MohamedBassem commented on GitHub (Dec 28, 2024):

Also, if you're using the hoarder image, don't set the USING_LEGACY_SEPARATE env.
Also, don't override SERVER_VERSION, the container defines it itself.

@MohamedBassem commented on GitHub (Dec 28, 2024): * Also, if you're using the `hoarder` image, don't set the `USING_LEGACY_SEPARATE` env. * Also, don't override `SERVER_VERSION`, the container defines it itself.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/karakeep#500

No description provided.

Rows
Columns