6 months ago
The goal is for your Evolution API service to send data to your n8n service using Railway's private network to avoid egress costs. Although both services are in the same project, private network communication isn't working, while the public network works perfectly.
Failed Solution Attempts
Initial Private Network Connection: We tried using the n8n private network URL in Evolution API, but the n8n trigger wasn't receiving the data. This was a persistent problem.
N8N_HOST Configuration: We added the N8N_HOST environment variable with the value 0.0.0.0 so that n8n would listen on all network interfaces, including the IPv6 that the Railway private network uses. This didn't solve the problem.
URL Without a Port: We verified that private network URLs don't need a port, but as a debugging step, we tried adding port 5678 to the URL, which also didn't work.
2 Replies
6 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!
6 months ago
Hello,
Per our fair use agreement, WhatsApp bots are not allowed on Railway unless they are using the official API from Meta. Since the Evolution API is in use, the official Meta API is not being used.
Please find somewhere else to host the WhatsApp bot portion of your automations, otherwise there is a risk of a ban.
Best,
Brody
Status changed to Awaiting User Response Railway • 6 months ago
Status changed to Closed brody • 6 months ago