Uploading Files Via Rclone Leads to Errors
Posted: Sat Apr 11, 2026 9:11 pm
Hello,
Been with you guys awhile on the 50TB plan. For a few months there, I really did not try to upload anything to Blomp, as almost every file failed, it was soooooooooooooooooooo slow, its like your server was running on dial up.
I tried it lately, and I am happy to report that the speed of the server is great ( upload wise ). However, 2 things are happening. I am only uploading 3 files at a time, they are large files, so the swift backend you use has to split them up into chunks to make 1 big file. Here is where the errors happen. From my point of view, uploading multiple 8GB files at once, once the server starts splitting them up, and then of course the other files are still uploading, the swift action of splitting the files will error out. Every time I upload a folder, no matter the size, there are ALWAYS swift errors.
I am also getting notices about hitting the "pacer limit". I think the two in combo, the server trying to split the file in the backround + the continuous uploads of other files at the same time is causing me to hit some time of artificial pacer limit, and would like to know why this is, or how to make it stop.
Literally, every, single, time, I upload a directory, I have 20 - 45 errors ( mainly due to the swift chunking large files ).
For example;
2026/04/11 19:20:35 DEBUG : pacer: low level retry 1/1 (error HTTP Error: 503: 503 Service Unavailable)
2026/04/11 19:20:35 DEBUG : pacer: Rate limited, increasing sleep to 10ms
2026/04/11 19:20:35 DEBUG : file.mkv: Received error: HTTP Error: 503: 503 Service Unavailable - low level retry 0/15
2nd example;
2026/04/11 18:57:48 DEBUG : pacer: Rate limited, increasing sleep to 20ms
2026/04/11 18:57:48 DEBUG : file.mkv: Received error: Put "http://swiftproxy.acs.ai.net:8080/v1/AU ... ACTED".mkv": write tcp 192.168.4.238:51292->205.134.187.66:8080: wsasend: An existing connection was forcibly closed by the remote host. - low level retry 0/15
Been with you guys awhile on the 50TB plan. For a few months there, I really did not try to upload anything to Blomp, as almost every file failed, it was soooooooooooooooooooo slow, its like your server was running on dial up.
I tried it lately, and I am happy to report that the speed of the server is great ( upload wise ). However, 2 things are happening. I am only uploading 3 files at a time, they are large files, so the swift backend you use has to split them up into chunks to make 1 big file. Here is where the errors happen. From my point of view, uploading multiple 8GB files at once, once the server starts splitting them up, and then of course the other files are still uploading, the swift action of splitting the files will error out. Every time I upload a folder, no matter the size, there are ALWAYS swift errors.
I am also getting notices about hitting the "pacer limit". I think the two in combo, the server trying to split the file in the backround + the continuous uploads of other files at the same time is causing me to hit some time of artificial pacer limit, and would like to know why this is, or how to make it stop.
Literally, every, single, time, I upload a directory, I have 20 - 45 errors ( mainly due to the swift chunking large files ).
For example;
2026/04/11 19:20:35 DEBUG : pacer: low level retry 1/1 (error HTTP Error: 503: 503 Service Unavailable)
2026/04/11 19:20:35 DEBUG : pacer: Rate limited, increasing sleep to 10ms
2026/04/11 19:20:35 DEBUG : file.mkv: Received error: HTTP Error: 503: 503 Service Unavailable - low level retry 0/15
2nd example;
2026/04/11 18:57:48 DEBUG : pacer: Rate limited, increasing sleep to 20ms
2026/04/11 18:57:48 DEBUG : file.mkv: Received error: Put "http://swiftproxy.acs.ai.net:8080/v1/AU ... ACTED".mkv": write tcp 192.168.4.238:51292->205.134.187.66:8080: wsasend: An existing connection was forcibly closed by the remote host. - low level retry 0/15