-
-
Notifications
You must be signed in to change notification settings - Fork 109
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
500 Internal Server Error #212
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
Having the same issue, any progress? |
OP has used the incorrect port in their compose, as they're using docker networking, they should be using the container port 3306 and not the bridged port on 3307. |
I'm also having the same issue with the default yaml provided. I only altered the password for the database.
|
I have similar error: here my error in laravel.log:
the weird thing is: I could not find a hint about a failed migration? |
I was able to get past this issue by manually setting the mysql user password. It looks like the docker compose example in the readme doesn't correctly set the mysql_user's password.
|
Does your password contain the character |
sorry in my case false alarm, happened because watchtower messed something up and ran older version of bookstack app container. Which then make sence i no more compatible to the Database |
@aptalca it did not |
Then please post your password (change it in your system afterwards) so we can try and reproduce. Last I looked into it, we had sanitization in place for every special character and they all worked (with the exception of the |
I experienced the same issue. The solution in my case was to tear down the containers and bring them up again, which was enough to trigger the migrations to occur. I'm not sure why they didn't run the first time by themselves. |
I experienced the same issue, I updated MYSQL_PASSWORD and forgot to update DB_PASS (it is used by bookstack to connect to the DB), which seems to be the same case for your compose file. |
I had the same problem. It appears that the bookstack_db container can take too long to do its initialization which causes the bookstack container to fail. Perhaps the bookstack container needs to try longer before giving up. Two workarounds that worked for me:
|
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
Is there an existing issue for this?
Current Behavior
I used Docker-Compose to start Bookstack but got 500 error.
in /log/nginx/error.log I don't have any entries.
Expected Behavior
Open bookstack configuration home page
Steps To Reproduce
use docker-compose file, I have changed only file ports in docker hub
Environment
CPU architecture
x86-64
Docker creation
version: "3" services: bookstack: image: lscr.io/linuxserver/bookstack container_name: bookstack environment: - PUID=1000 - PGID=1000 - APP_URL=https://bookstack.mydomain.com - DB_HOST=bookstack_db - DB_PORT=3307 - DB_USER=root - DB_PASS=secret - DB_DATABASE=bookstack volumes: - ./bookstack_app_data:/config ports: - 8080:80 restart: unless-stopped depends_on: - bookstack_db bookstack_db: image: lscr.io/linuxserver/mariadb container_name: bookstack_db environment: - PUID=1000 - PGID=1000 - MYSQL_ROOT_PASSWORD=password - TZ=America/Lima - MYSQL_DATABASE=bookstack - MYSQL_USER=bookstack - MYSQL_PASSWORD=password volumes: - ./bookstack_db_data:/config ports: - 3307:3306 restart: unless-stopped
Container logs
The text was updated successfully, but these errors were encountered: