We don't have a published root.crt or server.crt for PostgreSQL services. That means we can't send you certificate files, SHA-256 fingerprints, validity dates or SAN names, and we can't attest that a particular certificate belongs to your running database.

Your database runs on our SSL-enabled Postgres image. That image's TLS certificates are created and served by the database service itself. They are not issued by a public certificate authority that we keep a record of. The postgres-ssl repository shows exactly how the image creates and configures them.

We also can't offer a way to get the certificates that skips both your conditions: connecting to PostgreSQL and accessing the service's shell.

Hello Railway Support,

I’m preparing a safe, read-only compatibility check for my existing Self Training PostgreSQL database.

Could you please provide, or explain how to securely retrieve, the current public root.crt and server.crt certificates for my PostgreSQL service?

Please also confirm their SHA-256 fingerprints, validity dates, certificate SAN names, and that they belong to my currently running database.

I need a method that does not require accepting an unverified SSH host key, connecting to PostgreSQL, restarting the service, or changing its configuration.

I do not need passwords, private keys, backups, or database records.

If Railway does not support this, please let me know.

Thank you for your assistance.

We don't support this. We don't publish or attest root.crt or server.crt files for PostgreSQL services, so we can't give you certificate files, SHA-256 fingerprints, validity dates or SAN names, or confirm that a particular certificate belongs to your running database.

We also don't publish host key fingerprints for SSH access, so there's no method we can offer that meets all of your conditions.

Thank you. I understand these certificates and fingerprints aren’t available.

I’m not requesting them again.

Could you please escalate this discussion to a human Railway engineer?

I need guidance on the standard, supported way to safely inspect PostgreSQL schema metadata from an isolated service within Railway’s private network, without modifying the existing database or deploying my application.

Specifically, what database transport security and identity-verification method does Railway recommend for this setup?

Thank you.

Thank you. However, this is a production database security question, not a general community troubleshooting request.

Could you please escalate this to a human Railway support engineer?

We need Railway’s recommended, supported method for securely verifying PostgreSQL schema metadata through its private network, without modifying the production database.

We are not requesting certificates that Railway has already confirmed are unavailable.

If human technical support is not available on my current plan, please confirm that and explain the appropriate support channel.

Thank you.

You can inspect the schema by going into the Database tab when clicking into the Postgres service.

If you wish to view the data in depth, you'll need to use a Postgres client and connect to the database via the TCP proxy.

Thank you for your help.

Before deploying an updated application, I need to verify my existing PostgreSQL database structure without accessing or changing athlete records.

Does Railway’s Database viewer support a metadata-only schema export or a read-only SQL query facility?

Specifically, I need to inspect table definitions, columns, constraints, indexes, and migration metadata, including drizzle.__drizzle_migrations, without retrieving application data.

If the viewer cannot do this, what supported, secure method would you recommend?

Thank you.

You’ll need a db client to view definitions, constraints, etc.