I have been trying to report an issue related to a backup file which is bigger as the 5MB. Following https://community.safe.com/s/article/upload-a-file-to-the-safe-software-support-ftp I have tried to upload the respective file through the given `curl` command. But whatever I try, I keep getting "Failed FTP upload: 553".
I tried both zipped and unzipped, where the zipped file is around 6GB. Is there anything I can do to overcome this and continue with problem report?
Hello @smol , sorry to hear you are having problems reporting an issue. Though the file you are uploading is incredibly large, I don't think the size that's causing the failure. However, FTP doesn't like file names that have special characters, symbols or spaces in it.... I suggest removing these, if present, and trying again!
Hope this helps,
Kailin.
One thing to look at is the max file size tomcat (and IIS if you're routing through IIS) will accept
Hello @smol , sorry to hear you are having problems reporting an issue. Though the file you are uploading is incredibly large, I don't think the size that's causing the failure. However, FTP doesn't like file names that have special characters, symbols or spaces in it.... I suggest removing these, if present, and trying again!
Hope this helps,
Kailin.
Hello @kailinatsafe , thanks for the fast response. I tried with "test.zip", which causes the same issue. I even tried it with a UUID.
The following verbose result is produced:
curl -v -T test.zip ftp://ftp.safe.com/incoming
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Trying 52.37.1.147...
* TCP_NODELAY set
* Connected to ftp.safe.com (52.37.1.147) port 21 (#0)
< 220 (vsFTPd 3.0.2)
> USER anonymous
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0< 331 Please specify the password.
> PASS ftp@example.com
< 230 Login successful.
> PWD
< 257 "/"
* Entry path is '/'
> EPSV
* Connect data stream passively
* ftp_perform ends with SECONDARY: 0
< 229 Entering Extended Passive Mode (|||30058|).
* Trying 52.37.1.147...
* TCP_NODELAY set
* Connecting to 52.37.1.147 (52.37.1.147) port 30058
* Connected to ftp.safe.com (52.37.1.147) port 21 (#0)
> TYPE I
0 0 0 0 0 0 0 0 --:--:-- 0:00:01 --:--:-- 0< 200 Switching to Binary mode.
> STOR incoming
< 553 Could not create file.
* Failed FTP upload: 553
* Remembering we are in dir ""
* Uploaded unaligned file size (0 out of 5913803516 bytes)
0 0 0 0 0 0 0 0 --:--:-- 0:00:01 --:--:-- 0
* Connection #0 to host ftp.safe.com left intact
curl: (25) Failed FTP upload: 553
> QUIT
< 221 Goodbye.
* Closing connection 0I am running on MacOs, disabled firewall, chowned the file to 777, running as `sudo` all resulting in the same problem.
Hello @kailinatsafe , thanks for the fast response. I tried with "test.zip", which causes the same issue. I even tried it with a UUID.
The following verbose result is produced:
curl -v -T test.zip ftp://ftp.safe.com/incoming
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Trying 52.37.1.147...
* TCP_NODELAY set
* Connected to ftp.safe.com (52.37.1.147) port 21 (#0)
< 220 (vsFTPd 3.0.2)
> USER anonymous
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0< 331 Please specify the password.
> PASS ftp@example.com
< 230 Login successful.
> PWD
< 257 "/"
* Entry path is '/'
> EPSV
* Connect data stream passively
* ftp_perform ends with SECONDARY: 0
< 229 Entering Extended Passive Mode (|||30058|).
* Trying 52.37.1.147...
* TCP_NODELAY set
* Connecting to 52.37.1.147 (52.37.1.147) port 30058
* Connected to ftp.safe.com (52.37.1.147) port 21 (#0)
> TYPE I
0 0 0 0 0 0 0 0 --:--:-- 0:00:01 --:--:-- 0< 200 Switching to Binary mode.
> STOR incoming
< 553 Could not create file.
* Failed FTP upload: 553
* Remembering we are in dir ""
* Uploaded unaligned file size (0 out of 5913803516 bytes)
0 0 0 0 0 0 0 0 --:--:-- 0:00:01 --:--:-- 0
* Connection #0 to host ftp.safe.com left intact
curl: (25) Failed FTP upload: 553
> QUIT
< 221 Goodbye.
* Closing connection 0I am running on MacOs, disabled firewall, chowned the file to 777, running as `sudo` all resulting in the same problem.
@smol , could you try switching the transfer type and trying to upload individually as both - Binary & Ascii. (Done through: Filezilla -> Transfer -> Transfer Type). Let me know if you have any success with either type! Thanks in advance.
Hello @kailinatsafe , thanks for the fast response. I tried with "test.zip", which causes the same issue. I even tried it with a UUID.
The following verbose result is produced:
curl -v -T test.zip ftp://ftp.safe.com/incoming
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Trying 52.37.1.147...
* TCP_NODELAY set
* Connected to ftp.safe.com (52.37.1.147) port 21 (#0)
< 220 (vsFTPd 3.0.2)
> USER anonymous
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0< 331 Please specify the password.
> PASS ftp@example.com
< 230 Login successful.
> PWD
< 257 "/"
* Entry path is '/'
> EPSV
* Connect data stream passively
* ftp_perform ends with SECONDARY: 0
< 229 Entering Extended Passive Mode (|||30058|).
* Trying 52.37.1.147...
* TCP_NODELAY set
* Connecting to 52.37.1.147 (52.37.1.147) port 30058
* Connected to ftp.safe.com (52.37.1.147) port 21 (#0)
> TYPE I
0 0 0 0 0 0 0 0 --:--:-- 0:00:01 --:--:-- 0< 200 Switching to Binary mode.
> STOR incoming
< 553 Could not create file.
* Failed FTP upload: 553
* Remembering we are in dir ""
* Uploaded unaligned file size (0 out of 5913803516 bytes)
0 0 0 0 0 0 0 0 --:--:-- 0:00:01 --:--:-- 0
* Connection #0 to host ftp.safe.com left intact
curl: (25) Failed FTP upload: 553
> QUIT
< 221 Goodbye.
* Closing connection 0I am running on MacOs, disabled firewall, chowned the file to 777, running as `sudo` all resulting in the same problem.
It seems that simply using the FileZilla client worked. Even with the Transfer Type of "auto".
Using the `curl` binary option also resulted in the same result, so it might be save to assume that curl (my version atleast, 7.64.1) has some issues with connecting to the server. Maybe we can update the documentation of this after some further testing, as both the MacOS approach and the Linux approach of https://community.safe.com/s/article/upload-a-file-to-the-safe-software-support-ftp did not work?
Thanks for the help :) Btw, you can delete the files starting with "smol" as this was just uploaded for testing purposes.
Hello @kailinatsafe , thanks for the fast response. I tried with "test.zip", which causes the same issue. I even tried it with a UUID.
The following verbose result is produced:
curl -v -T test.zip ftp://ftp.safe.com/incoming
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Trying 52.37.1.147...
* TCP_NODELAY set
* Connected to ftp.safe.com (52.37.1.147) port 21 (#0)
< 220 (vsFTPd 3.0.2)
> USER anonymous
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0< 331 Please specify the password.
> PASS ftp@example.com
< 230 Login successful.
> PWD
< 257 "/"
* Entry path is '/'
> EPSV
* Connect data stream passively
* ftp_perform ends with SECONDARY: 0
< 229 Entering Extended Passive Mode (|||30058|).
* Trying 52.37.1.147...
* TCP_NODELAY set
* Connecting to 52.37.1.147 (52.37.1.147) port 30058
* Connected to ftp.safe.com (52.37.1.147) port 21 (#0)
> TYPE I
0 0 0 0 0 0 0 0 --:--:-- 0:00:01 --:--:-- 0< 200 Switching to Binary mode.
> STOR incoming
< 553 Could not create file.
* Failed FTP upload: 553
* Remembering we are in dir ""
* Uploaded unaligned file size (0 out of 5913803516 bytes)
0 0 0 0 0 0 0 0 --:--:-- 0:00:01 --:--:-- 0
* Connection #0 to host ftp.safe.com left intact
curl: (25) Failed FTP upload: 553
> QUIT
< 221 Goodbye.
* Closing connection 0I am running on MacOs, disabled firewall, chowned the file to 777, running as `sudo` all resulting in the same problem.
@smol , you are most welcome! Glad you were able to upload successfully. All files starting with "smol" have been deleted from FTP. We'll look into reviewing the article, thank you.