#tunnelRoute gives me a 502

5 messages · Page 1 of 1 (latest)

uncut fern
#

Hi all I'm evaluating sentry for one of our apps. We use NextJS and we deploy to AWS not Vercel. I'm trying to setup the tunnelRoute and as far as I know I'm folloing the setup instructions correctly. I'm just setting up the route in the config that's it. Once deployed all I get is 502. Docs are pretty thin here... what am I missing? Do I have to create a monitoring route? Do I have to manually add the rewrite? TIA

obsidian wagon
#

I am not familiar how next.js app are deployed on AWS
but how the tunnelRoute works, it's expect that /monitoring exists which then forwards the payload to Sentry - this is not happening for anything outside Vercel (and Netlify I believe) because we use rewrites

#

so unless you really have to use it, I would recommend not using on AWS

uncut fern
#

@obsidian wagon Thanks I did eventually found this. I'm creating the route to forward the payload based on the example you guys have. One question where can I find the sentry host url? Or is this correct 'oXXXXXX.ingest.sentry.io' ?