400 Authentication information is not given in the correct format


You're upgrading EVE-OS on an edge node and receive the following 400 response.

Error messages

Seen in the node's status tab:

Description=400 Authentication information is not given in the correct format. Check the value of Authorization header., Details: (none) HEAD https://zededacentral.blob.core.windows.net/diskimages/10.4.8-lts-kvm-amd64?timeout=61 Authorization: REDACTED
Found error in content tree master.2-ubuntu-2004 attached to volume my-device_0_m_0:
Syncer Download Status of image name: master.2-ubuntu-2004.packer, location: /persist/vault/downloader/pending/117cb9ab678eabe0b4e812e92a84e9a6d79612cf38e08e2ea73b9f6cdd5916ba.a5ac845529400dece6273b68a85b5851da0c4ccbce4f818bec4e06f42f4cbf2a - error could not get properties for blob: -> github.com/Azure/azure-storage-blob-go/azblob.newStorageError, /pillar/vendor/github.com/Azure/azure-storage-blob-go/azblob/zc_storage_error.go:42
===== RESPONSE ERROR (ServiceCode=InvalidAuthenticationInfo) =====
Description=400 Bad Request, Details: (none)
HEAD https://my-blob.blob.connect.bobst.com/images/master.2-ubuntu-2004.packer?timeout=61
Authorization: REDACTED
User-Agent: [Azure-Storage/0.14 (go1.18.6; linux)]
X-Ms-Client-Request-Id: [5faa1f93-12aa-43c3-5ab1-0d3dd773b4bc]
X-Ms-Date: [Tue, 23 Apr 2024 11:38:06 GMT]
X-Ms-Version: [2020-04-08]
RESPONSE Status: 400 Bad Request
Date: [Tue, 23 Apr 2024 11:38:09 GMT]
Server: [Microsoft-HTTPAPI/2.0]
X-Ms-Error-Code: [InvalidAuthenticationInfo]
X-Ms-Request-Id: [fbc00fe1-501e-006f-7472-95434c000000]

In the logs (for internal reference by CSEs):

The following message is for ZEDEDA Technical Support staff to verify that you are experiencing the error described here, rather than something else.

Controller certificate ID was not found for the corresponding context:

lookupControllerCert(7306a9f1ec614f390a496e9ff3a7402a) not found

Decryption is unsuccessful:

da02830a-4b27-4dad-b5b7-97665480b52e, datastore config cipherblock decryption 
unsuccessful, falling back to cleartext: Controller Certificate get fail


This problem is known to impact version prior to 9.4.15. It happens when a node running one of the affected EVE versions tries to retrieve certificates from its controller over a weak internet connection.


Power cycle the device several times to ensure that EVE successfully retrieves the certificate from the controller.

If you continue to receive the same 400 response after power cycling your device, reach out to ZEDEDA Technical Support for further help.

Was this article helpful?
0 out of 0 found this helpful