> For the complete documentation index, see [llms.txt](https://docs.synteq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.synteq.com/networking/troubleshooting-the-network/troubleshooting-no-connection.md). # Troubleshooting no connection ## Common issues At Synteq, we have a few most common issues that lead to no connection on your VPS/dedicated server: ### Incorrect network configuration The most common one is incorrect network configuration, or incorrect formatting. We have a very extensive section of tutorials that explains the correct configuration, as well as formatting, which can be found here: [Manual configuration](/networking/network-configuration/manual-configuration.md) ### Random Unexplained Issues The second most common cause of connection loss stems from unexpected system issues, which can range from installed software conflicts to corrupted system files or kernel panics. The vast majority of those can be fixed with a simple reboot from the respective management panels. \[[Metal](https://metal.crunchbits.com/) / [Virt](https://virt.crunchbits.com/)] ### Incorrect interface name The last most common issue that our clients encounter is partway due to incorrect configuration. You can check the correct interface name via the following command: ``` ip link show ``` And in the output looking for an interface that has `state UP`: ``` 2: ens18: mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether HIDDENMACADDRESS brd ff:ff:ff:ff:ff:ff altname enp0s18 ``` Then exchanging the interface name within your network configuration to the one from the command above, and restarting the networking process, or rebooting your service. ### Other If you've checked all of the above common causes, and are still encountering issues, don't hesitate to reach out to us via the buttons on the right top! --- # 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.synteq.com/networking/troubleshooting-the-network/troubleshooting-no-connection.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.