23 days ago
Our Railway workspace is on Pro and the production service has been redeployed after upgrading.
However, our app still cannot connect to Gmail SMTP:
- Host: smtp.gmail.com
- Port 465 SSL: Connection timeout
- Port 587 STARTTLS: Connection timeout
- App URL: https://web-production-8bec8.up.railway.app
- Service is trying to send via Nodemailer from Node.js
Please check whether outbound SMTP is enabled for this service and whether ports 465/587 are reachable from our deployment.
2 Replies
23 days ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open Railway • 23 days ago
23 days ago
Have you followed the "Debugging SMTP Issues" docs?
Follow the steps and if the issue persists please share the output of the command showed in the docs.
medim
Have you followed the "[Debugging SMTP Issues](https://docs.railway.com/networking/outbound-networking#debugging-smtp-issues)" docs? Follow the steps and if the issue persists please share the output of the command showed in the docs.
23 days ago
We followed the Debugging SMTP Issues docs and SSH’d into the service container.
Project: confident-vitality
Environment: production
Service: web
Inside the container:
root@48f06a0e6218:/app#
nc is not installed, so we used bash /dev/tcp tests:
timeout 10 bash -c '</dev/tcp/smtp.gmail.com/465' && echo "465 open" || echo "465 failed"
timeout 10 bash -c '</dev/tcp/smtp.gmail.com/587' && echo "587 open" || echo "587 failed"
Results:
465 failed
587 failed
Our app also returns Connection timeout from Nodemailer when trying to send through smtp.gmail.com.
The workspace is on Pro and the service has been redeployed after upgrading. Please check outbound SMTP access for this Pro service.