5 months ago
I'm experiencing SSL/TLS connection issues when trying to connect my IoT device to a Railway backend. While Postman requests work perfectly, my device fails during the SSL handshake.
Connection Details:
- Port: 443 (HTTPS)
- Protocol: HTTPS with TLS 1.2
The connection fails with these specific errors:
1. SSL handshake timeout (during TLS negotiation)
2. SSL handshake failure (during certificate verification)
I've verified:
- SNI (Server Name Indication) is enabled
- TLS 1.2 is being used
- The domain resolves correctly
- The device has proper internet connectivity
Questions:
1. Does Railway require specific SSL/TLS settings beyond standard HTTPS?
2. Are there specific certificate requirements?
3. Is there a way to test or debug the SSL handshake with Railway?
I have read the docs regarding Public Networking but I am not able to pinpoint what exactly I am doing wrong when trying to connect from my IoT device
2 Replies
5 months ago
1. Does Railway require specific SSL/TLS settings beyond standard HTTPS?
Not really. We enforce a minimum TLS version of 1.2, but nothing much apart from that unless you're using a proxy like Cloudflare that also provides HTTPS.
2. Are there specific certificate requirements?
Nope.
3. Is there a way to test or debug the SSL handshake with Railway?
Can you share the exact error you're receiving when attempting to connect from your IoT device?
If you're able to access it normally via Postman/a HTTP client, the cert is working and the issue lies with your IoT device. Have you checked that your system clock on the IoT device is set correctly?
Status changed to Awaiting User Response railway[bot] • 6 months ago
5 months ago
Just managed to make it work, just left the basic config for TLS 1.2 and it works. Thanks for your help!
Status changed to Awaiting Railway Response railway[bot] • 6 months ago
Status changed to Solved chandrika • 6 months ago