# Client Installation

PostLab Local is a special version of PostLab that only works with local GitLab servers.&#x20;

## Download

The latest PostLab Local release [is available here under `[Local]`](/postlab-classic/releases.md).

## Prerequisites

**Before launching the PostLab Local client on your Mac...**

1. Disable all unused network connections on your Mac.
   * Disable all active network connections except one to simplify administration.
2. [Disable IPv6 on any enabled network connections.](https://protonvpn.com/support/how-to-disable-ipv6-protocol-on-macos/)
3. Confirm your local area network has an active DHCP server in place.
4. [Add your PostLab Local Server's IP Address and Hostname to the `/etc/hosts` file.](#add-your-postlab-local-servers-ip-address-and-hostname-to-etc-hosts)
5. [Add the Self-Signed Certificate to your Mac.](#add-the-self-signed-certificate)
6. [Log into PostLab Local server, then reset your password.](#log-into-postlab-local-server-then-reset-your-password)

### Add Your PostLab Local Server's IP Address and Hostname to `/etc/hosts`

1. In Terminal, open the `/etc/hosts` file in your favorite text editor. For example, here's how you would open `/etc/hosts` using the `nano` editor:

```sh
sudo nano /etc/hosts
```

2. Add a new dedicated line with the the IP address and hostname in the form of:

`ip_address` `hostname`

Example:

```sh
192.168.1.3 hoth.postlab.local
```

{% hint style="danger" %}
The `/etc/hosts` file *must* have only one entry for the Hostname. Even if another line with the same Hostname is commented out for testing purposes, doing so will interfere with the PostLab Local Client working as expected.
{% endhint %}

3. Save the `/etc/hosts` file.
4. Done!

### Add the Self-Signed Certificate

{% hint style="success" %}
For Team Leads: have you created the self-signed certificate for your Team yet? If you still need to, stop here, [follow these steps to create a certificate on your PostLab Local Server](/postlab-classic/postlab-local/self-signed-certificates.md), then continue.
{% endhint %}

1. Open your PostLab Local Server in a Web browser by its Hostname and Port `8443` (e.g. `https://hoth.postlab.local:8443`)

{% hint style="warning" %}
Are you getting a `502` error in your Web browser? GitLab's services are still starting up. Wait a few minutes, then retry accessing the PostLab Local Server in your browser.&#x20;
{% endhint %}

2. Save the certificate to your local computer by dragging the certificate icon in your Web browser's address bar to a local folder.
3. In Finder, double-click the certificate file, which will launch `Keychain Access.app`.
4. When Keychain Access asks you where to store the certificate, choose `System`.
5. In Keychain Access, set `Trust > When using this certificate:` to `Always Trust`.

{% hint style="warning" %}
Can't see the PostLab Local Server certificate in Keychain Access? In `Keychain Access.app`, go to `View > Show Expired Certificates`. Although the certificate may be expired, as long as you downloaded it from the PostLab Local Server, it's still valid and trustworthy.
{% endhint %}

6. Done!

### Log into PostLab Local server, then reset your password

1. Open your PostLab Local Server in a Web browser by its Hostname and Port `8443` (e.g. `https://hoth.postlab.local:8443`)
2. Sign in under that newly created user provided by your PostLab Local support team.
3. Once you sign in as the new user, you can either update the password or use the same password.
4. Done!

Now you're ready to launch the PostLab Local client.

## Initial Use

When you first launch the PostLab Local client, it needs two pieces of information:

1. An `Activation number`, which is your license key.
2. Your PostLab Local Server's Hostname.
   * This is the same Hostname as your GitLab server. (Example: `hoth.postlab.local`)

{% hint style="success" %}
The first time you activate the PostLab Local client, your computer needs access to the public Internet. If your network has restrictions in place, you may have to add this HostName and Port to any Allowed Lists:\
\
[https://wyday.com](https://wyday.com/) on port 443
{% endhint %}

<figure><img src="/files/DV1RABbYvl5jk4hOtHit" alt=""><figcaption><p>Activate PostLab with the provided license key.</p></figcaption></figure>

<figure><img src="/files/sdRMlZp0FcfIwtMo2J3R" alt=""><figcaption><p>Click + to add your GitLab server</p></figcaption></figure>

<figure><img src="/files/x74x45t0qECk91YQJqNx" alt=""><figcaption><p>Enter your GitLab server URL or IP address</p></figcaption></figure>

Once you click `Continue`, PostLab Local is ready to use from this computer.

To get started, try one of our [Initial Workflow Checklists](/postlab-classic/checklists.md) for your NLE/video editing app of choice.


---

# Agent Instructions: 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:

```
GET https://docs.hedge.video/postlab-classic/postlab-local/client-installation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
