--- title: "Check the Deployment Status and Troubleshoot Startup Issues in Lasernet Keep" slug: "check-the-lasernet-keep-deployment-status-and-troubleshoot-startup-issues" description: "How to check the deployment status of Lasernet Keep and how to troubleshoot some common startup issues." tags: ["Lasernet Keep", "Troubleshooting"] updated: 2026-05-27T15:13:04Z published: 2026-05-27T15:13:04Z canonical: "kb.lasernetgroup.com/check-the-lasernet-keep-deployment-status-and-troubleshoot-startup-issues" --- > ## Documentation Index > Fetch the complete documentation index at: https://kb.lasernetgroup.com/llms.txt > Use this file to discover all available pages before exploring further. # Check the Deployment Status and Troubleshoot Startup Issues in Lasernet Keep > [!NOTE] > Note > > This article applies only to standalone installations. If users cannot access Lasernet Keep or the REST API is not responding, check the deployment status. This article explains how to check the deployment status and troubleshoot common startup issues for a standalone installation of Keep. ## Check the Deployment Status Keep is Java software running on a bundled Wildfly application server. After Wildfly starts, it completes the following deployment process that creates a running instance of the application: 1. Wildfly loads a `.ear` file that contains the Keep software. 2. Wildfly runs the software in that `.ear` file. If Keep is running and you can log in, it has been successfully deployed. However, if Wildfly cannot deploy Keep, the application will not run. If you think Keep is not running, check its deployment status: 1. On the Keep server, navigate to: `<installation directory>\Wildfly-<version>\standalone\deployments`. Appropriately substitute `<installation directory>` and `<version>`. The path to the `<installation directory>` varies depending on whether you chose the [default installation](/v1/docs/where-is-keep-installed#find-modified-installation-paths). 2. Locate `pdm_app_module.ear`. This file contains the main Keep components. 3. In the same directory, the extension of an accompanying file shows Keep’s deployment status. Locate this file and check the current deployment status. For example, `pdm_app_module.ear.deployed`. ![Files for a successful deployment of Keep.](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/successful deployment files.png) Keep deployment statuses: - `.deployed`: Keep was successfully deployed and is running. - `.deploying`: Wildfly is currently deploying the Keep application: - If the deployment succeeds, the file’s extension changes to `.deployed`. - If the deployment fails, the extension changes to `.undeployed` or `.failed`. - `.undeployed`: Wildfly has not deployed Keep. Before trying to restart Keep, you must complete further configuration steps. [Check the Keep logs](/v1/docs/read-keep-logs) for messages that identify the cause of the problem. Often, licensing issues cause this problem. If you require further assistance, contact [Lasernet Support](https://support.lasernetgroup.com/new-ticket). - `.failed`: Wildfly failed to deploy Keep. See [Troubleshoot Startup Issues](/v1/docs/check-the-lasernet-keep-deployment-status-and-troubleshoot-startup-issues#troubleshoot-startup-issues) to resolve common issues. ## Troubleshoot Startup Issues The following sections describe common startup issues and provide resolution steps: - [Keep Starts Before One or More of Its Dependencies](/v1/docs/check-the-lasernet-keep-deployment-status-and-troubleshoot-startup-issues#autoform-dm-starts-before-one-or-more-of-the-components-that-it-depends-on) - [A Port Conflict Occurs](/v1/docs/check-the-lasernet-keep-deployment-status-and-troubleshoot-startup-issues#autoform-dm-port-conflict) - [Keep Startup is Affected by a Firewall or Local Security Policy](/v1/docs/check-the-lasernet-keep-deployment-status-and-troubleshoot-startup-issues#autoform-dm-startup-is-affected-by-a-firewall-or-local-security-policy) If none of these issues is the cause of deployment failure, [check the Keep logs](/v1/docs/read-keep-logs) for messages that identify the root cause. If the logs do not help you to identify the cause, contact [Lasernet Support](https://support.lasernetgroup.com/new-ticket). ### Keep Starts Before One or More of Its Dependencies If Keep depends on an external software component that has not yet started when the application starts up, Wildfly will fail to deploy Keep. This can happen when the server is restarted. [Try manually restarting Keep](/v1/docs/check-the-lasernet-keep-deployment-status-and-troubleshoot-startup-issues#manually-restart-autoform-dm) to resolve this issue. ### A Port Conflict Occurs A port conflict can prevent Keep from starting. Use your preferred tools and approach to investigate the current port allocation for Keep and other software. If a conflict is found, take appropriate steps. ### Keep Startup is Affected by a Firewall or Local Security Policy Firewall configuration or a local security policy can prevent Keep from binding its configured port. This will prevent Keep from starting. To resolve this issue, follow these steps: 1. Locate the Keep `standalone.xml` file. It is in `<installation directory>\Wildfly-<version>\standalone\configuration` file (appropriately substitute `<installation directory>` and `<version>`). The `standalone.xml` file is in the same directory as `node.properties`. 2. Open the file and locate the following lines: ```xml                 ... ``` 3. In the `<host name="default-host" alias="localhost">` line, change `localhost` to your server’s host name. 4. Save `standalone.xml`. 5. [Restart Keep](/v1/docs/check-the-lasernet-keep-deployment-status-and-troubleshoot-startup-issues#manually-restart-autoform-dm). ## Manually Restart Keep After you have taken the recommended troubleshooting steps, restart Keep. If Keep is running as a Windows service, follow these steps to restart it: 1. Open the Windows **Services** window. 2. Locate the Keep service. For example, **Keep Server 11.1 - Standalone [Production]**. The service name contains the Keep version number and includes the corresponding Keep node name in square brackets. The node name is entered during installation and is typically the name of the relevant service. 3. Click **Restart Service**. > [!NOTE] > Note > > The restart can take up to 10 minutes.