> 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/setup/gateway-setup/it-conductor-gateway-restart-guide.md). # IT-Conductor Gateway Restart Guide A gateway restart may be required during maintenance, troubleshooting, or after configuration changes. You can restart the IT-Conductor Gateway using one of the following methods. #### Method 1: Restart from the Management UI 1. On the main menu go to Management → Resources → Gateways.

Figure 1: Gateways Option in Main Menu

2. Click the icon next to the gateway you wish to restart and click the **Request Restart** button.

Figure 2: Request Restart Option 1

3. The same button is also available by clicking on the gateway’s name → **Request Restart**

Figure 3: Request Restart Option 2

4. Wait a few minutes for the restart to complete. 5. Verify the gateway status by clicking on **Gateway's Name** → **Gateway Heartbeat** and enlarging the pop-up chart.

Figure 4a: Gateway Heartbeat

Figure 4b: Gateway Heartbeat Regulated

#### Method 2: Restart using commands (Linux Only) * Run the following commands on the gateway host: ``` sudo systemctl stop itconductor-gateway sudo systemctl start itconductor-gateway ``` * Run the following command to display the gateway’s state after restarting. ``` sudo systemctl status itconductor-gateway ``` #### Method 3: From the Configuration Utility (Windows Only) 1. Navigate to the directory where the JRE Gateway is installed. 2. Open the Configuration Utility. 3. Click the **Stop** icon to stop the gateway. 4. Once the gateway has stopped, click the **Start** icon to restart it.

Figure 5: Gateway Stop Start Option in the Configuration Utility (Windows)

--- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.itconductor.com/user-guide/setup/gateway-setup/it-conductor-gateway-restart-guide.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.