For some time now, we have been experiencing issues with a microservice hosted on Railway.app that previously worked flawlessly. The microservice in question receives POST requests, triggering a call to the EasyTrack API (for bus geolocation) and updates XML files with the latest known bus locations.

The problem that has arisen is an authentication error when querying the API. The API no longer returns the authentication token needed to retrieve the updated bus locations. We contacted the API support team, and they confirmed that everything is working fine on their end, suggesting that the issue could be related to DNS, firewall, or the IP address from Railway.app.

We attempted to resolve the issue by using a static IP, but this did not fix the problem. Has anyone else experienced a similar issue with API authentication on Railway.app, or have any suggestions on how to resolve this?