Q: Why does my widget give me a Gateway timeout??

PreparedElephant1 month ago

When I try to authenticate a Garmin user, everything is great until after it tries to redirect me to my app. Then we receive 504 Gateway timeout with my browser showing the source of the error was caused by https://api.tryterra.co. Is this a bug on your end???

terra

Jeffadmin1 month ago

Hey there,

This issue is most commonly caused by your configured webhook taking too long to respond to our auth_success or auth_failure payload. Typically happens when a configured endpoint has security preventing us from sending data or an expired ngrok url is used. If your service times-out, our service will reflect that as we send this payload synchronously so you can confirm that the authentication process is complete.

To resolve this:

  1. Update your network policies to whitelist the following Terra ip addresses and remove any Geoblocks placed on the London/Europe region:
    • 18.133.218.210
    • 18.169.82.189
    • 18.132.162.19
  2. Replace or update your Webhook URL to an appropriate one; you can determine if a URL is valid by submitting it on Dashboard > Connections, hitting Add Destination, selecting webhook and submitting the URL. If no error is presented, the webhook is ready for usage. You can also test the connection by going to the Data Generator and sending a test payload to your webhook, then you should be able to see the status on the Debug Event Log

PreparedElephant1 month ago

You were correct, updated the url and everything looks good on our side 👍