mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-02-05 00:29:48 +03:00
While working with multiple installations of BookStack on a one server in a one browser generates problems with multiple loggin session work #1780
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 @suvreal on GitHub (Jul 8, 2020).
Description
I have multiple installations of BookStack on one server and I need to maintain them as an administrator. But If I am logged to A installation I can't connect to the B one without any troubles.
If I am logged in installation A and try to log-in to installation B then I register the problem with connecting to the installation B (error 419 Page expired). After this attempt the login session in installation A is dropped while B log-in attempt while there is no set domain - APP_URL in .env (other conditions).
Domains I have set:
first installation - example.something.something
second installation - example.something.something/Ainstallation
third installation - example.something.something/Binstallation
Steps To Reproduce
Steps to reproduce the behavior:
You should have multiple BS installations on your server accessed by path of domains with same admin name/pass combination.
Expected behavior
There should be allowed multiple logged sessions for multiple bookstacks accesses.
Your Configuration (please complete the following information):
@ssddanbrown commented on GitHub (Jul 9, 2020):
Hi @suvreal,
In at least two of the instances could update your
.envfiles for those instances with the following option:Just so each have a unique
SESSION_COOKIE_NAMEvalue.I think you're having issues as, since all your instances are on the same domain, they're currently sharing the same cookie for sessions.
@suvreal commented on GitHub (Jul 10, 2020):
Thank you I will try it on Monday and give you appropriate feedback.
@suvreal commented on GitHub (Jul 13, 2020):
Mentioned solution was successful, thank you. Whereas this fix was successful this report ticket is maybe still not closed? I guess.
@ssddanbrown commented on GitHub (Jul 18, 2020):
Good to know it worked.
Will therefore close this.