Next.js tunnelRoute does not support selfhosted instances

[4ndv]

Problem Statement

Currently tunnelRoute always points to sentry.io, and there is no way to specify own server. Looks like some lists are now blocking by /?sentry_key rule, which affects all the instances, both cloud and selfhosted.

Solution Brainstorm

Add some option that will allow setting tunnelRoute's destination server

[4ndv]

Also the docs at the time aren't very good at clarifying that it will not work with a selfhosted instances

[lforst]

Hi, thanks for writing in! The tunnel option is not designed to be a mechanism around CORS. I recommend you actually configure CORS rules properly.

I will close this issue as we want to keep our backlog minimal and it is unlikely that we will ever change the behavior.

[4ndv]

Can you at least please clarify this in the docs for that config property?

[lforst]

Can you at least please clarify this in the docs for that config property?

Sure! getsentry/sentry-docs#6226

[4ndv]

Hi, thanks for writing in! The tunnel option is not designed to be a mechanism around CORS. I recommend you actually configure CORS rules properly.

I will close this issue as we want to keep our backlog minimal and it is unlikely that we will ever change the behavior.

@lforst and I found out that my issue wasn't actually a CORS at all, but uBlock Origin...

So looks like it isn't a bad idea to include an option for selfhosted instance?

Our sentry instance is not directly mentioned in the lists, but is blocked by this rule, according to uBlock Origin's logs:

[4ndv]

Some more information about the rule, looks like it originates from EasyList's EasyPrivacy (https://easylist.to/easylist/easyprivacy.txt):

[lforst]

Okay that changes things. I didn't know that they were looking for sentry_key now 🙄. Gonna reopen this then!

[4ndv]

Okay that changes things. I didn't know that they were looking for sentry_key now 🙄. Gonna reopen this then!

Thank you! My due-diligence was lacking too, because when uBlock blocks things, in console it looks like a CORS issue :)

I've edited my initial message to better reflect this