shuttle_shared_db diesel integration does not enable tls, but it is required
Author: oddgrdCreated Sep 17, 2025Updated Nov 6, 2025
LabelsS-Triage
What happened?
The pools returned from the shuttle-shared-db diesel-async integrations do not enable TLS, but it is required in deployment, as the Shared Database requires TLS. That means it works for local run with the local Docker postgres database, but not in deployment.
The diesel-async integrations should include a TLS implementation, ideally using Rustls, so that a TLS connection to the database can be established in deployment.
Reproduced with shuttle-shared-db = { version = "0.57.0", features = ["postgres", "diesel-async-deadpool"] }.
Version
v0.57.2
Which operating system(s) are you seeing the problem on?
In deployment
Which CPU architectures are you seeing the problem on?
In deployment
Relevant log output
ERROR postgres: failed to get pool connection: Error occurred while creating a new object: no pg_hba.conf entry for host "10.15.138.104", user "user_TRpidOk0D5QG", database "db_TRpidOk0D5QG", no encryptionDuplicate declaration
- I have searched the issues and there are none like this.
Source: shuttle-hq/shuttle