Getting 500 error on main url but not on dev url pointing to same build

When someone signs in on our site (app.aftergame.co) we get a 500 error. However for the same build when pointing to the Cloudflare generated url (6e9c7197.aftergame-web.pages.dev) it works??

Here's the trace:

fl=490f84
h=app.aftergame.co
ip=118.92.87.134
ts=1717214039.329
visit_scheme=https
uag=Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36
colo=SYD
sliver=none
http=http/3
loc=NZ
tls=TLSv1.3
sni=plaintext
warp=off
gateway=off
rbi=off
kex=X25519Kyber768Draft00

fl=490f84
h=app.aftergame.co
ip=118.92.87.134
ts=1717214039.329
visit_scheme=https
uag=Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36
colo=SYD
sliver=none
http=http/3
loc=NZ
tls=TLSv1.3
sni=plaintext
warp=off
gateway=off
rbi=off
kex=X25519Kyber768Draft00

fl=490f84
h=app.aftergame.co
ip=118.92.87.134
ts=1717214039.329
visit_scheme=https
uag=Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36
colo=SYD
sliver=none
http=http/3
loc=NZ
tls=TLSv1.3
sni=plaintext
warp=off
gateway=off
rbi=off
kex=X25519Kyber768Draft00

fl=490f84
h=app.aftergame.co
ip=118.92.87.134
ts=1717214039.329
visit_scheme=https
uag=Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36
colo=SYD
sliver=none
http=http/3
loc=NZ
tls=TLSv1.3
sni=plaintext
warp=off
gateway=off
rbi=off
kex=X25519Kyber768Draft00

I can't see anywhere to see logs for what's happening. On our API server everything looks good so it feels it's happening somewhere in Cloudflare

jordanfinners•6/1/24, 7:41 AM

If you go into your pages deployment, and then go into functions page. You can tail the logs there, it'll only show live logs but then if you try signing in you might see the requests etc

Jjordanfinners If you go into your pages deployment, and then go into functions page. You can t...

EricOP•6/1/24, 9:45 AM

that is surprisingly hidden - thank you this has helped!

Oddly, I'm getting an InvalidTokenError: Invalid token specifiedInvalidTokenError: Invalid token specified on my main domain but not .dev domain - this is after I clear all cookies / local storage.

Not sure why they would be different

jordanfinners•6/1/24, 10:02 AM

Is that a cloudflare error or from your application? Or other third party

EricOP•6/1/24, 10:38 AM

I assume this is something to do with authentication. But it is odd why it works on one URL but not the other that are both pointing to same build.

Getting 500 error on main url but not on dev url pointing to same build

Similar Threads

Similar Threads

Similar Threads