# File upload fails with FTP reply code 551

**URL:** <https://community.hubspot.com/t/file-upload-fails-with-ftp-reply-code-551/11885>\
**Category:** APIs & Integrations\
**Created:** [March 2, 2017, 10:59am UTC](https://community.hubspot.com/t/file-upload-fails-with-ftp-reply-code-551/11885 "2017-03-02T10:59:39Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![system](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/system/32/124_2.png) [@system](https://community.hubspot.com/u/system)\
**Post date:** [March 2, 2017, 10:59am UTC](https://community.hubspot.com/t/file-upload-fails-with-ftp-reply-code-551/11885/1 "2017-03-02T10:59:39Z")

</div>

At the moment, I cannot upload **any** file to the Hubspot FTP server. The server always replies with a 551 reply code, which, according to [536, 550, 551, 552, 553 FTP Response Codes | SolarWinds](http://www.serv-u.com/kb/1534/551-FTP-Reply-Code), means the following:

_A 551 reply code may be sent in response to any command requiring the server to store information locally. It is a permanent negative reply, which means the client is discouraged from sending the command again since the server will respond with the same reply code. It is only applicable **when the page file structure is being used** (through a “STRU P” command)._

I am using FTP since decades and didn’t even know that something like a “file structure” even existed. According to the STRU command description, the file structure can be “page”, “record”, or “file”, with the latter being supposed to be the default.

I am using FileZilla for the upload, which has worked successfully before. According to the FilleZilla log, it does not send the STRU command, so I would say the error is on the server side; perhaps it maintains a wrong default.

(One day I’d like to discuss the question why Hubspot uses such an outdated tool like FTP for file upload and does not support something much more usable like _rsync_. However, that’s a totally different question – though a very valid and important one! Customer satisfaction, you know!)

---

<div class="post-metadata">

**Author:** ![3PETE](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/3pete/32/61905_2.png) [@3PETE](https://community.hubspot.com/u/3PETE)\
**Post date:** [March 2, 2017, 2:31pm UTC](https://community.hubspot.com/t/file-upload-fails-with-ftp-reply-code-551/11885/2 "2017-03-02T14:31:43Z")

</div>

[@RainerKlute](https://community.hubspot.com/u/rainerklute) was this the precursor post to your more recent one? Regarding the bad TLS handshake?

---

<div class="post-metadata">

**Author:** ![system](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/system/32/124_2.png) [@system](https://community.hubspot.com/u/system)\
**Post date:** [March 2, 2017, 2:42pm UTC](https://community.hubspot.com/t/file-upload-fails-with-ftp-reply-code-551/11885/3 "2017-03-02T14:42:42Z")

</div>

No, I think this one is completely unrelated.

(I’ll get back to you on the other one in a minute …)

---

<div class="post-metadata">

**Author:** ![system](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/system/32/124_2.png) [@system](https://community.hubspot.com/u/system)\
**Post date:** [March 2, 2017, 2:58pm UTC](https://community.hubspot.com/t/file-upload-fails-with-ftp-reply-code-551/11885/4 "2017-03-02T14:58:19Z")

</div>

By the way, to rule out any relation to the [TLS handshake issue](https://integrate.hubspot.com/t/data-stream-ssl-tls-handshake-hangs-and-fails-when-uploading/3044/3) which I encountered yesterday: While I couldn’t upload files with _curl_ due to the handshake issue, I still was able to do so with _Filezilla_. I uploaded a few files this morning at about 08:30 UTC, but shortly after that no more upload was possible with _Filezilla_.

---

<div class="post-metadata">

**Author:** ![3PETE](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/3pete/32/61905_2.png) [@3PETE](https://community.hubspot.com/u/3PETE)\
**Post date:** [March 2, 2017, 3:14pm UTC](https://community.hubspot.com/t/file-upload-fails-with-ftp-reply-code-551/11885/5 "2017-03-02T15:14:30Z")

</div>

[@RainerKlute](https://community.hubspot.com/u/rainerklute) A 5xx error means it is server side. I’ll reach out internally and see if there are any known issues going on with FTP.

---

<div class="post-metadata">

**Author:** ![system](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/system/32/124_2.png) [@system](https://community.hubspot.com/u/system)\
**Post date:** [March 2, 2017, 5:14pm UTC](https://community.hubspot.com/t/file-upload-fails-with-ftp-reply-code-551/11885/6 "2017-03-02T17:14:51Z")

</div>

This also works again after you restarted your FTP services. Please implement a permanent solution! Thanks!

---

<div class="post-metadata">

**Author:** ![3PETE](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/3pete/32/61905_2.png) [@3PETE](https://community.hubspot.com/u/3PETE)\
**Post date:** [March 2, 2017, 6:02pm UTC](https://community.hubspot.com/t/file-upload-fails-with-ftp-reply-code-551/11885/7 "2017-03-02T18:02:19Z")

</div>

[@RainerKlute](https://community.hubspot.com/u/rainerklute) I’m glad it is working again. Sorry for the inconvenience.

---

<div class="post-metadata">

**Author:** ![jameshollands](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/jameshollands/32/53612_2.png) [@jameshollands](https://community.hubspot.com/u/jameshollands)\
**Post date:** [May 1, 2018, 2:48pm UTC](https://community.hubspot.com/t/file-upload-fails-with-ftp-reply-code-551/11885/8 "2018-05-01T14:48:57Z")

</div>

I am struggling with this now. Is there a fix for this?
