500 Server error... but not for everybody
Hello all,
I have a problem with the production of this website : https://launchbase.fr
Maybe you have a 500 visiting it, maybe not, and I have no idea why......
For me right now, https://launchbase.fr works, but https://launchbase-3cl.pages.dev/ was a 500 for everybody (until I bulk redirected)
If I try ANY build, I have a 500 : https://d93ae5f9.launchbase-3cl.pages.dev/ (which sounds weird because well... it was working at some point at least ^^")
The weird part is now :
- No issue locally (ofc)
- But not issue either on the preproduction, which is a separate cf Pages but from the same github (different branch, bot merged right now so the exact same) : https://launchabse.preprod.tech
- Can't be a data problem, my back is on adonisjs elsewhere, it's just a SSR front with nuxt. Server is up and happy (and even when I turn it off or have a problem with it, it's clearly not the error I have ^^")
I'm starting to think it's a cf problem and will be solved automatically soon T_T
Please share if you have any idea, I don't see how I can debug that :/
Thanks
7 Replies
What do your logs say?
?pages-logs
If you're looking to tail a Pages Function you can do so in the UI here: https://dash.cloudflare.com?to=/:account/pages/view/:pages-project/:pages-deployment/functions
or with Wrangler:
wrangler pages deployment tail [deploymentId/url]
I had no idea I could have logs here, thanks ^^"
Not sure if it's what you wanted me to do, I launched the stream logs and visited https://launchbase.fr with my phone (that always have the 500), but it gave me this :

click on one of the logs
and hopefully your app is outputting what the error is
I feel dumb I didn't realise I could click on it....
look like a serious start and obviously my fault, thanks 🙂
omfg the logs made something more obvisou already, it's on the EN version only, so it was random people depending on the default language, I should have thought about it
You most likely just saved my night, thanks a lot :))))
haha no worries :)
ofc the error itself was eventually stupid and easy to fix XD
All solved, thanks again 🙂