2 months ago
Description: Deploy and Host ghost-cms-deploy with Railway
Category: CMS
6 Replies
4 days ago
I am having issues sending email with Mailgun, I have added required variables as indicated on guide but still cant recieve email. I am trying to add a editor for the project. I am only on the free plan on Mailgun
4 days ago
Hi Kyle, can you share what you are seeing in the logs? There are couple of failure points, so sharing logs would help to narrow down that.
Also, did you complete your signup? and if so, were you able to receive the email?
4 days ago
Also just make sure to check your spam folder.
Also did you try setting up mailgun using api keys - in case smtp is having issue? Following env vars would be required for http api setup -
mail__transport=Mailgun
mail__options__auth__api_key= (generate one from here - https://app.mailgun.com/settings/api_security)
mail__options__auth__domain=
mail__from=
3 days ago
Ho @heimdall, sorry got a little bit busy, here are some logs from ghost and network.
2 minutes ago
Hey @kyle-atienza, sorry weekday took toll, heres the solution in short -
Remove these:
mail__options__auth__pass
mail__options__auth__user
mail__options__host
mail__options__port
mail__options__secure
mail__options__serviceAdd/update these:
mail__transport = Mailgun
mail__options__auth__api_key = <mailgun-api-key>
mail__options__auth__domain = <mailgun-domain>Why: Railway blocks outbound SMTP for free/trial & hobby plans (src: https://docs.railway.com/networking/outbound-networking). by default ghost is trying to connect via SMTP, waiting the full 2m TCP timeout, then failing with ETIMEDOUT. Switching mail__transport to Mailgun makes Ghost use Mailgun's HTTP API (port 443) - which works for me. Please try that and let me know