Currently, the proxy enforces the use of TLS certificates in a specific path.
This makes it harder to deploy on platforms like fly.io, where backend services are expected to run in plain mode and TLS termination should happen at the platform’s edge.
It would be very useful to have a configuration option (for example, a flag like --insecure-no-tls) to disable TLS. This way, the proxy could run in plain HTTP mode when it is behind a reverse proxy or load balancer that already handles TLS termination.
I’d be interested in contributing an implementation for this feature if you think it would fit the project.