--- title: "Installing Amplia on Rocky Linux" description: "Install an on-premises Amplia on Rocky Linux 8.x or greater, with prerequisites (licenses, DNS entries, database) and the ASP.NET Core Runtime 10.0." canonical: "https://docs.lacunasoftware.com/en-us/articles/amplia/on-premises/linux/install-rocky" locale: "en" product: "Amplia" last_updated: "2026-10-12" --- # Installing Amplia on Rocky Linux To install an [on-premises](https://docs.lacunasoftware.com/en-us/articles/amplia/on-premises) instance of [Amplia](https://docs.lacunasoftware.com/en-us/articles/amplia) on Rocky Linux, follow the steps below. For other platforms, [click here](https://docs.lacunasoftware.com/en-us/articles/amplia/on-premises). > **Tip** > > Before you start, make sure you have completed the steps outlined on [Planning before installation](https://docs.lacunasoftware.com/en-us/articles/amplia/on-premises#planning) ## Prerequisites * Rocky Linux 8.x or greater * **PKI SDK license** (in Base64 format) * **Web PKI license** (Base64/binary format) -- only needed if users will issue certificates on their computers (web issuing procedure) * **DNS entries** previously created for: * Dashboard access (see [Dashboard domain](https://docs.lacunasoftware.com/en-us/articles/amplia/on-premises#dashboard-domain)) * CRL publishing (see [Access domains](https://docs.lacunasoftware.com/en-us/articles/amplia/on-premises#access-domains)) * **Connection string** to a [previously created SQL Server or PostgreSQL database](https://docs.lacunasoftware.com/en-us/articles/amplia/on-premises/prepare-database) ## Install the ASP.NET Core Runtime 10.0 > **Info** > > These instructions assume you are logged in as **root**. If you are not, run `sudo su -` before continuing! Install the ASP.NET Core runtime package: ```sh yum install aspnetcore-runtime-10.0 ``` To test the installation, run: ```sh dotnet --list-runtimes ``` The expected output is similar to: ```text Microsoft.AspNetCore.App 10.0.* [*/dotnet/shared/Microsoft.AspNetCore.App] Microsoft.NETCore.App 10.0.* [*/dotnet/shared/Microsoft.NETCore.App] ``` > **Tip** > > For other operating system versions and alternative ways to install the ASP.NET Core Runtime, see [this page](https://docs.microsoft.com/en-us/dotnet/core/install/linux) ## Install Amplia Create a local user to run the Amplia server: ```sh mkdir /var/amplia useradd --system --home-dir /var/amplia amplia chown amplia:amplia /var/amplia ``` Create the site folder, download and extract the binaries: ```sh mkdir /usr/share/amplia curl -O https://cdn.lacunasoftware.com/amplia/amplia-5.0.0.tar.gz tar xzf amplia-5.0.0.tar.gz -C /usr/share/amplia chmod -R a=,u+rwX,go+rX /usr/share/amplia ``` > **Note** > > Site binaries can be read by any user and can only be changed by root users. This means that the application user (*amplia*) can read but not change the files, which is intentional. Create the configuration file from the given template: ```sh mkdir /etc/amplia cp /usr/share/amplia/config-templates/linux/appsettings.conf /etc/amplia/ chown -R root:amplia /etc/amplia chmod -R a=,u+rwX,g+rX /etc/amplia ``` > **Note** > > Configuration files can only be read by members of the *amplia* group and can only be changed by the root user. This is important to protect sensitive data stored on the configuration files from unauthorized access. ## Configure Amplia Edit the configuration file to configure your Amplia instance: ```sh nano /etc/amplia/appsettings.conf ``` On the `[General]` section, to fill the `EncryptionKey` setting generate a 256-bit key to encrypt sensitive data stored on the database: ```sh openssl rand -base64 32 ``` Also on the `[General]` section, to fill the `RootPasswordHash` setting choose a strong password for root access to the dashboard and hash it: ```sh dotnet /usr/share/amplia/Lacuna.Amplia.Site.dll -- hash-root-pass ``` > **Note** > > If you wish to enable user management, leave the `RootPasswordHash` setting blank and follow the steps on [Configure OpenID Connect](https://docs.lacunasoftware.com/en-us/articles/amplia/on-premises/configure-oidc) instead Fill the remaining settings according to the instructions on the configuration file. ## Set up a daemon Create the service definition file: ```sh touch /etc/systemd/system/amplia.service nano /etc/systemd/system/amplia.service ``` Enter the following: ```ini [Unit] Description=Amplia [Service] WorkingDirectory=/usr/share/amplia ExecStart=/usr/bin/dotnet Lacuna.Amplia.Site.dll Restart=always RestartSec=10 KillSignal=SIGINT SyslogIdentifier=amplia User=amplia Environment=ASPNETCORE_ENVIRONMENT=Linux Environment=DOTNET_PRINT_TELEMETRY_MESSAGE=false [Install] WantedBy=multi-user.target ``` Save the file, then enable the service and start it: ```sh systemctl enable amplia systemctl start amplia systemctl status amplia ``` The expected output is similar to: ```text * amplia.service - Amplia Loaded: loaded (/etc/systemd/system/amplia.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2019-07-07 05:50:04 UTC; 4min 22s ago Main PID: 10960 (dotnet) Tasks: 31 (limit: 2319) CGroup: /system.slice/amplia.service └─10960 /usr/bin/dotnet Lacuna.Amplia.Site.dll ... Dec 04 12:45:08 server.patorum.com amplia[32562]: Hosting environment: Production Dec 04 12:45:08 server.patorum.com amplia[32562]: Content root path: /usr/share/amplia Dec 04 12:45:08 server.patorum.com amplia[32562]: Now listening on: http://localhost:5000 Dec 04 12:45:08 server.patorum.com amplia[32562]: Application started. Press Ctrl+C to shut down. Hint: Some lines were ellipsized, use -l to show in full. ``` If necessary, restart the service: `systemctl restart amplia` To test that the Amplia server is running, run: ```sh curl http://localhost:5000/api/system/info ``` The expected output is something like: ```json {"productName":"Lacuna Amplia","productVersion":"5.x.x","spaVersion":"...","timestamp":"..."} ``` ## Set up a reverse proxy server > **Note** > > If you prefer to use Apache instead of Nginx, [see this article](https://docs.microsoft.com/en-us/aspnet/core/host-and-deploy/linux-apache?view=aspnetcore-2.2#configure-apache). Install Nginx (if not already installed): ```sh yum install nginx systemctl enable nginx.service systemctl start nginx.service ``` Test that Nginx is running: ```sh curl -I http://localhost/ ``` Check the first lines of the output, which should be similar to: ```text HTTP/1.1 200 OK Server: nginx/... ... ``` Edit the Nginx configuration: ```sh nano /etc/nginx/nginx.conf ``` Delete or comment out (with `#`s) the entire `server` section, located right below the clause `include /etc/nginx/conf.d/*.conf;`. After commenting out the section, the configuration file should look similar to this: ```nginx ... http { ... # Load modular configuration files from the /etc/nginx/conf.d directory. # See http://nginx.org/en/docs/ngx_core_module.html#include # for more information. include /etc/nginx/conf.d/*.conf; # server { # listen 80 default_server; # listen [::]:80 default_server; # server_name _; # root /usr/share/nginx/html; # # # Load configuration files for the default server block. # include /etc/nginx/default.d/*.conf; # # location / { # } # # error_page 404 /404.html; # location = /40x.html { # } # # error_page 500 502 503 504 /50x.html; # location = /50x.html { # } # } ... } ``` Create a site configuration file for Amplia: ```sh touch /etc/nginx/conf.d/amplia.conf nano /etc/nginx/conf.d/amplia.conf ``` Enter the following, replacing the dashboard domain on the `server_name` entry (see [Dashboard domain](https://docs.lacunasoftware.com/en-us/articles/amplia/on-premises#dashboard-domain)): ```nginx server { listen 80; server_name localhost ca.patorum.com; location / { proxy_pass http://localhost:5000; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection keep-alive; proxy_set_header Host $host; proxy_cache_bypass $http_upgrade; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; } } ``` > **Tip** > > Ideally, your site configuration should contain the entries `ssl_certificate` and `ssl_certificate_key` with a valid SSL certificate. This configuration is outside of the scope of these instructions. Allow Nginx to access the Amplia service: ```sh setsebool -P httpd_can_network_connect on ``` Test the Nginx configuration and reload it: ```sh nginx -t nginx -s reload ``` Test the site: ```sh curl http://localhost/api/system/info ``` Allow HTTP and HTTPS traffic to your system (if not already allowed): ```sh firewall-cmd --zone=public --add-port=80/tcp --permanent firewall-cmd --zone=public --add-port=443/tcp --permanent firewall-cmd --reload ``` ## See also * [Updating Amplia on Linux](https://docs.lacunasoftware.com/en-us/articles/amplia/on-premises/linux/update) * [Troubleshooting](https://docs.lacunasoftware.com/en-us/articles/amplia/on-premises/linux/troubleshoot)