There are two distinct problems which may result in the same error.
BackBlaze B2 does not have a centralised API server. Instead, whenever you are running a backup the centralised API server gives us an endpoint URL to the B2 pod (the actual server in their datacenter which stores your files) which hosts its own API server. Sometimes a specific pod may be running a buggy version of the B2 API server, causing an issue like that to appear even though we are sending the Content-Length header correctly.
The other problem has to do with your server. In some cases there is a proxy between your server and the rest of the Internet. Normally, proxies are transparent. However, in some cases a misconfigured proxy may alter or drop HTTP headers. If the proxy drops the Content-Length header you will get an error since this is required by B2.
I would recommend first trying to run your backup again or, alternatively, use the Manage Backups page to try and re-upload your backup archive to BackBlaze B2. Every time you run a backup or try to reupload you are getting to talk to a different B2 pod. This would solve the first problem.
If this doesn't work after trying it at least twice the problem must be a proxy in front of your server. This is something only your host can help you with. They are in control of their infrastructure. Let them know that their proxy is dropping or altering the HTTP Content-Length header which causes problems when uploading to BackBlaze B2. They should be able to reconfigure their proxy not to do that.
Nicholas K. Dionysopoulos
Lead Developer and Director
🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!
