Overview
This article explains how to use the "Hosts" page in the LGF Cloud Portal. This interface is used to add new platform hosts and to manage, inspect, and sync existing ones with the Host Cloud API.

_Figure: The main interface for managing hosts._
Prerequisites
Before adding a host, you will need:
- Administrator access to the LGF Cloud Portal.
- A provisioned and network-accessible host that you want to register.
- A valid Cloud API token generated from the target host.
Adding a New Host
To register a new host and make its platforms available for deployment:
- From the top navigation bar, click on Hosts.
- Locate the Add Host form at the top of the page.
- Name: Enter a unique, descriptive name for the host (e.g.,
lfw-lgf04). - Base URL: Enter the full, public-facing URL for the host, without any trailing slash (e.g.,
https://lfw-lgf04.dhcp). - Cloud API token: Paste the security token generated by the host.
- Click the Add Host button to save the configuration.
Managing Existing Hosts
The Known Hosts list displays all currently registered hosts.
- Name / Base URL: Identifiers for the host.
- RP Base Domain: The reverse proxy domain associated with the host.
- Actions:
- Test: Click this to send a test signal to the host to verify connectivity and API token validity.
- Refresh Platforms: Click this to sync the list of deployable platforms from the host. This is useful after a host's configuration has changed.
- Delete: This will remove the host and all associated platforms from the Cloud Portal. This action cannot be undone.
Below the host entry, a series of badges shows all the deployable platforms currently synced from that host (e.g., atc, gitlab, keycloak).
Verification
A successfully added host will immediately appear in the Known Hosts list. You can click the Test button to confirm that the Cloud Portal can communicate with it. A successful test indicates the host is configured correctly.
Troubleshooting
Failed to Add Host
If the portal shows an error when you click "Add Host", check the following:
- The Base URL is correct and publicly accessible.
- The Cloud API token is valid and has not expired.
Test Fails
If the Test action fails, it usually points to a network issue.
- Ensure there are no firewalls blocking communication from the Cloud Portal to the host's Base URL.
- Verify the host's services are running correctly.