Internal server error after upgrade from v0.18 to 0.23 #764

Closed
opened 2026-02-04 22:13:07 +03:00 by OVERLORD · 2 comments
Owner

Originally created by @haynes11 on GitHub (Aug 4, 2018).

Describe the bug
Upgraded to latest version (Albeit as a root user so permissions may be incorrect in terms of group but I have reset and they look normal. Internal server error

Steps To Reproduce
Steps to reproduce the behavior:

Upgrade to v 0.19 and after the upgrade completed I have an internal server error page. Nothing in the log file.

Your Configuration (please complete the following information):

  • Exact BookStack Version (Found in settings): v0.18 > v0.23 (Latest > Just followed update page as documented on your website)
  • PHP Version: PHP 7
  • Using Docker or reverse proxy (Yes/No): No

Additional context
Add any other context about the problem here.

This could be a file permissions problem/owner problem as I ran the upgrade as a different user. I have pretty much ruled this out though and it only happened after the upgrade

Originally created by @haynes11 on GitHub (Aug 4, 2018). **Describe the bug** Upgraded to latest version (Albeit as a root user so permissions may be incorrect in terms of group but I have reset and they look normal. Internal server error **Steps To Reproduce** Steps to reproduce the behavior: Upgrade to v 0.19 and after the upgrade completed I have an internal server error page. Nothing in the log file. **Your Configuration (please complete the following information):** - Exact BookStack Version (Found in settings): v0.18 > v0.23 (Latest > Just followed update page as documented on your website) - PHP Version: PHP 7 - Using Docker or reverse proxy (Yes/No): No **Additional context** Add any other context about the problem here. This could be a file permissions problem/owner problem as I ran the upgrade as a different user. I have pretty much ruled this out though and it only happened after the upgrade
OVERLORD added the 🐕 Support label 2026-02-04 22:13:07 +03:00
Author
Owner

@ssddanbrown commented on GitHub (Aug 4, 2018):

Hi @haynes11,
If you're seeing a plain 'Internal Server Error' then the error will likely be shown in your server's error logs.
Depending on OS, These are commonly found at /var/log/(apache2 or nignx)/error.log. Check the latest lines (tail -n 50 error.log) to see if there's an error in there when you try to access your instance.

@ssddanbrown commented on GitHub (Aug 4, 2018): Hi @haynes11, If you're seeing a plain 'Internal Server Error' then the error will likely be shown in your server's error logs. Depending on OS, These are commonly found at `/var/log/(apache2 or nignx)/error.log`. Check the latest lines (`tail -n 50 error.log`) to see if there's an error in there when you try to access your instance.
Author
Owner

@haynes11 commented on GitHub (Aug 4, 2018):

Hi @ssddanbrown 6AM after being up all night I really wasn't thinking clearly, so thank you for pointing that out! Now resolved! :)

@haynes11 commented on GitHub (Aug 4, 2018): Hi @ssddanbrown 6AM after being up all night I really wasn't thinking clearly, so thank you for pointing that out! Now resolved! :)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/BookStack#764