> For the complete documentation index, see [llms.txt](https://docs.hex-rays.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hex-rays.com/floating-license/admin/license-server/license-server-checklist.md).

# Installation Checklist

## New license server

Follow these steps if you do not re-use an already existing license server.

* [ ] Create the license server in the [My Hex-Rays portal](https://my.hex-rays.com/). See: [Add servers](/getting-started/licensing.md#add-servers)
* [ ] Activate your floating license and assign it to the new license server. See: [Floating license activation](/getting-started/licensing.md#floating-licenses-activation)

### Download the required files

* [ ] Download the **license server license** and **certificate bundle** from the [Servers tab](https://my.hex-rays.com/dashboard/servers).
* [ ] Download the installers (**license server** and **IDA Pro**) from the [Download center](https://my.hex-rays.com/dashboard/download-center/installers/release).

### Installation

* [ ] Start the license server installer and follow the steps.
* [ ] Copy the license server license, the certificate and the private key downloaded earlier into the installation directory.
* [ ] Change the license, certificate and private key ownership and access mode:

```
    >cd /opt/hexlicsrv
    >cp .../path/to/hexlicsrv.crt .
    >cp .../path/to/hexlicsrv.key .
    >cp .../path/to/license_server*.hexlic .
    >chown hexlicsrv:hexlicsrv hexlicsrv.crt hexlicsrv.key license_server*.hexlic
    >chmod 640 hexlicsrv.crt hexlicsrv.key license_server*.hexlic
```

* [ ] Create the initial database:

```
    >sudo -u hexlicsrv ./license_server --config-file hexlicsrv.conf \
                                        --recreate-schema
    >2024-04-14 14:30:28 License Server v1.0 Hex-Rays (c) 2024
    >2024-04-14 14:30:28 Database initialized; exiting.
```

* [ ] Test the license server:

```
    >sudo -u hexlicsrv ./license_server --config-file hexlicsrv.conf \
                                        --certchain-file hexlicsrv.crt \
                                        --privkey-file hexlicsrv.key \
                                        --license-file license_server_<LID>.hexlic
    >2024-04-14 14:35:47 License Server v1.0 Hex-Rays (c) 2024
    >2024-04-14 14:35:47 Using a license with 1 seats
    >2024-04-14 14:35:47 Listening on 0.0.0.0:65434...
```

* [ ] Start the service: `systemctl start hexlicsrv`
* [ ] Check that the service is active: `systemctl status hexlicsrv`

If you run into any issues, refer to the [troubleshooting](/floating-license/admin/license-server.md#troubleshooting) section of the documentation.

## Existing license server

* [ ] Activate your floating license and assign it to an existing license server. See: [Floating license activation](/getting-started/licensing.md#floating-licenses-activation)
* [ ] Download the license server from the [Servers tab](https://my.hex-rays.com/dashboard/servers).

### License file update

* [ ] Stop the license server: `systemctl stop hexlicsrv`
* [ ] Replace the existing license file with the new one.
* [ ] Make sure that the ownership and access mode are set correctly, using the same commands described in the [Installation](#installation) section above.
* [ ] Restart the service: `systemctl start hexlicsrv`


---

# 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://docs.hex-rays.com/floating-license/admin/license-server/license-server-checklist.md?ask=<question>&goal=<endgoal>
```

`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.