Changing SENTRY_DSN killed my Laravel site


#1

I’ve taken over a complex Laravel site which already has a value set for SENTRY_DSN in its .env file.

The site has some issues on some pages and I don’t have access to the data sent to that DSN so I set up a new account in Sentry just now and created a new DSN (free tier).

I stuck that in the live production .env file and KABOOM - site homepage shows the ‘Whoops something went wrong…’ error page.

What do I do?

PS. I am VERY new to Laravel.

TY!


#2

PS. I note that the old value is of the form:

hash:hash@url.com/12345

And the new one (as provided to me by Sentry) is of the form:

hash@url.com/12345

Is that the issue perhaps?


#3

Depends on which version of our SDK your application runs, we deprecated the “secret” DSN a long time ago.
But you can still copy the “secret” DSN in our interface DSN (Deprecated) is below the new one.


#4

Aha I hadn’t seen that interface. Bingo. Back in business.

For anyone else reading this thread, find the aforementioned deprecated URL ‘with’ secret here:

Home -> Projects -> now select your project -> Settings -> Client Keys (DSN)

And the colon separated style URL is there to behold.

TY