Skip to end of metadata
Go to start of metadata

Perform a full system backup

BlueMind makes every effort to provide reliable updates. In some special untested cases or due to external factors, however, data may be lost unexpectedly. BlueMind may not be held responsible for any possible update failure leading to system corruption.

It is your responsibility to prevent this risk by performing a complete system backup.

Linux Upgrades

Major upgrades of Linux distributions (Debian 7 to Debian 8, etc.) must not be performed using automatic distribution update mechanisms (changing package sources and using the aptitude dist-upgrade command) because this may modify BlueMind dependencies which may impact BlueMind services.

To perform major distribution upgrades, please contact your integrator service provider or contact us via our ticket platform.

On this page:



New in 3.5.14: preparing for updates

From BlueMind 3.5.14, you must prepare for updates in the admin console (System Management > Update BlueMind) before you update packages with aptitude. This extra step is designed for administrators to update their system easily without updating BlueMind.

For more information, administrators should read 3.1 Preparing for updates below.


The BlueMind subscription provides a simplified, tried and tested update system.

Updating BlueMind to a corrective or adaptive version is made easier, safer and faster thanks to the graphical admin tool.

Major Upgrades: Migration

Major BlueMind upgrades (e.g. from v2.x to v3.x or from v3.0.x to v3.5.x) require software deposit addresses to be updated. The subscription file must therefore be updated for you to perform the version upgrade.

Do not perform such BlueMind upgrades at the same time as a major distribution update (e.g. Ubuntu 12.04 to Ubuntu 16.04). To perform major distribution upgrades, please contact your integrator service provider or contact us via our ticket platform.

For major upgrades, you must contact BlueMind to obtain a new subscription file.

To find out more, please go to our dedicated page: Migrating from BlueMind 3.0 to BlueMind 3.5.



To access BlueMind update tools, you must have a valid and current subcription installed.

Access to the setup wizard

Updates require access to the setup wizard (https://<>/setup) for which you were provided a password at the end of the post-installation process.

In case you lost this password, there are two ways of recovering it:

  1. Before any installation operation: Access the administration console as global administrator admin0 and go to System management > System configuration > "Reverse proxy" tab: enter the new password and save.
  2. Using command line in console mode:
    • Log into the BlueMind server as root and type the following command:

      rm -f /etc/nginx/sw.htpasswd; htpasswd -b -c /etc/nginx/sw.htpasswd admin admin
    • Log into the /setup URL using admin/admin as username/password
      This step is required even if you have not reached the update step yet.


Updates are available for any version officially supported by BlueMind.

Debian no longer supports Debian 7 Wheezy

To continue being able to use BlueMind updates with this distribution, you must update repository urls in the /etc/apt/sources.list file for:

deb wheezy main
deb wheezy-backports main

Repository signature 

Repositories are now signed for all supported Ubuntu/Debian distributions.

Repository signature is required for Ubuntu 18.04 and Debian 9 which are supported by BlueMind 3.5.9.

You may, if you need or want to, manually import the key on all our supported distributions using the following command:

curl | apt-key add -

Otherwise, a warning may come up during earlier version updates. This will not interfere with updates however.

Update instructions

Repositories are registered as soon as the subscription is installed, as a result, BlueMind will be updated automatically when the system is updated.

If you've made changes to configuration files manually, make sure you back them up.
To find out more, please refer to the Appendices: note on configuration files.

Preparing for the update

Updates from BlueMind version 3.5.14 or above must always be prompted. This gives you greater control over versions and reduces the risk of errors – the target version can now be left open to allow updates to the latest published version or, on the contrary, it can be frozen to prevent unintentional updates. This also helps ensure that the server's major version is conformed to and consistent with the installation of additional packages – which will be installed in the server version.

This can be done in the admin console:

  • Go to System Management > Update BlueMind
  • Click "Setup": the latest available version will be installed.

Update procedure

The BlueMind update procedure begins with an update of the packages on all the installation's servers using the commands already used for installation. Steps 1 and 2 therefore must be applied to all the machines concerned. Then, the update itself will have to be played just once, by logging in to the /setup url:

Advanced administrators can perform update operations in command line using the bm-cli tool.

To find out more, please refer to the page CLI admin client.

  1. Log in as root on each platform server
  2. Update the packages on each 

    If you want to minimize service downtime, you can pass the update command with the "download-only" option, which enables you to download all the packages ahead of the update.

    This does not interrupt or slow down services, which means it can be done at any time of day or night.

    You can then run the "upgrade" command at a more convenient time and therefore reduce service downtime.

    Debian/Ubuntu Redhat/CentOS

    Repeat these commands on each platform server.

    You may get a warning message about repository signature during earlier version updates. This does not disrupt the update process, it is a mere warning. To remedy this issue, please refer to 2.3.c: Repository signature above.

  3. In your web browser, go to the setup wizard https://<>/setup:

    Note: this step requires the setup wizard's password - see paragraph 2.2 above.

  4. Click "Update" to start the automatic update process.
  5. Once this is done, a message informs you that configuration was successful:
    BlueMind is then available at its usual url.

In the event of a problem, errors are logged into the bm-core and bm-tomcat files.


About configuration files

The postfix configuration is overwritten during the installation phase only. From then on, this configuration is updated using the command postconf.
Configuration files can be configured as desired, with the following restrictions:

  • deleting BlueMind maps: maps can however be added.
  • editing mynetwork: mynetwork must be edited in the admin console.
  • editing relayhost: relayhost must be edited in the admin console.
Concerning NGinx: the virtual host is overwritten with every update.
All VHosts are disabled during updates. Only BlueMind VHosts (bm-client-access and bm-webmail) are enabled again afterwards. Other virtual hosts may be enabled again, but this must be done as part of the update process, in addition to and to complete the BlueMind update process.
BlueMind's virtual host can also be extended through the /etc/nginx/bm-local.d/*.conf files.
  • No labels


  1. Concernant la signature des dépôts, il n'est pas indiqué comment faire en Debian 8.

    Car la commandep our récupérer les certificats ne fonctionne pas.

    curl | apt-key add -
      % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                     Dload  Upload   Total   Spent    Left  Speed
      0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0curl: (60) SSL certificate problem: certificate has expired
    More details here:

    curl performs SSL certificate verification by default, using a "bundle"
     of Certificate Authority (CA) public keys (CA certs). If the default
     bundle file isn't adequate, you can specify an alternate file
     using the --cacert option.
    If this HTTPS server uses a certificate signed by a CA represented in
     the bundle, the certificate verification probably failed due to a
     problem with the certificate (it might be expired, or the name might
     not match the domain name in the URL).
    If you'd like to turn off curl's verification of the certificate, use
     the -k (or --insecure) option.
    gpg: no valid OpenPGP data found.

  2. On peut bypasser avec l'option -k mais cela ne fonctionne pas de toute façon au niveau aptitude

  3. Solution :

    touch /etc/apt/apt.conf.d/99verify-peer.conf \ && echo "Acquire { https::Verify-Peer false }" >> /etc/apt/apt.conf.d/99verify-peer.conf