> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/rdm/da/knowledge-base/troubleshooting-articles/ssh-connectivity-issues-with-cyberark-sia-and-vpn.md).

# Forbindelsesproblemer med SSH, CyberArk SIA og VPN

Ret SSH-forbindelsesfejl via CyberArk SIA, mens De er forbundet til en VPN, ved at deaktivere håndhævelse af klient-IP for MFA-cache i indstillingerne for CyberArk SIA.

Lær, hvordan De fejlfinder problemer ved brug af SSH via CyberArk Secure Identity Access (SIA), især i miljøer, hvor De opretter forbindelse via VPN.

### Problem

Det er ikke muligt at starte SSH-forbindelser, mens De er forbundet til en VPN og bruger CyberArk SIA til godkendelse. Problemet opstår, fordi den IP-adresse, der bruges til MFA-udfordringen, er en anden end den IP-adresse, der bruges til at starte SSH-sessionen.

### Løsning

For at løse problemet skal De deaktivere håndhævelse af klient-IP for MFA-cache i indstillingerne for CyberArk SIA. Det gør det muligt for systemet at basere sig på andre faktorer end klientens IP-adresse for at bevare MFA-sessionen.

1. Log på CyberArk SIA Admin Portal.
2. Gå til **SIA** – **Settings** – **Client IP enforcement for MFA caching.**
3. Deaktiver SSH.


---

# 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.devolutions.net/rdm/da/knowledge-base/troubleshooting-articles/ssh-connectivity-issues-with-cyberark-sia-and-vpn.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.