> 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/knowledge-base/troubleshooting-articles/ssh-connectivity-issues-with-cyberark-sia-and-vpn.md).

# SSH connectivity issues with CyberArk SIA and VPN

Fix SSH connection failures over CyberArk SIA while connected to a VPN by disabling client IP enforcement for MFA caching in CyberArk SIA settings.

Learn how to troubleshoot issues when using SSH over CyberArk Secure Identity Access (SIA), specifically in environments where you're connecting via VPN.

### Problem

It's not possible to launch SSH connections while connected to a VPN and using CyberArk SIA for authentication. This issue occurs because the IP address used to perform the MFA challenge is different from the IP address used to launch the SSH session.

### Solution

To resolve this issue, disable client IP enforcement for MFA caching in the CyberArk SIA settings. This allows the system to rely on other factors than the client IP for MFA session continuity.

1. Log in to the CyberArk SIA Admin Portal.
2. Navigate to **SIA** – **Settings** – **Client IP enforcement for MFA caching.**
3. Disable 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/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.