Object Storage Service:0041-00000104

Problem description

When a mirroring-based back-to-origin rule is triggered, data cannot be read from the origin.

Causes

An exception on the origin prevents OSS from fetching data. Common causes include:

• The origin server is unreachable or returns an unexpected status code.

• DNS resolution for the origin domain fails.

• The HTTPS certificate on the origin is invalid (if the origin uses HTTPS).

• Objects at the back-to-origin URL are not publicly accessible, or the back-to-origin configuration lacks the permissions needed to retrieve them.

Examples

None

Solutions

Work through the following steps to identify and fix the issue.

1. Check whether the origin is reachable.

      curl -I "https://<your-origin-domain>/<object-path>"

   A 200 or 206 response confirms the origin is accessible. Any other status code indicates a problem on the origin.

2. Check DNS resolution for the origin domain.

      nslookup <your-origin-domain>

   If the domain does not resolve, fix the DNS configuration before retrying.

3. If the origin uses HTTPS, verify the certificate.

      openssl s_client -connect <your-origin-domain>:443 -servername <your-origin-domain>

   Look for Verify return code: 0 (ok). Any other return code indicates a certificate issue.

4. Verify that objects at the back-to-origin URL are publicly accessible, or that the back-to-origin configuration has the correct permissions to retrieve them.

5. Verify that the origin server is running and handling requests as expected.

References

• Mirroring-based back-to-origin