SMTP blocked for n8n password recovery impacting our students
devtoolscitdev
PROOP

2 months ago

Hello Railway team,

I’m currently hosting an n8n instance on Railway using the Hobby plan, and I’ve encountered an issue with the password recovery feature, which relies on SMTP to send reset emails.

I’ve configured Brevo (Sendinblue) as the SMTP provider and verified all environment variables:

N8N_SMTP_HOST=smtp-relay.brevo.com
N8N_SMTP_PORT=587
N8N_SMTP_USER=xxxx
N8N_SMTP_PASS=xxxx

However, the password recovery emails fail to send.

After reviewing your documentation (Outbound Networking), I understand that SMTP traffic is blocked on the Free, Trial, and Hobby plans to prevent spam or abuse.

I fully understand the reason for this restriction, but this limitation is causing unexpected issues for many users.
I run an online course where we teach and recommend Railway as the hosting platform for n8n-based projects we currently have over 2,000 students using Railway as part of our lessons.

Unfortunately, this SMTP restriction has surprised many of them, as it prevents password recovery for the n8n application itself meaning that if a user loses their credentials, they effectively lose access to their hosted instance.

Could you please confirm if upgrading to the Pro plan fully unlocks outbound SMTP, and whether this change takes effect immediately after upgrading?

Additionally, would the Railway team consider allowing limited SMTP use (e.g., for password recovery or transactional emails) on Hobby projects to avoid this problem for educational purposes?

Thank you so much for your attention and support.

Best regards,
Leandro Manes
Founder @ Citizen Developer

Solved$10 Bounty

3 Replies

Railway
BOT

2 months ago

Hey there! We've found the following might help you get unblocked faster:

If you find the answer from one of these, please let us know by solving the thread!


uxuz
MODERATOR

2 months ago

Hey, SMTP is available on the pro plan, but keep in mind that you will most likely have to redeploy your primary n8n service for the new limits and features to be applied. The Railway docs you have referenced above also has a guide on how to debug and see if SMTP works correctly in a service (which in this case would be your primary n8n service).

Railway does not manually grant pro plan features or limits to users of other plans.

While not the most ideal solution, it is also possible to reset all user credentials (removing all users) without SMTP (pro plan), by following the n8n forum and n8n docs. In short, this can be done by running n8n user-management:reset in your primary service and redeploying it afterwards. You will have to SSH into your primary service in order to run the command, which will require you to use the Railway CLI. The command to SSH into your service can be retrieved by right clicking on it and selecting Copy SSH Command afterwards.


uxuz
MODERATOR

2 months ago

Hey, did the message I sent above solve your concerns and issues?


Status changed to Solved uxuz about 2 months ago


Loading...