Session expired immediately after logging in
When I log in, LedgerSMB 1.8 or higher immediately says my session has expired. What can I do to fix this?
Short answer: add the "--preload-app" flag to the Starman command line.
Long answer: As of LedgerSMB 1.8, session information is stored in an encrypted cookie. To make sure the encryption key is unique for every installation, a new encryption secret is being generated each time LedgerSMB is started. However, Starman (without the "--preload-app" flag) loads the application in each forked worker separately, leading to different encryption secrets in each worker with the indicated behaviour as a result.
- Read more about Session expired immediately after logging in
- Log in or register to post comments