Bludit CMS. Session initialization failed.
Posted: Fri May 28, 2021 3:28 am
I just installed Bludit using the official docker image.
I added volume mounts for bl-content, bl-plugins, and bl-theme so I can easily manage things.
I ran into a permissions issue on my first run of the installer which a lazily resolved by doing a chmod on the bl-content directory on the host machine.
The next run of the installer ended with a 'Please check your theme configuration in the admin panel. Check for an active theme.'
I was a bit confused since this was a 'fresh' docker install. So I tried to goto domain.tld:8000/admin and I got the "Bludit CMS. Session initialization failed." message.
I tried to check the logs in the docker container but they get sent to /dev/stdout and /dev/stderr. So no logs to see what's going on.
I tried to chmod 777 for all of bl-content but that didn't help.
I read an old post about permissions for /var/lib/php/sessions but the docker container does not have a php/ directory in /var/lib.
I'm not sure where to go from here. Maybe bl-content can't live outside of the container, but that doesn't make much sense....
I added volume mounts for bl-content, bl-plugins, and bl-theme so I can easily manage things.
I ran into a permissions issue on my first run of the installer which a lazily resolved by doing a chmod on the bl-content directory on the host machine.
The next run of the installer ended with a 'Please check your theme configuration in the admin panel. Check for an active theme.'
I was a bit confused since this was a 'fresh' docker install. So I tried to goto domain.tld:8000/admin and I got the "Bludit CMS. Session initialization failed." message.
I tried to check the logs in the docker container but they get sent to /dev/stdout and /dev/stderr. So no logs to see what's going on.
I tried to chmod 777 for all of bl-content but that didn't help.
I read an old post about permissions for /var/lib/php/sessions but the docker container does not have a php/ directory in /var/lib.
I'm not sure where to go from here. Maybe bl-content can't live outside of the container, but that doesn't make much sense....