a month ago
For Railway TCP Proxy, can a custom domain accept standard TLS traffic on port 443 while passing the TLS handshake byte-for-byte to the service, preserving the original SNI hostname? Or must the client connect to the Railway-assigned nonstandard TCP Proxy port?
Our service needs to terminate TLS itself, require and validate the client certificate against a custom CA, and check SAN/EKU. Does TCP Proxy support this for both the Railway hostname and a custom-domain CNAME? Please also confirm idle timeouts and connection-lifetime limits.
Pinned Solution
a month ago
No, you can't accept standard TLS traffic on port 443, that's the HTTP edge and it terminates TLS. The TCP proxy, on the other hand, is raw TCP you can do TLS handshake passthrough to your service and so you can handle termination yourself along with certificate handling and such for your custom CA.
The TCP proxy does always use a Railway assigned port that you cannot customize. You can customize the domain with CNAME records but the port remains a uncustomizable. As for timeouts, the HTTP edge timeouts is 60s for idle connections and 5 minutes for HTTP requests with no data or 15 minutes with data (source), I'm not sure whether or not that applies to the TCP proxy though.
You can read more on TCP proxying here: https://docs.railway.com/networking/tcp-proxy
3 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 1 month ago
a month ago
No, you can't accept standard TLS traffic on port 443, that's the HTTP edge and it terminates TLS. The TCP proxy, on the other hand, is raw TCP you can do TLS handshake passthrough to your service and so you can handle termination yourself along with certificate handling and such for your custom CA.
The TCP proxy does always use a Railway assigned port that you cannot customize. You can customize the domain with CNAME records but the port remains a uncustomizable. As for timeouts, the HTTP edge timeouts is 60s for idle connections and 5 minutes for HTTP requests with no data or 15 minutes with data (source), I'm not sure whether or not that applies to the TCP proxy though.
You can read more on TCP proxying here: https://docs.railway.com/networking/tcp-proxy
dev
No, you can't accept standard TLS traffic on port 443, that's the HTTP edge and it terminates TLS. The TCP proxy, on the other hand, is raw TCP you can do TLS handshake passthrough to your service and so you can handle termination yourself along with certificate handling and such for your custom CA. The TCP proxy does always use a Railway assigned port that you cannot customize. You can customize the domain with CNAME records but the port remains a uncustomizable. As for timeouts, the HTTP edge timeouts is 60s for idle connections and 5 minutes for HTTP requests with no data or 15 minutes with data ([source](https://docs.railway.com/networking/public-networking/specs-and-limits)), I'm not sure whether or not that applies to the TCP proxy though. You can read more on TCP proxying here: https://docs.railway.com/networking/tcp-proxy
a month ago
Thank you! Have a blessed weekend.
Status changed to Awaiting User Response Railway • about 1 month ago
Status changed to Solved dev • about 1 month ago