10 months ago
The flow works well only in testing with a test URL, when using the Production URL and activating the flow it does not respond to the API, it keeps trying forever and does not receive anything?
Pinned Solution
10 months ago
I discovered the problem in the simple local memory node in production, it lost the relationship with the messages, so I redid the references and it worked.
Thanks to everyone for the help.
5 Replies
10 months ago
Hi!
Are you serving your URL through Cloudflare? That's the easiest way to set it up
https://docs.railway.com/guides/public-networking#custom-domains
Also, setting up the SSL/TLS to Full instead of Flexible could solve the problem
https://docs.railway.com/guides/public-networking#provider-specific-instructions
If this doesn't work, if you could send some screenshots from the logs when you do requests to the API, that would be helpful
10 months ago
I’m not using Cloudflare. I just want to access my project through the Railway production URL, nothing else. It works in testing, but in production, when I access it, the flow is triggered, but it doesn’t return anything to me. That’s the problem.
10 months ago
Could you attach some screenshots from the logs and the domain setup? Are you calling this endpoint from the browser or somewhere else?
10 months ago
do you have environment variables in your dev setup that may not work in prod?
10 months ago
I discovered the problem in the simple local memory node in production, it lost the relationship with the messages, so I redid the references and it worked.
Thanks to everyone for the help.
Status changed to Solved chandrika • 10 months ago