> For the complete documentation index, see [llms.txt](https://legacy.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://legacy.docs.synteq.com/system-administration/ssh-keys/how-to-ssh-into-your-server-using-ssh-keys.md).

# How to SSH into your server using SSH keys

## Why should you use SSH keys? 

SSH keys provide a more secure authentication method than passwords by using cryptographic key pairs instead of text-based credentials. They're virtually impossible to brute-force, eliminate the risk of password interception, and allow you to authenticate without typing a password each time. Most importantly, SSH keys protect your server from automated attacks that constantly try to guess common passwords.

## How to SSH into a server with SSH keys?

### 1. Make sure your SSH keys are in the correct place

Start by going to the following folder on Windows: `C:\Users\YourUsername.ssh\`

And in there make sure that you have 3 files in there:

* KEY
* KEY.pub
* config

If you do not have a config file, then please create one with the following content:

```
Host *
    IdentityFile ~/.ssh/your_key_name
    IdentitiesOnly yes
```

### 2. SSH into your server

Afterward, you should be able to just SSH into your server using the following command:

```
ssh root@YOUR-SERVER-IP
```


---

# 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://legacy.docs.synteq.com/system-administration/ssh-keys/how-to-ssh-into-your-server-using-ssh-keys.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.