> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/on-premise/on-premise/how-to-guide/installation/advanced-installation/ubuntu-20.md).

# Linux installation script

Install Navixy On-Premise on Ubuntu, Debian, AlmaLinux, Rocky Linux, or Red Hat Enterprise Linux with the installation script, then open the Admin Panel.

This guide describes Navixy On-Premise platform installation using automated scripts. This type of installation is designed for and supported only on these 64-bit Linux distributions:

* Ubuntu 22.04, 24.04, and 26.04
* Debian 12 and 13
* AlmaLinux, Rocky Linux, and Red Hat Enterprise Linux 9 and 10

On AlmaLinux, Rocky Linux, and Red Hat Enterprise Linux, SELinux stays in enforcing mode. If firewalld is active, the script asks whether to open the HTTP and HTTPS ports. Open the ports for your GPS devices yourself. Store your own HTTPS certificates under `/etc`: SELinux doesn't let Nginx read certificates from other folders.

For other Linux distros, only manual installation is available.

For Windows servers, navigate to [the relevant section](https://navixy.com/docs/on-premise/on-premise/how-to-guide/installation/advanced-installation/windows-installation.md).

## Checking prerequisites

First, you need to have the following before you start the installation:

* A server (or servers) meeting all the [Server hardware](https://navixy.com/docs/on-premise/on-premise/how-to-guide/requirements/server-hardware.md) requirements
* Registered domain names that you will use for your Navixy instance
* Navixy software package and License key provided by the Navixy team
* Internet access from the server to the repositories that the script installs software from:
  * `repo.mysql.com`, for MySQL 8.4
  * `packages.adoptium.net`, on Debian 12, for Temurin JDK 25
  * the EPEL and CRB repositories, on AlmaLinux, Rocky Linux, and Red Hat Enterprise Linux. On Red Hat Enterprise Linux, also `dl.fedoraproject.org`.

This automatic process will install all the software prerequisites listed in [Server software](https://navixy.com/docs/on-premise/on-premise/how-to-guide/requirements/server-software.md) document meaning that you don't need to install them yourself manually.

## Navixy package

The Navixy On-Premise distribution package is always available for download at the [direct link](https://get.navixy.com/latest). On Linux, you can download it with `wget` using the following command:

```
wget https://get.navixy.com/latest --content-disposition
```

## Wizards for installation and configuration

Script for [automatic initial installation](https://navixy.com/docs/on-premise/on-premise/how-to-guide/installation/advanced-installation/ubuntu-20/installation-wizard.md)

Script for [automatic configuration](https://navixy.com/docs/on-premise/on-premise/how-to-guide/installation/advanced-installation/ubuntu-20/configuration-wizard.md)

## **Final steps**

When the instalation is done, you can login to the admin panel using domain name you have specified during the installation. Default login is '**admin**' and password is '**admin**'. To make additional settings, you can run the [Configuration wizard](https://navixy.com/docs/on-premise/on-premise/how-to-guide/installation/advanced-installation/ubuntu-20/configuration-wizard.md) again and choose other options.

If you have any questions regarding the installation or configuration of the product, please contact Navixy technical support at <support@navixy.com>.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://navixy.com/docs/on-premise/on-premise/how-to-guide/installation/advanced-installation/ubuntu-20.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
