24 days ago
Project: amusing-radiance
Service: @smm/api
Environment: production
I upgraded to the Pro plan and redeployed the service twice, but outbound SMTP on port 465 is still not working. I tested connectivity directly inside the container via railway ssh:
mail.allinonsr.com port 25 unreachable
mail.allinonsr.com port 465 unreachable
mail.allinonsr.com port 587 unreachable
mail.allinonsr.com port 2525 unreachable
To rule out a DNS or destination-side issue, I also tested a known-good SMTP host from the same container:DNS OK (mail.allinonsr.com) -> 14.128.14.32
DNS OK (smtp.gmail.com) -> 142.250.27.108
smtp.gmail.com:465 ERROR (connection failed)
mail.allinonsr.com:465 TIMEOUT
Both DNS lookups succeed, but connections to port 465 fail for both my own mail server AND smtp.gmail.com — this suggests outbound SMTP is still being blocked/dropped at the Railway network level for this service, despite the Pro plan. Can you confirm whether SMTP is actually enabled for this service, or if there's additional action needed on my end?
1 Replies
24 days ago
Your workspace is currently on the Hobby plan, not Pro. SMTP is only available on the Pro plan and above, so outbound SMTP ports remain blocked on Hobby. Please upgrade to Pro, then perform a re-deploy of your application for us to apply the new configuration and refer to Debugging SMTP issues for additional troubleshooting steps.
Status changed to Awaiting User Response Railway • 24 days ago
17 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 17 days ago