Troubleshooting S3-Compatible Repositories

Product version: 11.0

Last modified: 06 March 2025

Problem

S3-compatible repository (Amazon S3, Wasabi, or Backblaze) is in an Inaccessible state, preventing backups or restores.

Background

S3-compatible storage requires proper network connectivity, authentication credentials, and access permissions to function correctly. When a repository becomes inaccessible, it is essential to diagnose the issue by checking network connectivity, verifying credentials, and ensuring firewall rules allow the necessary traffic.

Solution

Follow these steps to diagnose and resolve the issue:

  1. Ensure your system can reach the storage provider using the following network diagnostic commands.

Note

The addresses in the commands below are provided as examples. Use the correct address depending on your environment.

  • Run the following command to check if the host name resolves correctly:

  • ping s3.amazonaws.com # Amazon S3

  • ping s3.eu-central-1.wasabisys.com # Wasabi

  • ping s3.eu-west-004.backblazeb2.com # Backblaze

If the ping fails with a "Name or service not known" error, verify your DNS settings and ensure the host name is correct.

  • To confirm that the required ports are open, run:

  • echo > /dev/tcp/s3.amazonaws.com/443 && echo "Amazon S3 Connection successful"

  • echo > /dev/tcp/s3.eu-central-1.wasabisys.com/443 && echo "Wasabi Connection successful"

  • echo > /dev/tcp/s3.eu-west-004.backblazeb2.com/443 && echo "Backblaze Connection successful"

If the command does not return a message about successful connection, ensure your firewall allows outbound traffic on port 443.

  • To validate SSL/TLS connectivity to the storage provider, use OpenSSL:

  • openssl s_client -connect s3.amazonaws.com:443 # Amazon S3

  • openssl s_client -connect s3.eu-central-1.wasabisys.com:443 # Wasabi

  • openssl s_client -connect s3.eu-west-004.backblazeb2.com:443 # Backblaze

If the connection fails or shows certificate errors, verify the SSL settings.

  1. Ensure that your firewall allows outbound connections to the storage provider's IP ranges.

  2. If using a proxy, verify that it is correctly configured for HTTPS traffic.

  3. Ensure that the correct Access Key and Secret Key are used.

  4. Verify the correct region and endpoint URL are configured in the repository settings.

  5. If the issue persists, create a support bundle, including the logs and the results of the above commands, and contact the support team.