BS 5.1: nginx only shows 404 after installation

Configuration/Setup
1

Hi,

I guess I correctly followed the Docker installation instruction.

including the installation of the SSL certificate & key.

When I now enter https://HOSTNAME , nginx’s answer is “404”. Same for https://HOSTNAME/w/

I assume, that the only configuration file that I should touch, is .env

Then I found /data/bluespice/wiki/bluespice/log/install-20251222….log. According to this file, neither git, nor diff3 could be found.

whereis git
git: /usr/bin/git
whereis diff3
diff3: /usr/bin/diff3

The same file tells me, that the server name is “localhost”, the server url is “localhost/w” and that it cannot connect to MYSQL on localhost - I can connect, with the credentials from .env.

It seems that the de deployment isn’t running as it should. If it is my fault, that what am I doing wrong?

Thanks for any hint or suggestion,

Stefan

2

Hello Stefan,

the installation logs does not provide accurate information in this case - this can and should be improved in the future. The mentioned “localhost” name, db connection problem, missing git and diff can all be ignored, as it is the same for successfully installed instances as well.

There are several ways to tell whether this is only a network problem, or actually an installation problem of the wiki:

  1. Run ./bluespice-deploy exec -it database mariadb in the compose directory. Execute show databases; query, and one should see a database bluespice if the wiki installation is correct.
  2. Run ./bluespice-deploy logs -f wiki-task in the compose directory. One should see repeated messages popping out, without errors or exceptions. This indicates that the wiki installation is correct.
  3. Run ./bluespice-deploy exec -it proxy bash in the compose directory. Execute curl http://wiki-web:9090/wiki/, with a correctly installed wiki one should see a piece of html for wiki login.

If the wiki installation is correct, then it might be a problem of network connection. In your case, are you adding your domain name to your hosts file, or are you using an actual DNS service? If your web request is reaching the wiki-web container, you should see corresponding request messages in ./bluespice-deploy logs -f wiki-web. If you made changes to the compose/.env file, you would need to run ./bluespice-deploy down then ./bluespice-deploy up -d to take the changes into effect.

Indeed all you should prepare is .env and the certificates - if the problem you experienced persists until here, it would be helpful if you share an anonymized version of your .env file, so that we can further discuss and debug.

Thank you for your feedback, and hope that you can run your BlueSpice Wiki soon!

Best wishes for the upcoming new year,
Hua