I received a `HTTP 500` error on a public dashboar...
# ask-questions
a
I received a
HTTP 500
error on a public dashboard URL. How can I troubleshoot this?
Experiment ID:
exp_19g621m8xdyhtw
s
Looking into this...
I couldn't replicate this with other links. Did you create this link and able to try creating the link again?
a
The link on the experiment doesn't change for the experiment if I "unshare" and "reshare" 🤔
I am thinking that it is an issue with the underlying query
But the "internal" dashboard renders fine: https://app.growthbook.io/experiment/exp_19g621m8xdyhtw
Only the public URL fails with a 500 error...
🤔 1
s
What if you try with a different experiment?
And the setting here is "Anyone with the link"?
CleanShot 2025-04-14 at 17.26.55.png
a
New experiments work fine, but they also turn into 500s when I generate impression/metric data. Wondering if I am fudging up the experiment configuration in some way.
Just curious how I can debug the 500 error. It doesn't have anything useful in the HTTP response as it is a web response, not an API one.
Seeing this in the
view source
on the errored public page:
Copy code
{
  "props": {
    "pageProps": {
      "statusCode": 500
    }
  },
  "page": "/_error",
  "query": {},
  "buildId": "WfLF3oiZCoH96O_zlugqh",
  "isFallback": false,
  "isExperimentalCompile": false,
  "err": {
    "name": "Internal Server Error.",
    "message": "500 - Internal Server Error.",
    "statusCode": 500
  },
  "gip": true,
  "scriptLoader": []
}
s
I'm not sure. I'm going to ask engineering if they have any insight. When you say "generate impression/metric data," what do you mean exactly? I'm looking to find some repeatable steps to help us debug.
a
Hey, thanks for the quick responses! By impression/metric data, I am just referring to the underlying metrics for the dashboard. Exposure is probably a better word than impression. As long as there is no data, the public dashboard URL loads the empty state just fine. But, once there is some data, the public dashboard URL returns a 500. The internal dashboard URL seems to render fine.
s
Thanks. I'll relay this to the team.
🙌 1
a
Thanks!
f
This should be fixed now. Thanks for catching this bug!
a
Nice! Can we make this easier to self-troubleshoot in the future?
f
Yeah, definitely. We should have better error handling on that route that passes more informative messages to the front end. These public routes go through a very different flow from the rest of the app, so they aren't quite as robust yet.
✅ 1