> For the complete documentation index, see [llms.txt](https://docs.verge.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verge.io/run-the-platform/system-administration/license-updates-verify.md).

# Verify Licensing and Update Server Configuration

How to verify connectivity to the VergeOS update server and troubleshoot licensing configuration issues, including credentials and update source selection.

Valid licensing configuration is required to run workloads and NAS services and to perform system updates. Normal licensing and updates will require connection and authentication to a VergeOS Update Server.

{% hint style="info" %}
**For Air-gap licensing/updates see: KB articles:** [**Requesting an Airgap License for VergeOS**](/knowledge-base/system-administration/requesting-an-airgap-license.md) **and** [**Updating a VergeOS System with Airgap License**](/knowledge-base/system-administration/updating-vergeos-system-with-airgap-license.md)**.**
{% endhint %}

## Verify Connection to a VergeOS Update Server

1. From the Main Dashboard, navigate to **System > Updates**. This will bring you to the Updates Dashboard.
2. Click **Check For Updates** on the left menu.
3. Verify a green indicator in the ***Status*** field. A failed connection will be indicated with a red status and an error message in the status field.
4. If the status is not green:
   * click **Edit Settings** on the left menu.
   * Verify **correct licensing User/Password**. If you are unsure of your licensing credentials contact your VergeOS sales or support representative.
   * Verify **Update Source**
     * for home labs and POC (Not-for-resale) installations: ***Verge.io Trial/NFR***
     * for normal production licenses: ***Verge.io Updates***
   * Verify **Internet connection** from the VergeOS system.


---

# 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://docs.verge.io/run-the-platform/system-administration/license-updates-verify.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.