external API request works on local and not in the deploy

omermor1TRIAL

9 months ago

I am currently experiencing an issue with my deployed application on Railway. The application integrates with an external API (JDoodle) and works perfectly in my local development environment. However, after deploying to Railway, the API requests are being rejected with a 403 Forbidden status code.

Here are some details about the issue:

  • Platform: Railway

  • Environment: Production

  • API Endpoint:https://api.jdoodle.com/v1/execute

  • Request Method: POST

  • Error:Request failed with status code 403 (received in production environment)

  • Local Environment: No issues, everything works as expected.

I have ensured that all environment variables (such as clientId and clientSecret) are correctly configured in the Railway environment, identical to those used locally. Despite this, the API calls fail only in the production environment hosted on Railway.

Could you please assist in diagnosing what might be causing this issue? Is there any possibility that the production environment's IP is being blocked, or is there any network configuration that might be affecting these requests? Any guidance or help in resolving this issue would be greatly appreciated.

Thank you for your support.

Best regards,
Omer Mor

1 Replies

brodyEMPLOYEE

9 months ago

Assuming you are indeed calling that endpoint with the correct auth, this would be jdoodle blocking your request.

Railway does not block outgoing request, nor do we have a way to do that in such a manner.

I would recommend getting in contact with jdoodle on this matter.