"An Error Occurred" after logging in after update #5509

New Issue

OVERLORD · 2026-02-05T10:07:47+03:00

OVERLORD commented

2026-02-05 10:07:47 +03:00

Originally created by @2wenty1ne on GitHub (Nov 19, 2025).

Attempted Debugging

I have read the debugging page

Searched GitHub Issues

I have searched GitHub for the issue.

Describe the Scenario

I updated to BookStack v25.11.1.
Everything worked pretty well except that I can't log in anymore.
After entering my password and email, I get the An Error Occurred" screen.

Versions

My PHP version is up-to-date: PHP 8.2.29

Errors

Errors in Log Content below

Update process

I tried to follow the process documented in the admin doku.
After running composer install --no-dev, I got an error.
I have to admit I didn't read the whole error message, just one part which told me to run composer update, which I did.

composer update gave me the error that the PHP zip extension was missing. ("Yes, I know it said it in the doku, I wanted to follow it from top to bottom")

I installed the extension, ran composer update again, and it worked.
After that, I ran composer install --no-dev

I ran the PHP migration without problems and cleared the system.

The import and export worked after a restart.

Exact BookStack Version

v25.11.1

Log Content

In the console of the website, I get a `505 Internal Server Error` from the "POST http://bookstack-ip/login".   

In the `storage/logs/laravel.log`, I get the following errors:
`[2025-11-18 21:00:50] production.ERROR: This password does not use the Bcrypt algorithm. {"exception":"[object] (RuntimeException(code: 0): This password does not use the Bcrypt algorithm. at /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Hashing/BcryptHasher.php:88)`

followed by a 62-line stacktrace.

The following errors in `/var/log/apache2/error.log`:  
`[ssl:error] [pid 301:tid 301] AH02217: ssl_stapling_init_cert: can't retrieve issuer certificate!`  
`[pid 301:tid 301] AH02604: Unable to configure certificate localhost:443:0 for stapling`   

`/var/log/nginx/error.log` does not exist.

Hosting Environment

I installed BookStack via TurnKey in a Proxmox Container.

Debian GNU/Linux 12 (bookworm) with PHP 8.2.29

Originally created by @2wenty1ne on GitHub (Nov 19, 2025). ### Attempted Debugging - [x] I have read the debugging page ### Searched GitHub Issues - [x] I have searched GitHub for the issue. ### Describe the Scenario I updated to BookStack v25.11.1. Everything worked pretty well except that I can't log in anymore. After entering my password and email, I get the An Error Occurred" screen. ## Versions My PHP version is up-to-date: `PHP 8.2.29 ` ## Errors Errors in Log Content below ## Update process I tried to follow the process documented in the admin doku. After running `composer install --no-dev`, I got an error. I have to admit I didn't read the whole error message, just one part which told me to run `composer update`, which I did. `composer update` gave me the error that the PHP zip extension was missing. ("Yes, I know it said it in the doku, I wanted to follow it from top to bottom") I installed the extension, ran `composer update` again, and it worked. After that, I ran `composer install --no-dev` I ran the PHP migration without problems and cleared the system. The import and export worked after a restart. ### Exact BookStack Version v25.11.1 ### Log Content ```text In the console of the website, I get a `505 Internal Server Error` from the "POST http://bookstack-ip/login". In the `storage/logs/laravel.log`, I get the following errors: `[2025-11-18 21:00:50] production.ERROR: This password does not use the Bcrypt algorithm. {"exception":"[object] (RuntimeException(code: 0): This password does not use the Bcrypt algorithm. at /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Hashing/BcryptHasher.php:88)` followed by a 62-line stacktrace. The following errors in `/var/log/apache2/error.log`: `[ssl:error] [pid 301:tid 301] AH02217: ssl_stapling_init_cert: can't retrieve issuer certificate!` `[pid 301:tid 301] AH02604: Unable to configure certificate localhost:443:0 for stapling` `/var/log/nginx/error.log` does not exist. ``` ### Hosting Environment I installed BookStack via TurnKey in a Proxmox Container. Debian GNU/Linux 12 (bookworm) with PHP 8.2.29

OVERLORD added the 🐕 Support label 2026-02-05 10:07:47 +03:00

OVERLORD commented

2026-02-05 10:07:49 +03:00

@ssddanbrown commented on GitHub (Nov 19, 2025):

Hi @2wenty1ne,

The import and export worked after a restart.

So did you perform some kind of import and export as part of this update process?
The error logged generally reflects an issue with the format of the user password, so trying to understand if there was opportunity for the database data to become affected as part of your update process here.

@ssddanbrown commented on GitHub (Nov 19, 2025): Hi @2wenty1ne, > The import and export worked after a restart. So did you perform some kind of import and export as part of this update process? The error logged generally reflects an issue with the format of the user password, so trying to understand if there was opportunity for the database data to become affected as part of your update process here.

OVERLORD commented

2026-02-05 10:07:50 +03:00

@2wenty1ne commented on GitHub (Nov 19, 2025):

No, the import and export was the reason I performed the updated and I wanted to tell that the update worked.

I'm pretty sure the password is the same, I have it in my password manager and always filled it in. It worked like this before the update.

I don't know if the data could be affected. I did what I described. I have a backup of the proxmox container from before the update, can I export the password or other data from it?
I also have the cookie on my workstation and can still use bookstack, I will setup a new Admin user before the cookie dies.

@2wenty1ne commented on GitHub (Nov 19, 2025): No, the import and export was the reason I performed the updated and I wanted to tell that the update worked. I'm pretty sure the password is the same, I have it in my password manager and always filled it in. It worked like this before the update. I don't know if the data could be affected. I did what I described. I have a backup of the proxmox container from before the update, can I export the password or other data from it? I also have the cookie on my workstation and can still use bookstack, I will setup a new Admin user before the cookie dies.

OVERLORD commented

2026-02-05 10:07:50 +03:00

@2wenty1ne commented on GitHub (Nov 21, 2025):

Hi again @ssddanbrown,

I was able to create a new admin account using the cookie and transfer ownership to the new one.

Is there a way to determine why this happened, how I can prevent it in the future, and whether more data is corrupted?

@2wenty1ne commented on GitHub (Nov 21, 2025): Hi again @ssddanbrown, I was able to create a new admin account using the cookie and transfer ownership to the new one. Is there a way to determine why this happened, how I can prevent it in the future, and whether more data is corrupted?

OVERLORD referenced this issue

2026-02-05 10:34:12 +03:00

[PR #5509] [CLOSED] Separate permission to add/remove a book to/from a shelf #5427 #6510

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/BookStack#5509