-
Notifications
You must be signed in to change notification settings - Fork 157
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
Error 500 by fresh installation (Docker/Postgres) #412
Comments
I faced similar problem as well... For example, the step 2: I am working to self-host it with Docker and traefik reverse proxy. |
If you ran into the same problem as me, you would see this as the first log entry:
The issue is that the entrypoint only runs the database setup if it's the creator of the database. See Line 78 in 4143013
However it doesn't grant the necessary permissions, and the setup code is a bit ... Well it could be better. How to get wallabag working with postgresThere's a flag So my environment looks like this now:
Then we start the container and wait for it to finish starting up, afterwards jump into a shell:
Now we can run the install script ourselves
Since we ran that as root, we have to fix the permissions (otherwise you will get some nasty session errors)
Then you should be able to hit your containers url or whatever you mapped it to and see My database wouldn't close the hanging connections, to force drop it the syntax is as follows: DROP DATABASE dbName WITH (FORCE) |
If you're using a version of Postgres after 15, you will get the following error:
To fix it, you need to grant permissions to the
|
Thanks for the pointers. I don't know why, but for me this doesn't really work. I believe the docker example assumes creation of that user etc. before, implicitly. I kinda expected it will just work. I am running inside a VM and connect to the docker-compose local postgres instance, therefore I don't mind the thing running under a super user, so do it like this:
however, this doesn't work out of the box either, initial migration doesn't spin up - tables are not being created, and after a fresh start, I see things like this int he DB:
I had to exec the initialization inside wallabag container via I was able to also get it working via creating the wallabag user, database, granting permissions etc., but it was more hassle for me. |
Hi there,
I've some difficulties installing Wallbag on my docker host. After "deployment", I get an error 500 by trying to connect to the URL.
Docker compose:
ENV file:
Logs when database already exists:
Logs when database doesn't exists:
Thing is, I have no tables in my database, despite wallbag user is owner of the database and I think "of course", this will result in the 500 error. api is available tough with the mentionned URL.
One thing: if I create the database after the initial start without, the logs will be exactly the same as above, so the DB is found. Remove root credentials doesn't help either.
Any clue where to start? Thx in advance! 😉
The text was updated successfully, but these errors were encountered: