Skip to content
Discussion options

You must be logged in to vote

Start with the actual network destination. An old tunnel, custom transport, or environment override can keep sending to Sentry after the visible DSN changes. Confirm requests reach your Bicho instance's envelope or store route and that any envelope DSN names the receiving origin and project.

Check authentication next. All supplied keys must match the route project; secret-enabled backend projects also need the generated transport headers. Never add an admin token to the SDK as a fix.

For browser requests, inspect the preflight and POST separately. Bicho's ingest routes support cross-origin ingestion with wildcard origin and Sentry authentication headers. Read/admin CORS is separate. A pro…

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by zapalblizh
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants