Suddenly get a 500 errors

[ZuluPilgrim]

Suddenly get a 500 errors

[ZuluPilgrim]

I am not sure what was happening. As I work in IT I know things generally don't break without someone doing something but I really don't remember making any changes and I have three other instances on other VMs running with no issue.

I felt there was something in the container that was off so I pulled it down, pruned all aspects from docker and repulled it from the source.

Everything is now up and running again.

Thanks for walking me through this all.

[ssddanbrown]

Hi @ZuluPilgrim, Looks like a common issue of the app not being able to access the database.

• Can you check the bookstack_app_data/www/.env file, and where possible confirm the values of any options starting with DB_.
• Do you remember ever changing any of the database options within the compose config after first boot/run of the stack?

[ZuluPilgrim]

@ssddanbrown thanks for getting back to me. I just tried doing some troubleshooting while away from home and now I van access the site.

I tried editing the document I was working on and all seemed to go well until I hit save as the page eventually returned an unknown error. I then tried logging off and back on again. I got to the MFA page but then it all wen pear-shaped again.

Here is what you asked for

# Database details
DB_HOST='bookstack_db'
DB_PORT='3306'
DB_DATABASE='bookstackapp'
DB_USERNAME='bookstack'
DB_PASSWORD='dbpassword'

Which are correct as I can now browse to the site again.

It looks like I am going to need to wait until the MFA starts working again. Tried incognito mode and that made no difference.

Actually the whole site is now becoming unresponsive again.

I might wait until it is up again and then pull all the docs our and stand up a new instance.

Just got: 504 Gateway Time-out

VM has heaps of disk space and memory.

Also other docker containers are running fine on this VM.

Should I try upgrading to the latest Bookstack? If so, do I just remove existing container and then re-run docker compose as it stands?

[ssddanbrown]

Okay, I'm a little confused on the state of things now and what's been changed so I'll put out some options:

Original Database Connection Error

If this was the issue things should not be intermittently working unless there's also a networking issue between containers or something like that.

The original error you had appeared to be a connection error to the database. Based on the details provided, it looks like there's been a database password change at some time since the .env file DB_PASSWORD does not align with the compose DB_PASS option. On both the database and app container, the password options can be a bit "sticky" (and don't act upon changes) so it's best to leave these as the original value (which I'd guess is dbpassword unless the env has been manually changed since initial run).

"An error has occurred" message

If you see a "An error has occurred" message, with a BookStack-style header bar still showing, this is an app-level error so should be logged to the app error log, found at bookstack_app_data/www/laravel.log. Find the latest messages for that which have a timestamp that align with when you got the error to show, then share back the error.

504 Gateway Time-out

Generally indicates a webserver/proxy level issue. Check the bookstack_app_data/log/nginx/error.log file for more details. If nothings there, check the logs for any proxy layers involved if you have any.

---

Should I try upgrading to the latest Bookstack?

IMO that risks just throwing more variables into the picture, think it'd be rare to be something based on the particular version of image you're using.