# Rebex backend: SSH → “Connect using SFTP/SCP” fails when connection uses proxy

**URL:** https://community.royalapps.com/t/rebex-backend-ssh-connect-using-sftp-scp-fails-when-connection-uses-proxy/2153
**Category:** Royal TS (for Windows)
**Created:** [October 13, 2025, 11:24am UTC](https://community.royalapps.com/t/rebex-backend-ssh-connect-using-sftp-scp-fails-when-connection-uses-proxy/2153 "2025-10-13T11:24:05Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![balu100](https://community.royalapps.com/letter_avatar_proxy/v4/letter/b/e19b73/32.png) [@balu100](https://community.royalapps.com/u/balu100)
#### Post date: [October 13, 2025, 11:24am UTC](https://community.royalapps.com/t/rebex-backend-ssh-connect-using-sftp-scp-fails-when-connection-uses-proxy/2153/1 "2025-10-13T11:24:05Z")

</div>

When using a proxy in an SSH connection (Rebex backend), the **Quick Actions → Connect using SFTP/SCP** buttons fail with a timeout.

The base SSH session connects fine through the proxy, but the secondary SFTP/SCP session never reaches the host.

Error shown:

```auto
Rebex.Net.SftpException: Connection attempt timed out.
Rebex.Net.ProxySocketException: Connection attempt timed out.

```

Environment

Royal TS for Windows v7.3.51009

Backend: Rebex

Proxy type: SOCKS5 (internal corporate proxy)

Secure Gateway: not used

Host reachable only through proxy

Same issue in reverse direction (SFTP → “Connect using SSH”)

Additional information

Using the **PuTTY backend** , SSH↔SFTP/SCP switching through the same SOCKS5 proxy works normally.

---

<div class="post-metadata">

### Author: ![stefan\_koell](https://community.royalapps.com/user_avatar/community.royalapps.com/stefan_koell/32/9_2.png) [@stefan\_koell](https://community.royalapps.com/u/stefan_koell)
#### Post date: [October 30, 2025, 1:30pm UTC](https://community.royalapps.com/t/rebex-backend-ssh-connect-using-sftp-scp-fails-when-connection-uses-proxy/2153/2 "2025-10-30T13:30:34Z")

</div>

Thanks for the bug report! The next release will have this fixed. Stay tuned…

Regards,  
Stefan