Skip to content
Railway Storage Bucket — TLS Certificate Verification Error 10
ferasalrifai-oss
OP

a month ago

Hello Railway Support,

I need assistance securely accessing an existing Railway Storage Bucket to create an independent backup of encrypted objects.

Environment:

  • Project: Salaf Articles
  • Storage endpoint: https://t3.storageapi.dev
  • Windows 10
  • Python 3.13.16
  • OpenSSL 3.5.9
  • Strict TLS certificate and hostname verification enabled

Error:

  • TLS_CERTIFICATE_FAILURE
  • OpenSSL verify_code: 10 (certificate has expired)
  • Failure during TLS handshake, before the HTTP response

A credential-free diagnostic retrieved four peer-presented certificates:

  • storage.dev — valid until January 6, 2027
  • Let's Encrypt YE2 — valid until September 2, 2028
  • ISRG Root YE — valid until September 2, 2032
  • ISRG Root X2 — valid until September 2, 2032

All four appeared valid on October 13, 2026. However, OpenSSL still returned verification error 10. The exact certificate in the failing constructed verification path remains unidentified.

The Windows clock and timezone were checked. No certificate verification bypass, trust-store modification, credential rotation, or production change has been performed.

Please advise:

  1. Is there a known certificate-chain compatibility problem affecting this Storage Bucket endpoint?
  2. What is the officially supported secure S3 access method for Windows?
  3. How can I download the existing encrypted objects byte-for-byte without disabling TLS verification?
  4. Is a secure alternative available without modifying the production environment or creating paid resources?

My goal is to preserve and independently verify the original encrypted objects.

Please do not request secret access keys or OAuth credentials in a public discussion.

Thank you.

Solved

1 Reply

Railway
BOT

a month ago

The chain you captured is publicly trusted and every certificate in it is within its validity dates, so we can't reproduce an expired certificate on our side from what you've shared. Your client's verifier is building its path from those certificates plus its own local trust store, and that combination is what needs checking. We can't say which certificate in that constructed path is the one OpenSSL reports as expired.

Also note that buckets use virtual-hosted style URLs, so a real S3 client connects to your bucket name as a subdomain of the endpoint, not to the bare endpoint. A credential-free test against the bare endpoint may not be the same handshake your client actually makes. The Credentials tab on your bucket shows which URL style that bucket uses.

There isn't a Windows-specific access method. Buckets are fully S3-compatible, so any standard S3 client or SDK with strict TLS verification turned on can list and GET your objects using the endpoint, bucket name and keys from the Credentials tab. A plain GET returns the stored bytes exactly as uploaded, and bucket egress and API operations are free, so this doesn't change your production setup or create any new resources.


Status changed to Awaiting User Response Railway • about 1 month ago


Railway
BOT

a month ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway • about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...