Metrics for projects packages and pagespeed insights have failed #140
-
Beta Was this translation helpful? Give feedback.
Replies: 7 comments
-
For the projects one I think that's because mix between user account and organization projects (and vice-versa) are not supported. As for pagespeed, 500 errors are usually returned when pagespeed api wasn't able to reach your website.
Since your website is up, maybe check if you have any firewall/fail2ban/bot-blocking rules. For reference, since my website is behind a Cloudflare proxy, sometimes it flagged the pagespeed bot as a spamming/malicious one so I needed to tune it a bit to make it work |
Beta Was this translation helpful? Give feedback.
-
All right thanks! |
Beta Was this translation helpful? Give feedback.
-
I'd like to say that I didn't fix anything on my website, only by running web.dev several times, I made the pagespeed insights back again. |
Beta Was this translation helpful? Give feedback.
-
interesting though |
Beta Was this translation helpful? Give feedback.
-
Yeah I assume since it's just a timeout, sometimes pagespeed succeed to reach your website and sometimes not. I don't think it's possible to increase timeout of pagespeed api though, so I don't have any solution to offer you atm for this problem 😕 |
Beta Was this translation helpful? Give feedback.
-
Commit |
Beta Was this translation helpful? Give feedback.
-
OK thank you for that |
Beta Was this translation helpful? Give feedback.
For the projects one I think that's because mix between user account and organization projects (and vice-versa) are not supported.
I'll look at it this week to fix it 👍
As for pagespeed, 500 errors are usually returned when pagespeed api wasn't able to reach your website.
When testing on web.dev your website I get the following :
Since your website is up, maybe check if you have any firewall/fail2ban/bot-blocking rules.
If every…