> For the complete documentation index, see [llms.txt](https://docs.lithnet.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lithnet.io/ams/v2.1/help-and-support/app-pages/host-configuration-page.md).

# Host configuration page

Settings on this page apply to the physical host computer only. If you have more than one Access Manager server, these settings will be unique to each server.

![](https://1174763835-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYKUIJoHjACu79Ekwwf7i%2Fuploads%2Fgit-blob-438368d8aec5ee8d5f074baf98672ba92ce1c0e4%2Fui-page-host-configuration.png?alt=media)

## App version and updates

Shows the current application version, and optionally shows you if there is a new version of the application available. You can prevent the application from checking for updates, by disabling the `Enable update checks` option. Note that this only checks to see if updates are available. Updates must always be downloaded and installed manually.

## Service account

Specifies the service account that runs the Access Manager Service application. Use a group-managed service account where ever possible.

Before you change the service account, make sure the database permissions allow the new account to connect. If you are using the built-in SQL express database, you do not need to make any manual changes.

## TLS/SSL Certificate

### Certificate

Specify the TLS certificate used to protect HTTPS traffic to and from the website. You can select a certificate from the local machine store, or import a PFX file.

### Certificate expiry

Shows how long until the currently selected certificate expires.

## HTTP configuration

### HTTP Port

The HTTP port that the application will listen on. The default is port 80. Note that this port is only used to redirect connections to HTTPS. The application won't serve content over non HTTPS connections.

### HTTPS Port

The HTTPS port that the application will listen on. The default is port 443.

## Web app configuration

### Enable the web app

When enabled, this host will serve the Access Manager web app. You can disable this if you want to have an API-only or configuration-only host.

## API configuration

### Enable the Access Manager API

When enabled, the Access Manager service API is activated, allowing devices with the Lithnet Access Manager Agent installed to communicate with this server and manage their local admin passwords.

### API host name

When the Access Manager API is enabled, you must specify a valid DNS name that will be used by Access Manager Agents to contact this host. This name must match exactly with the AMS server name configured on the agents themselves, and it must be present in the HTTPS certificate used by the service.

:::{admonition} Warning :class: warning If this value differs from the AMS server name configured in the agent at installation time, the agent will be unable to communicate with the server :::


---

# 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.lithnet.io/ams/v2.1/help-and-support/app-pages/host-configuration-page.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.
