# Connectors 1. [Home](https://www.agilicus.com/) 2. [Agilicus AnyX Administrative Web Interface](https://www.agilicus.com/anyx-guide/agilicus-anyx-administrative-web-interface/) 3. [Resources](https://www.agilicus.com/anyx-guide/agilicus-anyx-administrative-web-interface/resources/) 4. Connectors ![](https://www.agilicus.com/www/9ba6112d-featured-anyx-admin-resourcesconnectors.png)## Connectors [CONTACT](/contact-us/) The **Connectors** pages (routes `/connector-overview`, `/connector-new`, and `/forwarding-services`) manage the outbound-only links between your site and the Agilicus cloud. A connector is the small piece of software that runs on your side of the network and fronts your local resources. See [Connectors (concepts)](/anyx-guide/agilicus-anyx-administrative-web-interface/concepts/connectors/) for the full theory. ## Purpose A connector links your site to the Agilicus cloud using outbound-only connections, so your resources need no inbound ports and are invisible to the public internet. The Connectors overview lists every connector you have deployed and its health, is where you create new connectors and install them, and where you manage routing, proxying, and detailed statistics. The Forwarding Services page makes a network resource at one site available to a connector at another site. ``` %%{init: {"theme": "base", "themeVariables": {"background": "#ffffff", "primaryColor": "#e8f1fb", "primaryBorderColor": "#1f4e79", "primaryTextColor": "#111111", "lineColor": "#4a4a4a", "secondaryColor": "#f5f5f5", "fontFamily": "Inter, sans-serif"}} }%% flowchart LR subgraph Cloud["Agilicus cloud"] AP[Identity-aware proxy] end subgraph SiteA["Site A"] C1[Connector] R1[Web application] R2[Database] end subgraph SiteB["Site B"] C2[Connector] R3[Legacy system] end AP <-->|outbound-only tunnel| C1 AP <-->|outbound-only tunnel| C2 C1 --> R1 C1 --> R2 C2 --> R3 ``` ## Why use it - Expose internal applications, databases, shares, desktops, and SSH services with no firewall changes and no public addresses. - Run high-availability pairs of connectors so a single failure does not interrupt access. - Create a connector quickly and install it on a container, Linux host, router, appliance, or Windows machine with a single command. - Monitor connector health, live connection statistics, routes, and proxying from one screen. - Forward a network resource (for example a database) from one site to a connector at another site, without a VPN. ## When to use it - During initial setup, when you first connect your site (see [Getting started: connect to sites](/anyx-guide/agilicus-anyx-administrative-web-interface/getting-started/connect-to-sites/)). - Whenever you add a new site or network segment that needs to reach the platform. - When you need to inspect why a connector or the resources behind it are unreachable. - When a site at another location needs access to a network resource at your site. **Prerequisite**: permission to administer connectors and applications (an owner or administrator role). Without it, the pages show a *no permissions* message. ## How to use it ### Connector overview 1. Open **Resources > Connectors > Overview** from the left navigation. ![Connector overview](https://www.agilicus.com/www/495da492-connector-overview.png) The table lists every connector with its type icon, name, the networks assigned to it, its status, live connection counters, an *Is Listening* indicator, and an actions menu. Expand a connector row to see its instances, NTP forwarding options, and the *Sync local clock* setting. 1. Use the toolbar buttons to add a connector (**ADD CONNECTOR**), manage **SIEM FORWARDING** (see [Audit destinations](/anyx-guide/agilicus-anyx-administrative-web-interface/organisation/audit-destinations/)), or delete selected connectors. 1. Open the **more** menu on a connector row for the row actions: ![Connector overview row actions](https://www.agilicus.com/www/a3cae43b-connector-overview-row-actions.png) - **Install Connector**: opens the download dialog with the install command for this connector. - **Search in Audits**: jumps to the audit subsystem filtered to the resources behind this connector. - **Manage Routes**: opens the routes dialog to add, modify, or delete local listen routes. - **View Detailed Statistics**: opens the statistics dialog with live counters. - **Manage Proxies**: opens the proxies dialog to arrange connectors as outer or inner proxies. - **Configure Networks**: assigns networks (application services) to the connector. ### Creating and installing a connector 1. Open **Resources > Connectors > New**. The wizard has two steps: **Connector name** and **Done**. ![New connector wizard: step 1](https://www.agilicus.com/www/64df9024-connector-wizard-step1-name.png) 1. Enter a name. The tooltip explains that it must be unique across all connectors. Select **Create**. 1. The Done step confirms the connector was created and offers **Install Connector**. ![New connector wizard: step 2, done](https://www.agilicus.com/www/42455faa-connector-wizard-step2-done.png) 1. Select **Install Connector** to open the download dialog, which shows the exact command to run on the target device. The dialog has tabs for **Linux**, **Windows (CMD)**, **Windows (PowerShell)**, **Docker**, and **Manual**. ![Connector download dialog from the wizard](https://www.agilicus.com/www/dcc7866d-connector-wizard-install-dialog.png) The same dialog opens from **Install Connector** on the connector overview row menu: ![Connector download dialog](https://www.agilicus.com/www/512ae007-connector-download-dialog.png) For a container environment, the Docker tab gives a ready-to-run command: ``` docker run -d --name agilicus-connector --net=host --restart=always \ -v agilicus_cfg:/etc/agilicus/agent \ -e AGILICUS_CHALLENGE_ID= -e AGILICUS_CHALLENGE_CODE= \ cr.agilicus.com/pub/images/agilicus-agent/client:stable ``` ![Connector download dialog: Docker](https://www.agilicus.com/www/7633ca2a-connector-download-dialog-docker.png) The Manual tab shows the generic installer command: ``` agilicus-agent client --install --challenge-id --challenge-code ``` ![Connector download instructions: manual](https://www.agilicus.com/www/a3cae43b-connector-download-instructions-manual.png) 1. Copy the command with **COPY**, run it on the target device, and the connector signs in to the platform. The command expires; select **REGENERATE** for a new one. Tick *This is a subsequent connector (create a cluster)* to add a connector to an existing high-availability cluster. After installation the connector appears on the overview with its health and counters. See [Connector sign-in](https://www.agilicus.com/product-guide/connector-sign-in) and [Generic connector install](https://www.agilicus.com/product-guide/generic-connector-install). ### Inspecting connector statistics 1. From the row actions menu, select **View Detailed Statistics** to open the statistics dialog. ![Connector statistics dialog](https://www.agilicus.com/www/dcc7866d-connector-stats-dialog.png) The dialog shows live counters grouped into **Overall Connection Statistics** (connections successful, failed, current, timed out, reset, host not found, and bytes and datagrams in each direction), **Overall TLS Statistics**, **Overall Share Statistics**, and **Overall HTTP Statistics**. These update while the dialog is open and are the fastest way to see whether a connector is healthy. ### Managing routes 1. From the row actions menu, select **Manage Routes** to open the routes dialog, where you add a route with a **Port**, a **Hostname/IP**, and **Bind To Everything**, delete routes, and save. ![Connector routes dialog](https://www.agilicus.com/www/8f1ea1a8-connector-routes-dialog.png) ### Managing proxies 1. From the row actions menu, select **Manage Proxies** to arrange connectors as proxies for each other, useful when a connector cannot reach a resource directly. The dialog shows the outer connector and inner connectors. ![Connector proxies dialog](https://www.agilicus.com/www/200cfc4d-connector-proxy-dialog.png) ### Forwarding services 1. Open **Resources > Connectors > Forwarding**. This page makes a network resource available to a connector at another site. ![Forwarding services](https://www.agilicus.com/www/21f02783-forwarding-services.png) 1. Select **ADD FORWARDING SERVICE** to add a row, then choose the **Source connector** (the connector on the remote site that needs access) and the **Destination Network** (the network resource at your site). The **Protocol**, **Destination IP/hostname**, and **Destination Ports** fill in from the destination network; set the **Source IP/hostname** (for example `0.0.0.0` to expose it to any device in the site, or `localhost` to keep it local) and **Source Ports** if they differ from the destination. ![Forwarding services: populated](https://www.agilicus.com/www/16a309e9-forwarding-services-populated.png) The example above forwards local port 5432 on the connector *x9* to the network *demo-db-01* at 10.10.10.50:5432. Select **DELETE FORWARDING SERVICES** to remove selected rules. ## Fields and controls reference | Control | Purpose | Required | Default | Valid values | Notes | |---|---|---|---|---|---| | Name | The connector's unique name | Yes | n/a | Up to 100 characters | Must be unique across all connectors | | Networks | Application services assigned to the connector | No | n/a | One or more networks | Configured from the row actions menu | | Status | Summary health of the connector | Read-only | n/a | Good, warn, down, not available | With a colour-coded icon and tooltip | | Connections successful | Live count of successful connections | Read-only | n/a | A number | Updates while the page is open | | Connections failed | Live count of failed connections | Read-only | n/a | A number | A rising value indicates problems | | Is Listening | Whether the connector exposes its assigned resources locally | Read-only | n/a | Checked or unchecked | | | NTP forwarding | Whether the connector forwards network time protocol traffic | No | disabled | disabled, local, all | On the expanded row | | Sync local clock | Whether the connector synchronises its local clock | No | Unchecked | Checked or unchecked | On the expanded row | | Source connector | Connector that provides the forwarding service | Yes | n/a | A configured connector | Forwarding page | | Destination Network | Network resource being forwarded | Yes | n/a | A network with a port | Forwarding page | | Source IP/hostname | Local address the service binds to | No | localhost | localhost or 0.0.0.0 | Forwarding page | | Source/Destination Ports | Port or port ranges | No | Destination ports | For example 80, or 80, 1000-2000 | Forwarding page | ## Dialogs and popups - **Connector download dialog**: the install command per platform (Linux, Windows CMD, Windows PowerShell, Docker, Manual), the *subsequent connector* cluster option, **COPY**, **REGENERATE**, and the command expiry timer. - **Connector statistics dialog**: live connection, TLS, share, and HTTP counters. - **Connector routes dialog**: add and delete local listen routes. - **Connector proxies dialog**: arrange outer and inner proxies. - **SIEM forwarding dialog**: the **SIEM FORWARDING** button opens the Agilicus SIEM Forwarding Settings dialog, where you enable the Microsoft Sentinel or Google SecOps proxy presets, choose which connectors act as SIEM traffic proxies, and read the DNS configuration instructions for the hostnames to point at your connector. ![SIEM forwarding dialog](https://www.agilicus.com/www/42455faa-connectors-siem-forwarding-dialog.png) - **Confirmation dialog**: deleting a connector warns you to uninstall it from its host first; if the connector has running instances, the dialog tells you which hostnames were seen running it recently and asks you to uninstall it there too. ![Connector delete confirmation](https://www.agilicus.com/www/7633ca2a-connector-delete-confirmation.png) ## Configuration versus diagnostics versus confirmation - **Configuration**: creating connectors, installing them, routes, proxies, networks, forwarding services, and the NTP and clock settings on the expanded row are persistent configuration. - **Diagnostics**: the status column, live connection counters, and the statistics dialog are read-only health information. - **Confirmation**: deleting a connector is permanent and stops the platform from reaching the resources behind it. Confirm that the connector software is uninstalled from its host before deleting. ## Pagination and async behaviour - The connector overview pages at **25 rows per page**; the paginator shows the current page and totals. The demo organisation has 1 connector, so all rows appear on one page. - Connector creation and deletion apply asynchronously. After creating a connector, wait a few seconds, then reload to see it on the overview with its health. Newly created connectors show *not available* until the software signs in. - The status column and connection counters poll and update while the page is open (roughly every few seconds). - Forwarding services save when you blur the edited row; after adding or deleting a rule, wait a few seconds, then reload to confirm. ## Troubleshooting - **A connector shows Down**: check the machine it runs on is powered on and reachable, and that it can make outbound HTTPS connections to the Agilicus cloud. See [Site firewall configuration](https://www.agilicus.com/site-firewall-configuration). - **A connector shows Not Available**: it has been created but has not signed in yet. Run the install command from the download dialog and check the connector's logs. - **Connections failed is rising**: the resources behind the connector are unreachable from it. Verify the resource addresses, and use **Search in Audits** from the row menu to see the failed requests. - **A forwarding service does not work**: check that the source connector is installed and healthy at the remote site, the destination network exists and is reachable, and that source and destination ports do not conflict with another forwarding rule on the same host. - **A newly created connector name does not appear**: the name must be unique across all connectors; the wizard shows a validation error if it is not. ## See also - [Connectors (concepts)](/anyx-guide/agilicus-anyx-administrative-web-interface/concepts/connectors/) - [Zero trust architecture](/anyx-guide/agilicus-anyx-administrative-web-interface/concepts/zero-trust-architecture/) - [Applications](/anyx-guide/agilicus-anyx-administrative-web-interface/resources/applications/) - [Networks (portal page)](/anyx-guide/agilicus-anyx-administrative-web-interface/resources/networks/) - [Audits](/anyx-guide/agilicus-anyx-administrative-web-interface/access/audits/) - [Policies](/anyx-guide/agilicus-anyx-administrative-web-interface/access/policies/) - [Audit destinations](/anyx-guide/agilicus-anyx-administrative-web-interface/organisation/audit-destinations/) - [Getting started: connect to sites](/anyx-guide/agilicus-anyx-administrative-web-interface/getting-started/connect-to-sites/) ## Web guide - [Agilicus connector](https://www.agilicus.com/product-guide/agilicus-connector) - [Generic connector install (Linux, FreeBSD, embedded)](https://www.agilicus.com/product-guide/generic-connector-install) - [Connector sign-in](https://www.agilicus.com/product-guide/connector-sign-in) - [Connector details and diagnostic counters](https://www.agilicus.com/product-guide/connector-details-diagnostic-counters) - [Connector high availability](https://www.agilicus.com/product-guide/agilicus-connector-high-availability) - [Forwarding](https://www.agilicus.com/product-guide/forwarding) - [Site firewall configuration](https://www.agilicus.com/site-firewall-configuration)