Aurora Corporate documentation

Installing on Debian / Ubuntu Linux


Aurora Corporate can be automatically installed and configured on Ubuntu Linux, Debian Linux or any compatible Linux distribution.

It was tested on: Ubuntu 20.04 - 23.10, Debian 11 and 12. It should also work on Linux Mint as well as other compatible flavors of Linux, as long as those provide the following dependencies: Apache 2, PHP 7.4 or newer, MySQL 5.7.8 or newer / MariaDB 10.2.7 or newer, with mysqlnd driver.

In case if any components are not detected on the system, they will be automatically deployed from OS repository as dependencies.

NB: This package uses Apache webserver. Check this page if you wish to use Nginx instead.

By default, the package assumes PHP is used as Apache module. But if the system is already configured for PHP-FPM, this case is automatically supported as well.

Configuring repository access

To have the product installed, add the following line to /etc/apt/sources.list file:

deb /

All the commands mentioned below must be run with superuser privileges. If you’re logged in as regular user, use su command on Debian or sudo su on Ubuntu to get full privileges. In case of Ubuntu, you can add sudo in front of a single command to get superuser privileges temporarily.

Install public key of our repository using the following commands:


curl -s | sudo gpg --no-default-keyring --keyring gnupg-ring:/etc/apt/trusted.gpg.d/afterlogic.gpg --import
chmod 644 /etc/apt/trusted.gpg.d/afterlogic.gpg


apt install gpg
curl -s | gpg --no-default-keyring --keyring gnupg-ring:/etc/apt/trusted.gpg.d/afterlogic.gpg --import
chmod 644 /etc/apt/trusted.gpg.d/afterlogic.gpg

Alternately, you can use a single legacy command (deprecated in newer Debian/Ubuntu releases):

wget -qO - | apt-key add -

Update APT cache with:

apt update

Installing the package

To install the product package, run the following command:

apt install aurora-corporate

Once Aurora is installed, it can be accessed at address, or http://localhost/aurora-corporate/ for local access.

To configure the installation, you can log into /adminpanel/ as superadmin user, default password is empty.

The product itself resides under /usr/share/aurora-corporate directory. Webserver configuration file is found at /etc/aurora-corporate/apache.conf with /etc/apache2/conf-available/aurora-corporate.conf and /etc/apache2/conf-enabled/aurora-corporate.conf symlinks created for it.

Virtual host setup for SSL

Default Apache configuration for the package doesn't set a separate hostname, it only points to a subdirectory of the default host. So if you have pointing to the server, you would need to enable SSL for that domain and its hostname, not for Aurora Corporate itself.

Another option is to create a separate entry under /etc/apache2/sites-available directory, copy /etc/aurora-corporate/apache.conf file to /etc/apache2/sites-available/aurora.conf, remove Alias line from it and surround the rest as follows:

<VirtualHost *:80>
        DocumentRoot /usr/share/aurora-corporate
        ErrorLog ${APACHE_LOG_DIR}/aurora.somedomain.error.log
        LogLevel warn
        CustomLog ${APACHE_LOG_DIR}/aurora.somedomain.access.log combined

Disable the default aurora-corporate.conf setup and enable the above configuration:

a2disconf aurora-corporate
a2ensite aurora.somedomain
service apache2 restart

Make sure Aurora Corporate can be accessed at and then proceed with setting up SSL for the installation, e.g. via Certbot:

certbot -d

Upgrading the product installation

The product is upgraded in the standard way using APT repository. If you wish to check whether there are updates for any of the packages you have installed, run the following:

apt update
apt upgrade

Or do that specifically for Aurora Corporate package:

apt update
apt install aurora-corporate

If new version is available, it will be installed, preserving the product configuration.


NB: Starting from 8.3.7, mod_rewrite is enabled automatically for new installs but when upgrading the package you may still need to perform the below configuration manually.

In v8.3.5, CSRF protection was substantially revised and may require web server reconfiguration. We're now shipping .htaccess file to ensure authentication headers are sent through, but if you're getting Error 500, that may mean you have mod_rewrite disabled. To correct that, run the following as super user:

a2enmod rewrite
service apache2 restart

And if you receive "Cookies need to be updated. To continue, please click here or reload this page." message, make sure .htaccess file is actually read by the web server. Read more on this at CSRF protection documentation page.

Uninstalling the product

To uninstall Aurora Corporate completely, run:

apt purge aurora-corporate


If you encounter any issues, feel free to post reports at the Aurora Issue tracker.