Your machine couldn't look up the Backblaze hostname. This is almost always a DNS or content-filter issue on your network. Run the network check from Step 00 again, and if it still fails, contact your IT department and ask them to allow outbound HTTPS to *.backblazeb2.com.

Your network is reaching the right place but a firewall is dropping the connection. This usually requires IT to allow traffic on port 443 to *.backblazeb2.com. If you're on a corporate VPN, try disconnecting briefly to confirm whether the VPN is the cause.

Your credentials weren't accepted. A few things to check:

• Make sure you copied the Backblaze B2 Credentials, not the AWS S3 Credentials shown above them in Openda — they look similar but aren't interchangeable.
• Re-run aws configure --profile segmed-b2 and re-enter the keys, watching for accidental whitespace at the start or end when pasting.
• Check the Expiration Date shown beneath the credentials in Openda. If it's in the past, contact your Segmed representative for fresh credentials.

Authentication worked, but the directory you specified doesn't exist or your key doesn't have access to it. Double-check that the value in field ③ matches the Directory shown in Openda exactly, including any hyphens or numbers. Don't include s3:// when entering it here — that's added automatically.

The AWS CLI isn't installed, or your terminal hasn't picked it up yet. Revisit the Before you start section above. After installing, close and reopen your terminal window, then run aws --version to confirm.

For large datasets, the sync can take hours and may pause briefly between files — this is normal. If it has actually stopped (no progress for several minutes), interrupt with Ctrl + C and re-run the same command. The sync command resumes where it left off and will only re-download files that didn't complete.

This usually means a corporate firewall or antivirus is intercepting HTTPS connections (TLS inspection). Contact your IT department — they may need to add Backblaze to a TLS-inspection exclusion list, or install a corporate root certificate on your machine that covers Backblaze traffic.

This is the most common issue, and it's almost never your credentials. It usually means the Path field was left empty, so Cyberduck tried to list every directory on the server — which your key isn't allowed to do.

• Re-open the connection, click More Options at the bottom of the dialog, and enter your directory from ③ in the Path field.
• Double-check the Path matches the Directory shown in Openda exactly, including any hyphens or numbers. Don't add s3:// or any slashes at the start.

Your credentials weren't accepted. A few things to check:

• Make sure you copied the Backblaze B2 Credentials, not the AWS S3 Credentials shown above them in Openda — they look similar but aren't interchangeable.
• Re-paste both keys, watching for accidental whitespace at the start or end. Pasting into the fields in Step 01 of this guide will strip stray spaces for you — then copy the cleaned values from the preview.
• Check the Expiration Date shown beneath the credentials in Openda. If it's in the past, contact your Segmed representative for fresh credentials.

Your machine can't reach Backblaze — this is a network issue, not a Cyberduck issue. Re-run the browser check from Step 00. If it fails, contact your IT department and ask them to allow outbound HTTPS (port 443) to *.backblazeb2.com. If you're on a corporate VPN, try disconnecting briefly to confirm whether the VPN is the cause.

This usually means a corporate firewall or antivirus is intercepting HTTPS connections (TLS inspection). Don't click through the warning — contact your IT department. They may need to add Backblaze to a TLS-inspection exclusion list, or install a corporate root certificate on your machine that covers Backblaze traffic.

You connected, but you're not looking at the right place. Check that the Path in your connection matches the Directory from Openda character-for-character. If you saved a bookmark earlier with a wrong or missing Path, right-click the bookmark → Edit Bookmark and fix the Path there.

For large datasets, downloads can take hours and may pause briefly between files — this is normal. If a transfer has actually stopped, open Window → Transfers, select it, and click the resume (↻) button. When asked what to do with existing files, choose Resume — already-completed files are skipped, and partial files continue from where they stopped.