> For the complete documentation index, see [llms.txt](https://docs.itconductor.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.itconductor.com/user-guide/diagnostics/running-itconductor-gateway-from-cli.md).

# Running IT-Conductor Gateway from CLI

### Problem

If the IT-Conductor Gateway encounters a problem when starting from the IT-Conductor Gateway GUI, or when the service won't run with errors such as Error 1067 or Service Start Error, perform the troubleshooting guide discussed below.

![Figure 1: Error 1067 Message](https://377464071-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXhp08OmU8050PePmMgDt%2Fuploads%2FjyS9mo5gyHIHqJiBuXpQ%2F329285654?alt=media)

![Figure 2: Service Start Error](https://377464071-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXhp08OmU8050PePmMgDt%2Fuploads%2FnGbxUpL6F02eAaiQaYoM%2F329252871?alt=media)

### Troubleshooting <a href="#runningitcgatewayfromcommandline-solution" id="runningitcgatewayfromcommandline-solution"></a>

1. Make sure to check that the IT-Conductor Gateway can test connect successfully by launching IT-Conductor Gateway.

![Figure 3: Gateway Configuration (Windows)](https://377464071-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXhp08OmU8050PePmMgDt%2Fuploads%2FFcQV8I46LS9OrFqmdbnG%2F329056270?alt=media)

![Figure 4: IT-Conductor Connection Test](https://377464071-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXhp08OmU8050PePmMgDt%2Fuploads%2FjeqY6RqZiFXg2ZkS9YJm%2F329252879?alt=media)

2. If a successful connection was tested, run the IT-Conductor Gateway in manual command line mode to troubleshoot any error messages further.

* cd \<ITC Gateway Installation Directory> (e.g. cd C:\program files\it-conductor\agent)
* Start the gateway: **jre\bin\java -Xmx1000m -Ditconductor.diag=true -jar lib\Gateway.jar**
* Navigate to **Management > Resources > Gateways** and check the Gateway logs to verify if it runs successfully or is still with errors.
* Check **Heartbeat Age** which should be small (in seconds) if connected and working. If not, check the logs and [report the issue to the Support Team](/references/support.md).

![Figure 5: Gateway Log Icon](https://377464071-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXhp08OmU8050PePmMgDt%2Fuploads%2FJB0LFg42u48vl5dzGbPt%2F329056282?alt=media)

### Related Information

* [IT-Conductor Gateway Setup for AWS](/user-guide/setup/gateway-setup/aws.md)
* [IT-Conductor Gateway Setup for Linux x64](/user-guide/setup/gateway-setup/it-conductor-gateway-setup-for-linux.md)
* [IT-Conductor Gateway Setup for Windows x64](/user-guide/setup/gateway-setup/windows-x64.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.itconductor.com/user-guide/diagnostics/running-itconductor-gateway-from-cli.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.