the 500 error page is blank

[dzwdz]

20:24 <pushcx> looks like DM replies and search are 500ing
20:24 <dzwdz> with a blank error page which is lovely
20:24 <pushcx> could you report that bug, that the 500 doesn't have an error page? not sure what that is or when that started...

It do be a blank page. Here's what curl says:

dzwdz@fleshwing:~$ curl -v "https://lobste.rs/search?q=acme.sh&what=comments&order=newest"
*   Trying 67.205.189.7:443...
* Connected to lobste.rs (67.205.189.7) port 443 (#0)
* ALPN: offers h2,http/1.1
-snip- irrelevant TLS stuff 
* using HTTP/2
* h2h3 [:method: GET]
* h2h3 [:path: /search?q=acme.sh&what=comments&order=newest]
* h2h3 [:scheme: https]
* h2h3 [:authority: lobste.rs]
* h2h3 [user-agent: curl/7.88.1]
* h2h3 [accept: */*]
* Using Stream ID: 1 (easy handle 0x562e25870790)
> GET /search?q=acme.sh&what=comments&order=newest HTTP/2
> Host: lobste.rs
> user-agent: curl/7.88.1
> accept: */*
> 
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
< HTTP/2 500 
< server: nginx
< date: Fri, 19 Jan 2024 19:26:17 GMT
< content-type: text/html; charset=UTF-8
< content-length: 0
< x-request-id: 990074a4-fd10-4584-b157-f8aa85828bb2
< strict-transport-security: max-age=63072000; includeSubDomains; preload
< content-security-policy: frame-ancestors 'none'
< 
* Connection #0 to host lobste.rs left intact

I assume there's no consistent way to reproduce it, unless you'd add something like lobste.rs/500 which throws that error on purpose. In fact, the search already got fixed as I'm writing this.

404 works fine, with a proper custom error page.