> For the complete documentation index, see [llms.txt](https://docs.termius.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.termius.com/help-center/troubleshooting/connection-drops-after-a-successful-authentication.md).

# Connection drops after a successful authentication

In some cases, the session may disconnect immediately after authentication or a few seconds later.

One possible cause is how the SSH server handles OS detection or shell history fetching for terminal autocomplete.

Some Termius features use SSH `exec` channels by running commands right after the connection is established. You can confirm this in the connection log by looking for the `⚙️ Executing command` entry near the end.

If that is the cause, disable the features that rely on SSH `exec` channels.

{% tabs %}
{% tab title="Desktop" %}
Open **Termius** → **Settings** → **Terminal** and disable:

* Autocomplete
* Import shell history
* Detect OS
  {% endtab %}

{% tab title="Mobile" %}
Open **Termius** → **Profile** → **Settings** and disable:

* Import command history
* Detect Host Operating System
  {% endtab %}
  {% endtabs %}


---

# 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.termius.com/help-center/troubleshooting/connection-drops-after-a-successful-authentication.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.