Backblaze B2 POST EOF errors

Help and Support
1

What is the problem you are having with rclone?

When using a Backblaze B2 config, I continually run into errors like: Failed to lsd with 2 errors: last error was: Post "https://api005.backblazeb2.com/b2api/v1/b2_list_file_names": EOF no matter the operation. I’ve tried using lsd/sync/copy and all run into POST . . . : EOF. Interestingly, when I use Backblaze as an S3 provider, it works as expected, so my keys and such are definitely correct. Also running curl -X POST https://api005.backblazeb2.com/b2api/v1/b2_list_file_names runs into curl: (35) TLS connect error: error:0A0003E8:SSL routines::reason(1000) which I’m not sure is related.

This problem has occurred on fresh Docker containers using rclone/rclone on a Synology NAS, a Fedora workstation laptop, and on Windows.

Run the command 'rclone version' and share the full output of the command.

/config/rclone # rclone version
rclone v1.71.1
- os/version: alpine 3.22.1 (64 bit)
- os/kernel: 4.4.302+ (x86_64)
- os/type: linux
- os/arch: amd64
- go/version: go1.25.1
- go/linking: static
- go/tags: none

Which cloud storage system are you using? (eg Google Drive)

Backblaze B2

The command you were trying to run (eg rclone copy /tmp remote:tmp)

rclone lsd -vvv backblaze:icloud-synology

Please run 'rclone config redacted' and share the full output. If you get command not found, please make sure to update rclone.

/config/rclone # rclone config redacted
[b2]
type = s3
location_constraint = us-east-005
provider = Other
region = us-east-005
secret_access_key = XXX
access_key_id = XXX
endpoint = s3.us-east-005.backblazeb2.com

[b2-crypt]
type = crypt
password = XXX
password2 = XXX
remote = b2:icloud-synology

# Problem is with this config
[backblaze]
type = b2
account = XXX
key = XXX
### Double check the config for sensitive info before posting publicly

A log from the command that you were trying to run with the -vv flag

/config/rclone # rclone lsd -vv backblaze:icloud-synology
2025/10/16 14:24:39 DEBUG : rclone: Version "v1.71.1" starting with parameters ["rclone" "lsd" "-vv" "backblaze:icloud-synology"]
2025/10/16 14:24:39 DEBUG : Creating backend with remote "backblaze:icloud-synology"
2025/10/16 14:24:39 DEBUG : Using config file from "/config/rclone/rclone.conf"
2025/10/16 14:24:39 DEBUG : pacer: low level retry 1/10 (error Post "https://api005.backblazeb2.com/b2api/v1/b2_list_file_names": EOF)
2025/10/16 14:24:39 DEBUG : pacer: Rate limited, increasing sleep to 20ms
2025/10/16 14:24:39 DEBUG : pacer: low level retry 2/10 (error Post "https://api005.backblazeb2.com/b2api/v1/b2_list_file_names": EOF)
2025/10/16 14:24:39 DEBUG : pacer: Rate limited, increasing sleep to 40ms
2025/10/16 14:24:39 DEBUG : pacer: low level retry 3/10 (error Post "https://api005.backblazeb2.com/b2api/v1/b2_list_file_names": EOF)
2025/10/16 14:24:39 DEBUG : pacer: Rate limited, increasing sleep to 80ms
2025/10/16 14:24:39 DEBUG : pacer: low level retry 4/10 (error Post "https://api005.backblazeb2.com/b2api/v1/b2_list_file_names": EOF)
2025/10/16 14:24:39 DEBUG : pacer: Rate limited, increasing sleep to 160ms
2025/10/16 14:24:40 DEBUG : pacer: low level retry 5/10 (error Post "https://api005.backblazeb2.com/b2api/v1/b2_list_file_names": EOF)
2025/10/16 14:24:40 DEBUG : pacer: Rate limited, increasing sleep to 320ms
2025/10/16 14:24:40 DEBUG : pacer: low level retry 6/10 (error Post "https://api005.backblazeb2.com/b2api/v1/b2_list_file_names": EOF)
2025/10/16 14:24:40 DEBUG : pacer: Rate limited, increasing sleep to 640ms
2025/10/16 14:24:40 DEBUG : pacer: low level retry 7/10 (error Post "https://api005.backblazeb2.com/b2api/v1/b2_list_file_names": EOF)
2025/10/16 14:24:40 DEBUG : pacer: Rate limited, increasing sleep to 1.28s
2025/10/16 14:24:41 DEBUG : pacer: low level retry 8/10 (error Post "https://api005.backblazeb2.com/b2api/v1/b2_list_file_names": EOF)
2025/10/16 14:24:41 DEBUG : pacer: Rate limited, increasing sleep to 2.56s
2025/10/16 14:24:42 DEBUG : pacer: low level retry 9/10 (error Post "https://api005.backblazeb2.com/b2api/v1/b2_list_file_names": EOF)
2025/10/16 14:24:42 DEBUG : pacer: Rate limited, increasing sleep to 5.12s
2025/10/16 14:24:44 DEBUG : pacer: low level retry 10/10 (error Post "https://api005.backblazeb2.com/b2api/v1/b2_list_file_names": EOF)
2025/10/16 14:24:44 DEBUG : pacer: Rate limited, increasing sleep to 10.24s
2025/10/16 14:24:44 ERROR : error listing: Post "https://api005.backblazeb2.com/b2api/v1/b2_list_file_names": EOF
2025/10/16 14:24:44 DEBUG : 5 go routines active
2025/10/16 14:24:44 NOTICE: Failed to lsd with 2 errors: last error was: Post "https://api005.backblazeb2.com/b2api/v1/b2_list_file_names": EOF
2

