service issues
# support-questions
t
Are there any known service problems right now? Authentication on our website has started throwing 500 and 405 errors. Can't figure out why.
r
hey @tktom none from our side (for the core hosting). Do you see any error stack on the backend?
t
I can't find any errors in our monitoring. We use Nextjs, and Sentry for monitoring.
r
i have DM'd you your connection url - if you click on it, it works fine.
Is your backend SDK process working?
t
Figured it out. I've disabled Sentry and it's back up. Looks like something conflicting there.
r
hmm. Figured out the cause of the 500 error?
t
The culprit was Sentry in the next.config.js file. I've commented out the code and now the issue no longer exists. I'm going to debug this issue and figure out why Sentry was causing authentication issues. Will update when I find out.
r
sounds good
thanks
t
@rp The supertokens api auth route breaks when Sentry (https://docs.sentry.io/platforms/javascript/guides/nextjs/) is added. One example is when I try login via Google, the api endpoint returns 404, and " Error [ERR_STREAM_WRITE_AFTER_END]: write after end" is logged to the nextjs terminal. My api route is exactly like the example https://supertokens.com/docs/thirdpartyemailpassword/nextjs/setting-up-backend#2-expose-the-supertokens-apis I've been fiddling about, and for some reason if I comment the following everything works fine. if (!res.writableEnded) { res.status(404).send('Not found') }
I dont know how Sentry & Supertokens work under the hood, so I'm a bit stuck. Any insight?
r
So if you add the 404 and then call a route which we have, it still throws a 500 error?
t
https://github.com/getsentry/sentry-javascript/issues/6099 Looks like a known issue with Sentry's code. Nothing supertokens is doing wrong
r
right. So then maybe you can just remove the 404 part perhaps?
t
Yeah, going to remove that and hope no other problems arise.
17 Views