--- title: "Troubleshooting appliance registration" slug: "troubleshooting-appliance-registration-v7-0" description: "Troubleshoot appliance registration issues with our guide. Learn to check connectivity, firewall settings, and ensure your appliance is activated correctly." tags: ["Troubleshooting", "Appliance Troubleshooting", "Appliances"] updated: 2026-06-05T19:17:37Z published: 2026-06-05T19:17:37Z canonical: "support.appgate.com/troubleshooting-appliance-registration-v7-0" --- > ## Documentation Index > Fetch the complete documentation index at: https://support.appgate.com/llms.txt > Use this file to discover all available pages before exploring further. # Troubleshooting appliance registration After an appliance has been configured and seeded, the next step is to register the appliance with the Controller. This should happen automatically, however networking issues may prevent the new appliance from registering correctly. This section provides guidance on troubleshooting appliances that do not register automatically. --- ## Prerequisites - You will need SSH access to the Controller and the new appliance. --- ## Troubleshooting registration issues The [Appliances](/v1/docs/appliances-page-v7-0) page (System > Appliances) displays the state of all appliances in the ***Status*** column. When a new appliance has been configured, it will appear on the Appliances list as *Not Active* until it is activated. If the appliance is showing status information, a version number, and statistics, then it is correctly registered. If your new appliance remains *Not Active* after several minutes, try the following steps to identify where the issue lies. The usual causes of registration failure are networking, firewall, and DNS problems. ![](https://cdn.us.document360.io/e7482ce5-acfa-4c3b-b76c-b6c32472644a/Images/Documentation/image-1772802510350.png?sv=2026-02-06&spr=https&st=2026-11-21T21%3A49%3A48Z&se=2026-11-21T22%3A49%3A48Z&sr=b&sp=r&sig=OOYmcsPJX%2FtgRzbqRya2l%2B348WIZDJA2e%2FivDb2jb5k%3D) All new appliances must connect to the Controller to be activated. So if an appliance is *Not Active* then it is either not seeded or cannot make an outbound connection on port 443 to the Controller. #### Contacting the new appliance To attempt to contact the new appliance: 1. SSH to the new appliance using its IP address and DNS name. For example: `$ ssh -i ~/keys/my-key my-controller.uksouth.cloudapp.azure.com` `$ ssh -i ~/keys/my-key cz@52.243.40.102` If you cannot connect using the DNS name, then there is a DNS registration problem with the new appliance. 1. Once logged in you should see the following: `Authorized uses only. All activity may be monitored and reported.` `Last login: Wed Jul 22 09:01:11 2020` `Welcome to AppGate SDP (GNU/Linux 5.3.0-61-generic x86_64)` `appgate 5.2.0-21363-release (image1)` `Hint: run 'sudo cz-setup' for appliance management.` #### Verify that the appliance is seeded To check if the appliance is seeded, enter the following command: `$ cat /mnt/state/last-state` Once the appliance is in a steady state you should see: `waiting_config` - The seed file has not been found. See the section on [manually seeding an appliance](/v1/docs/activating-an-appliance-v7-0#manually-seeding-an-appliance). `appliance_ready` - The appliance is seeded and ready to talk to the Controller. May show other states if it is a Controller. #### Verify that the Controller is reachable To see if you can contact the Controller, use the nc command. For example: `$ nc -z -v my-controller.uksouth.cloudapp.azure.com 443` `$ nc -z -v 51.140.54.245 443` If you cannot connect using the DNS name, then there is a DNS registration problem with the Controller appliance. If you can reach the Controller, you should see: *Connection to my-controller.uksouth.cloudapp.azure.com 443 port [tcp/snpp] succeeded!* If you cannot connect, then you need to check the outbound firewall rules at the Gateway and the inbound rules at the Controller. Once activated, the appliance will show on the dashboard and indicate its health status. If it is not reporting as *Healthy* then it may be only partially connected. This might be the case with Controllers that are required to make connections in both directions. ### Appliances with a *Warning* status If the dashboard displays a *Warning* status, it may not have registered correctly and there are still some networking, firewall, or DNS issues remaining: - An appliance may have registered but can connect to only one of two Controllers - An appliance might be having issues connecting to the LogServer or LogForwarders ![List of appliances with their statuses, functions, and resource usage details displayed.](https://cdn.us.document360.io/e7482ce5-acfa-4c3b-b76c-b6c32472644a/Images/Documentation/warning_appliance.png?sv=2026-02-06&spr=https&st=2026-11-21T21%3A49%3A48Z&se=2026-11-21T22%3A49%3A48Z&sr=b&sp=r&sig=wBkAvsWR%2FfpU%2F7QeD%2B5nunyd1dSGGsR0rZs92%2BF5eIE%3D) > [!NOTE] > **NOTE** > > Unlike Gateways, Portals, and Connectors that only make outbound 443 connections, Controllers, LogForwarders, the LogServer, and the Metrics Aggregator need to be able to receive traffic on 443 from other members of the Collective. If you do not get a correctly registered appliance within a few minutes of activation, try following the steps below to identify where the issue lies. #### Verify that the new appliance is reachable To see if you can contact the appliance, SSH in to the relevant appliances and then use the nc command. For example: `$ nc -z -v myserver.mycompany.com 443` `$ nc -z -v 52.243.40.102 443` If you cannot connect using the DNS name, then there is a DNS registration problem with the new appliance. If you can connect, you should see: *Connection to myserver.mycompany.com port 443 [tcp/snpp] succeeded!* You should also try this from your own PC. If you cannot connect at all, check the inbound firewall rules at the Gateway. If you can connect from your PC but not the Controller, check the outbound rules at the Controller. If the appliance is showing a *Healthy* status, then the problem is no longer with port 443 nor with DNS. For more information, see the section about how to fix any issues with both the set-up and maintenance of [HA Controllers](/v1/docs/controller-maintenance-and-troubleshooting-v7-0).