-
Notifications
You must be signed in to change notification settings - Fork 258
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Undefined column" after upgrading linkding to v1.27.0 using postgres DB backend #682
Comments
Looks like the latest migrations were not run. Could you please share the Docker logs from starting a fresh container? It should contain something like this:
There might be some errors in that area. |
Something else to try would be to open a shell in the container and then run:
And then see what the output of that is. |
I had the same issue. My database migrations could not be executed because the
After adjusting the environment variable value it worked fine. |
Using linkding1.28.0 and postgres as database backend, I got such output:
|
Thanks for your effort on linkding, I love it!
After upgrading from v1.26.0 to v1.27.0, I only get HTTP 500 errors. As I'm using PostgreSQL as DB backend, I guess some columns are missing. Going back to v1.26.0 solved the issue temporarily. Here's an excerpt of the log:
The text was updated successfully, but these errors were encountered: