> For the complete documentation index, see [llms.txt](https://inuva.gitbook.io/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://inuva.gitbook.io/home/self-hosting-inuva.md).
# Self hosting Inuva
### How can I install it?
When you buy the [Inuva standalone](https://inuva.me/sign-up) version, you get a license key. The license key is 11 characters long and is valid for up to 5 machines. You don't have to note down the license key as you can retrieve it anytime you want on the Inuva site.
Once you log in you'll be redirected to the [download page](https://inuva.me/download). The command to download the installer will be displayed along with your license key.
You can enter these commands in any Linux distribution (tested on Ubuntu 22 and Debian). This will load up the installer and prompt you to configure your unique Inuva configuration. During the installation process, you'll be prompted to enter a **6 digit passcode**, this will be your login password.
Once the installer is finished you will have the following:
1. The Inuva server running on port `49152`
2. A new entry in crontab that automatically updates Inuva
3. Optionally: Nginx configured with Brotli module and HTTP/3
4. Optionally: VS Code dev tunnel installed on the system
{% hint style="info" %}
Inuva will be installed in `/srv/inuva`. Here you'll find the SQLite database and the compiled code.
{% endhint %}
### What now?
The inuva server is running on port `49152` if the server is on your local network you can surf to the machine's IP-address with the port number like this `http://192.0.0.3:49152`. You'll see the login screen and you can now enter the **6 digit passcode** that you entered during installation.
Your login page
{% hint style="warning" %}
After 10 failed login attempts you will be blocked for 15 minutes. This protects you from attackers that try to brute force your login.
{% endhint %}
After a succesful login, you'll be redirected to the desktop page. That should look a bit like this:
The standard Inuva desktop
#### Public Access
If you have followed this guide, you are accessing Inuva on your local network. When you're on the go you don't have access to your local network but you probably still want to access your Inuva desktop.
{% hint style="danger" %}
It is strongly advised to only access Inuva over secure TLS connections!
{% endhint %}
If you're new to hosting a public website on a server I would strongly recommend that you look into Nginx that acts as a reverse proxy. For more advanced users, you can download an Nginx template from the inuva website by making an authenticated GET request to . You can learn how to make authenticated requests at [API](/home/developers/api.md)
### Next steps
Congratulations, you have Inuva installed on your machine or server. You can now access your machine or server with a GUI from anywhere on any devices. Make sure to test out Inuva on your smartphone or tablet.
You can join the [Discord ](https://discord.gg/A3PBghf5d9)for the latest updates, report bugs, request new features and vote on major updates.
### Troubleshooting
#### I see errors during installation
This can happen, the installer tries to recover from failed installations but you can check a couple of things.
* Try to install again with `--force`, without extra options such as Nginx, VS Code, auto updates. If this succeeds, you can restart the installer with modules enabled until you find which module is causing the error.
* Check if the Inuva server is running by entering the following command `sudo systemctl status inuva` . If this is running you should be able to navigate to your desktop.
* Check if the cron entry was made by executing the following command `sudo cat /etc/crontab` . If you don't see any entry with Inuva, you can contact us or wait for a new update.
* Nginx install fails, this is highly experimental and only works on Ubuntu 22. Any other installation is not tested or patched.
* You can find logs in various places: `/var/log/inuva.log` , `/var/log/update.log`, `sudo systemctl status inuva`, `sudo journalctl -u inuva`
* Node is not installed or you don't have the correct version installed. I would highly recommend installing [NVM](https://github.com/nvm-sh/nvm):
```bash
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.7/install.sh | bash
nvm install 20.4
```
If something just isn't working out, feel free to post it on the [Discord ](https://discord.gg/A3PBghf5d9)or just DM me. I'm also available on [Twitter](https://twitter.com/LaurensMesure)! If you like a more traditional way to reach out, you can contact .
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://inuva.gitbook.io/home/self-hosting-inuva.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.