1. Invalid Credentials: Incorrect or invalid access credentials provided during repository setup.

2. Invalid Service Endpoint or DC Region: Incorrectly entered service endpoint URL or an invalid data center (DC) region selection.

3. Insufficient Access Privileges or Storage Space: The target repository lacks the necessary access permissions or storage capacity.

4. Connectivity Issue: Network or internet connectivity problems preventing communication with the repository.

Depending on the cause, follow these solutions to resolve the connectivity issue:

Cause 1: Invalid Credentials

1. Ensure that you have accurately entered the required details for each object storage repository.
   
2. For S3 and S3 Compatible repositories, verify the accuracy of the Access Key and Secret Key.
   
3. For Azure Blob, confirm the correctness of the provided Storage Account Name and Access Key.
   

Cause 2: Invalid Service Endpoint or DC Region

1. Double-check the accuracy of the Service Endpoint URL and ensure that the selected or entered DC Region is valid.
2. Match the DC region provided in the Service Endpoint URL with the one selected/entered in the DC Region field.
   

Example Format:

Service Endpoint: s3.<DC_Region>.amazonaws.com

DC region: <DC_Region>

Cause 3: Insufficient Access Privileges or Storage Space

1. Ensure that the credentials used for repository connection possess the required access privileges.
2. For S3 Compatible Storage, verify that the locally deployed storage has sufficient storage space.
   

Cause 4: Connectivity Issue

1. Confirm that the BDRShield Backup server has unrestricted internet access.
2. Check and configure any NAT, firewall, or antivirus tools on the server to permit traffic to/from the provided Service Endpoint.