# Unable to connect to SFTP-server

**URL:** <https://community.n8n.io/t/unable-to-connect-to-sftp-server/118585>\
**Category:** Questions\
**Created:** [May 21, 2025, 2:20pm UTC](https://community.n8n.io/t/unable-to-connect-to-sftp-server/118585 "2025-05-21T14:20:24Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![rens](https://avatars.discourse-cdn.com/v4/letter/r/2bfe46/32.png) [@rens](https://community.n8n.io/u/rens)\
**Post date:** [May 21, 2025, 2:20pm UTC](https://community.n8n.io/t/unable-to-connect-to-sftp-server/118585/1 "2025-05-21T14:20:25Z")

</div>

## Describe the problem/error/question

I try to add a new SFTP credential. In FileZilla I can successfully connect to the SFTP-servers with the credentials that I use. However, when entering the credentials in n8n and click “Save”, the button changes to “Testing” and stays stuck like that. In the console I can see multiple error trying to connect, but unfortunately I cannot make sense of them.

Is this a bug in n8n or does the SFTP-server block the connection (no IP-whitelisting is needed, so it must be something else then)? Any way to find out how to solve this error?

Any help is appreciated.

## What is the error message (if any)?

I see the follow error messages in the console:

- `POST https://tixly.app.n8n.cloud/rest/credentials/test 500 (Internal Server Error)`
- `[Vue warn]: Error in https://vuejs.org/error-reference/#runtime-5: "ResponseError: end: No SFTP connection available" (found in <SaveButton>)`
- `POST https://o1420875.ingest.us.sentry.io/api/4503960699273216/envelope/?sentry_key=c458d7c5a07ff107dc42f25f6ce4bcdb&sentry_version=7&sentry_client=sentry.javascript.vue%2F8.33.1 403 (Forbidden)`
- `POST https://o1420875.ingest.us.sentry.io/api/4503960699273216/envelope/?sentry_key=c458d7c5a07ff107dc42f25f6ce4bcdb&sentry_version=7&sentry_client=sentry.javascript.vue%2F8.33.1 403 (Forbidden)`

## Information on your n8n setup

- **n8n version:** 1.93.0
- **Running n8n via (Docker, npm, n8n cloud, desktop app):** n8n cloud

---

<div class="post-metadata">

**Author:** ![Gallo\_AIA](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/gallo_aia/32/69059_2.png) [@Gallo\_AIA](https://community.n8n.io/u/Gallo_AIA)\
**Post date:** [May 21, 2025, 2:31pm UTC](https://community.n8n.io/t/unable-to-connect-to-sftp-server/118585/2 "2025-05-21T14:31:59Z")

</div>

Hello @rens welcome here!

The error you’re seeing (`end: No SFTP connection available`) combined with the “Testing” button getting stuck usually means that n8n couldn’t establish the SFTP connection, even before trying credentials.

Try to do these points:

- Double-check the host/port/auth method
- Try outside of n8n (CLI or FileZilla) to confirm the SFTP server is reachable
- If it works elsewhere but not in n8n.cloud, the server may block traffic from cloud environments

tell me every test or further details.  
Thanks

---

<div class="post-metadata">

**Author:** ![rens](https://avatars.discourse-cdn.com/v4/letter/r/2bfe46/32.png) [@rens](https://community.n8n.io/u/rens)\
**Post date:** [May 21, 2025, 2:52pm UTC](https://community.n8n.io/t/unable-to-connect-to-sftp-server/118585/3 "2025-05-21T14:52:28Z")

</div>

Thank you @Gallo_AIA ,  
I can successfully connect through the same port and with the same credentials through FileZilla. So then it must be the SFTP server blocking the request.

Any idea what to tell the provider of the SFTP-server that they need to change to allow the connection from n8n cloud?

---

<div class="post-metadata">

**Author:** ![Gallo\_AIA](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/gallo_aia/32/69059_2.png) [@Gallo\_AIA](https://community.n8n.io/u/Gallo_AIA)\
**Post date:** [May 21, 2025, 5:18pm UTC](https://community.n8n.io/t/unable-to-connect-to-sftp-server/118585/4 "2025-05-21T17:18:11Z")

</div>

Ehy @rens,

ask to SFTP Provider to check firewall or fail2ban rules and allow traffic from the IP ranges used by n8n Cloud. Unfortunately idk if you can reach the IP of n8n cloud.

---

<div class="post-metadata">

**Author:** ![paryupaa](https://avatars.discourse-cdn.com/v4/letter/p/ba9def/32.png) [@paryupaa](https://community.n8n.io/u/paryupaa)\
**Post date:** [May 26, 2025, 8:06am UTC](https://community.n8n.io/t/unable-to-connect-to-sftp-server/118585/5 "2025-05-26T08:06:28Z")

</div>

I have the same problem with the SFTP node. The hoster is saying the IP address is not banned.

---

<div class="post-metadata">

**Author:** ![Steph\_Sjostrom](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/steph_sjostrom/32/61469_2.png) [@Steph\_Sjostrom](https://community.n8n.io/u/Steph_Sjostrom)\
**Post date:** [July 3, 2025, 11:02pm UTC](https://community.n8n.io/t/unable-to-connect-to-sftp-server/118585/6 "2025-07-03T23:02:38Z")

</div>

I am having the same problem. I went back and forth with the n8n AI Assistant verifying everything (credentials, whitelisting, ciphers etc.) until it ran out of ideas.

The SFTP server is a basic setup that we can connect to from any where else with no issues.

Has anyone been able to connect to a SFTP server from n8n successfully?

---

<div class="post-metadata">

**Author:** ![rens](https://avatars.discourse-cdn.com/v4/letter/r/2bfe46/32.png) [@rens](https://community.n8n.io/u/rens)\
**Post date:** [July 4, 2025, 2:07pm UTC](https://community.n8n.io/t/unable-to-connect-to-sftp-server/118585/7 "2025-07-04T14:07:49Z")

</div>

Unfortunately, I still have not been able to solve this issue in n8n. The provider of the SFTP server confirms that there are no firewall rules and the IP addresses are not blocked. I can reach the SFTP server from my local computer or from other platforms, but not n8n. There are also no clear error messages in n8n so it is completely unclear what the issue is.

My current workaround is putting a file on another SFTP server that I **can** reach from n8n (Hetzner storagebox). And then I use [Make.com](http://Make.com) to transfer the file from that SFTP server to the final SFTP server. [Make.com](http://Make.com) has no issues with reaching both SFTP servers.

---

<div class="post-metadata">

**Author:** ![lvl99](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/lvl99/32/98160_2.png) [@lvl99](https://community.n8n.io/u/lvl99)\
**Post date:** [July 25, 2025, 9:49am UTC](https://community.n8n.io/t/unable-to-connect-to-sftp-server/118585/8 "2025-07-25T09:49:56Z")

</div>

I’ve been having issues with connecting to SFTP server as well. In my case, I can connect to the server using self-hosted/locally run n8n, however I cannot with n8n Cloud: [Issue with FTP/SFTP list files on Cloud vs local community version](http://community.n8n.io/t/issue-with-ftp-sftp-list-files-on-cloud-vs-local-community-version/145809)

For some reason with n8n Cloud, it is returning what looks like an old cached version of the SFTP directory. I cannot for the life of me figure out how to get the uncached/live SFTP server directory list on n8n Cloud.

---

<div class="post-metadata">

**Author:** ![Il\_Bardo](https://avatars.discourse-cdn.com/v4/letter/i/839c29/32.png) [@Il\_Bardo](https://community.n8n.io/u/Il_Bardo)\
**Post date:** [August 8, 2025, 12:56pm UTC](https://community.n8n.io/t/unable-to-connect-to-sftp-server/118585/9 "2025-08-08T12:56:25Z")

</div>

I was having the same issue trying to connect with user and password.

The Credentials window automatically fills the fields for the Private Key and the Passphrase with dots, even if nothing was written in them.

 ![dots](https://europe1.discourse-cdn.com/n8n/original/3X/0/e/0eab747100b1f08099f34985d1bafffe0070fa25.jpeg)

Trying everything, I deleted the content of both fields, and the connection worked immediately.

---

<div class="post-metadata">

**Author:** ![system](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/system/32/195824_2.png) [@system](https://community.n8n.io/u/system)\
**Post date:** [December 9, 2025, 7:44am UTC](https://community.n8n.io/t/unable-to-connect-to-sftp-server/118585/11 "2025-12-09T07:44:25Z")

</div>

Closed on December 9, 2025, 7:44am UTC

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
