500 error suggestions

[clarkwinkelmann]

Based on a suggestion from @luceos I'm thinking of doing the following:

In the requests list which is shown in a scan or on a fail page, make the following changes:

• Try to show a no-js preview of the error page, this would help troubleshoot things like Cloudflare errors where the explanation is shown on the page but is hard to read when looking at the raw HTML
• Show a guess of where the error originates from. "Oops" and boot errors would be shown as "Flarum error", Cloudflare pages would be shown as "Proxy error" and others would be shown as "webserver/PHP errors"
• For each guess, a short explanation of where the logs could be found
• Instead of just listing "500" in a badge in the list, the guessed error type could actually be shown as a badge
• I could also auto-expand the first request error if there's a single one since the scan will stop right away if the homepage cannot be reached

[luceos]

Communities in a failing state could be removed after a couple of days I guess..

[clarkwinkelmann]

You mean from the showcase? That part is already handled by the ping system, which is not great but will remove forums that error after a few tries. That logic doesn't care if it's a Flarum error or not, and I don't really think it should.