> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/on-premise/on-premise/how-to-guide/maintenance/restarting-instance.md).

# Restarting instance

Restart Navixy on-premise on Linux using the restart-navixy command or on Windows via the services.msc console to manage Windows NT services.

Restarting the Navixy platform may be necessary in certain situations such as troubleshooting, configuration changes, or to verify the license, especially after access has been previously suspended due to non-payment.

If you need to perform any of the tasks mentioned above, restarting the Navixy platform backend is usually sufficient. This backend consists of three Java services, namely the "api-server", "sms-server", and "tcp-server".

After restarting the services, it may take 60-90 seconds for them to start and stabilize. Therefore, it is recommended to wait for this period before checking the platform's operation.

## Restarting on Linux

To restart the Navixy instance on on Linux, just run the following command:

```
restart-navixy
```

This command will execute a script that restarts the backend services. The process is fully automated, so all you need to do is wait for it to complete.

You can also restart any of the three backend servers separately. To do this, use the following commands:

```
systemctl restart api-server
systemctl restart sms-server
systemctl restart tcp-server
```

## Restarting on Windows

If Navixy instance is installed on Windows, the platform backend services will work as regular Windows NT services. To access the services, open the **services.msc** snap-in, and you will find three Navixy services in the list:

* Navixy api-server
* Navixy sms-server
* Navixy tcp-server

To restart any required service or all of them, simply right-click on the corresponding service(s) and select "Restart".

![](https://4021216648-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkUnMmePH99SsdChtqqu7%2Fuploads%2Fgit-blob-e1ea471f45102bdf28847316959cf8426b3e7867%2Fimage-20230810-134010.png?alt=media)


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://navixy.com/docs/on-premise/on-premise/how-to-guide/maintenance/restarting-instance.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 `build a script that syncs our docs to a CMS` 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.