Making Installation Work BS 5.1 with Docker on GCloud VM

[rsdancey]

I am trying to install BlueSpice Free inside a Google Compute VM. I have acquired and assigned a static IP. I have created a DNS A record which points to that static IP; the DNS record has populated and the A record is pointing at the desired IP.

I access the VM via shell, and then follow the directions in the BlueSpice installation guide Step 1 Get the Stack.

I have created a .env file in the bluespice-deploy-main/compose directory

The .env file I have created looks exactly like the default file provided in the documentation except I have changed the edition to Free, configured the password sender and emergency contact to valid email addresses, changed the WIKI_HOST to my desired machine name, and configured the SMPT variables to use my mail server.

I left the DB_PASS value at “…”

I added LETSENCRYPT=true

running sudo ./bluespice-deploy up -d results in what appears to be a correctly installed BlueSpice installation. All the containers eventually show green checkmarks. There are several warnings about not having set the DB_ROOT_USER and DB_ROOT_PASS variables.

If I attempt to access the wiki by going to https://wiki.mydomain.com/BlueSpice first I get a 500 Internal Server error, followed by a page that says:

Sorry! This site is experiencing technical difficulties.

Try waiting a few minutes and reloading.

(Cannot access the database)

No amount of waiting resolves this issue.

Things I have tried:

Added DB_ROOT_USER and DB_ROOT_PASS entries
Provided a DB_PREFIX entry
set the various DB variables to entries of my choosing including DB_PASS (changed it from “…”)

No changes or different behavior of any kind; always fails in the same way

If access the container with docker exec -it bluespice-wiki-web sh and ping database I get valid ping data although the IP address is a range that is neither the internal IP provided by Google nor the static IP assigned to the virtual machine. (It’s a 172.18.0.X address)

The machine bluespice-database.bluespice_default is also pingable at the same ip address as database

[rsdancey]

I have narrowed what seems to be the problem down. I am trying to make a clean install to ensure that my .env changes are being correctly implemented.

./bluespice-deploy down
docker rmi $(docker images -a -q)

cd ~/
rm -r bluespice-deploy-main
rm main.zip

sudo shutdown -r now

// close ssh
// reopen ssh

wget https://github.com/hallowelt/bluespice-deploy/archive/refs/heads/main.zip
&& unzip main.zip
&& cd bluespice-deploy-main/compose

cp .env.sample .env

// change fields in .env:
// WIKI_PASSWORDSENDER to real email
// WIKI_EMERGENCYCONTACT to real email
// WIKI_HOST to real host name
// SMTP values to real values
// LETSENCRYPT=true

./bluespice-deploy up -d

// the system pulls all the containers
// the system creates/starts all the containers
// all succeed, green checkmarks except bluespice-search which fails after waiting for 60s

docker exec -it bluespice-database sh
mariadb
SHOW DATABASES;

+--------------------+
| Database |
+--------------------+
| information_schema |
| mysql |
| performance_schema |
| sys |
+--------------------+

There's no bluespice database

[rsdancey]

Minor Warning: There's a non-critical nginx warning about a conflicting server name on port 9090, but this doesn't prevent the container from functioning.

[rsdancey]

In the script /app/bin/init-database this line gates the setup of the database:

if ( !$dbRootUser || !$dbRootPass ) {
// If no root user is set, we can't create a database or set permissions
exit( 0 );
}

If the DB_ROOT_PASS value in .env is a blank, this gate will cause the script to exit

Setting an arbitrary password in .env results in the script failing:

Initializing database 'bluespice' on database ...
FAILED
SQLSTATE[HY000] [1045] Access denied for user 'root'@'bluespice-wiki-web.bluespice_default' (using password: YES)
User: root
Pass: t...t
Host: database

[rsdancey]

I logged into the database container, accessed mariadb, created two users and gave rights to the two users:

CREATE USER 'username'@'localhost' IDENTIFIED BY 'password' PASSWORD EXPIRE NEVER;

GRANT ALL PRIVILEGES ON *.* TO 'username'@'localhost' WITH GRANT OPTION;

CREATE USER 'username'@'%' IDENTIFIED BY 'password' PASSWORD EXPIRE NEVER;

GRANT ALL PRIVILEGES ON *.* TO 'username'@'%' WITH GRANT OPTION;

FLUSH PRIVILEGES;

I modified .env to make DB_USER equal to 'username' and DB_PASS equal to 'password'
I set DB_ROOT_USER = $DB_USER and DB_ROOT_PASS=$DB_PASS

then I took the containers down, and then brought them back up

my installation continued to have issues with the bluespice specific database tables so I ran this command:

docker exec bluespice-wiki-web php /app/bluespice/w/maintenance/update.php --quick

SUCCESS! My wiki has begun working!

[Tux1178]

I have followed these instructions (https://en.wiki.bluespice.com/wiki/Setup:Installation_Guide/Docker) and get the same error message.

Any news on that issue?