welcome to the forum,

so far, i cannot reproduce the issue.

are all the machines behind the same router?

rclone config redacted b2:
[b2]
type = b2
account = XXX
key = XXX

rclone lsd b2: -vv
2025/10/16 10:55:55 DEBUG : rclone: Version "v1.71.0" starting with parameters ["rclone" "lsd" "b2:" "-vv"]
2025/10/16 10:55:55 DEBUG : Creating backend with remote "b2:"
2025/10/16 10:55:55 DEBUG : Using config file from "d:\\data\\rclone\\rclone.conf"
          -1 1999-12-31 19:00:00        -1 zorkzork

curl -X POST https://api005.backblazeb2.com/b2api/v1/b2_list_file_names
{
  "code": "bad_request",
  "message": "object should start with brace but found: ￿",
  "status": 400
3

Yes, they are under the same router. Just tried with a mobile hotspot, it's working now interestingly.

rclone ls -vvv b2:icloud-synology 
2025/10/16 11:21:39 DEBUG : rclone: Version "v1.72.0-beta.9179.1903b4c1a" starting with parameters ["rclone" "ls" "-vvv" "b2:icloud-synology"]
2025/10/16 11:21:39 DEBUG : Creating backend with remote "b2:icloud-synology"
2025/10/16 11:21:39 DEBUG : Using config file from "/home/h3yb4ws/.config/rclone/rclone.conf"
     3980 log.1
2025/10/16 11:21:40 DEBUG : 8 go routines active

I'll have to check my router settings, but I'm fairly certain I don't have anything non-standard AFAIK.

4

Looks to be DNS related. For reference, I'm using Optimum.

Setting the DNS to Google DNS or Cloudflare seemed to have fixed this problem. Doesn't help that it's near impossible to access my router settings since Optimum has it behind their website and that barely works.

5

More info in case it’s helpful to others: I ran into this issue yesterday as well and it still persists today. I noticed the endpoint is the same, api005. Backblaze was down a few days ago at some data centers, and I noticed I can ping other endpoints like api001, api006 successfully. The traceroute shows api005 getting stuck at the ISP DNS level (I use bluestream).

I suspect the outage with backblaze caused DNS problems on api005. ISP DNS updates are extremely slow (mine seems to take a few days), so this will take a few days to propagate through the system.

6

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