mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-02-09 11:19:38 +03:00
Cannot Login - explode(): Passing null to parameter #2 ($string) for saml2 in config file (but never used it!) #3899
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @sebzan on GitHub (Jul 4, 2023).
Describe the Bug
When accessing my Bookstack app on my Synology suddenly an error message shows up about "explode(): Passing null to parameter #2 ($string)" in Config file Bookstack.
I can see the login page but when I try to login I come to an error page.
Funny thing is that I´m not even using saml2 in any way, newer have!
I can see in Portainer that there have been an update at "2023-07-03 09:03:24" (local time) for the image - and the application worked the day before yesterday....
I'm using the latest image, solidnerd image.
Steps to Reproduce
Expected Behaviour
Screenshots or Additional Context
/var/www/bookstack/app/Config/saml2.php
on line 17_
Browser Details
Latest chromeversion on Windows 10 (latest)
Exact BookStack Version
23.6.0
PHP Version
8.2.7
Hosting Environment
Im running Bookstack via Docker on my Synology station.
Synology OS: DSM 7.2-64570 Update 1
Synology model: DS720+
RAM: 10 GB
Docker version: Latest, "Container Manager"
@ssddanbrown commented on GitHub (Jul 4, 2023):
Hi @sebzan,
You have not stated which docker image you're using, but I'm assuming the solidnerd image?
If so, please try updating the image in use as they patched this issue yesterday.
@sebzan commented on GitHub (Jul 4, 2023):
Hi,
Sorry, updated the bugreport now, using the latest image...
BR Zeb
@ssddanbrown commented on GitHub (Jul 4, 2023):
@sebzan Can I confirm the method you're using to check you're using the latest image?
@sebzan commented on GitHub (Jul 4, 2023):
In portainer it looks like this:
I´ve also recreated the container for bookstack just now via Portainer and pulled the latest image and that did not work either.
@ssddanbrown commented on GitHub (Jul 4, 2023):
Okay, thanks @sebzan for confirming.
If you use
solidnerd/bookstack:23.6.0-1instead ofsolidnerd/bookstack:latestthat should get you to the patched version.Looks like their patched container image isn't tagged to
latest, which I've raised with the solidnerd container team.@sebzan commented on GitHub (Jul 4, 2023):
Okay @ssddanbrown;
I´ll try to edit the image version in portainer and the pull that image down... Will get back.
@sebzan commented on GitHub (Jul 4, 2023):
@ssddanbrown:
[First exuse me for my lacking skills on container as such. I´ve installed the bookstack app as a "stack" via Portainer following a post from "Marius hosting"].
I´m trying to change the image version as you mentioned above in portainer but I really seems to miss something because where i´m filling in the new image version in "Container> Bookstack> Container details and Create image" nothing happends after updating. And of course I´m a bit carefule since I have a lot of doumentation in the app. (db). :)
Where do I actually change from using the ":latest (not latest) image version to the one you mention without messing up the DB after puling down and creating a new image?
@ssddanbrown commented on GitHub (Jul 4, 2023):
@sebzan Unfortunately I'm not familiar with portainer at all.
I was kind of hoping you'd just be able to change the
imageform field you had in your screenshot above.Go careful though! Ideally make sure you have backups of docker volumes in use, and/or backups/snapshots of the entire host system if possible.
@sebzan commented on GitHub (Jul 4, 2023):
@ssddanbrown: I´ll will do a more exact check later on today and then might have a go agian. :)
But, If the latest released version (solidnerd/bookstack:23.6.0-1) is fixed, since it´s actually is a problem, then I don´t need to do anything more than just "pull down" the image again in portainer and viola. :) - So let´s hope your friends will fix it quickly. :)
@sebzan commented on GitHub (Jul 4, 2023):
@ssddanbrown:
Workaround fixed for the error in "the latest build" - everything is working again. :)
This bug can be closed.