Post AG8lBnQjo8a6Az7JFw by mrjunge@outerheaven.club
 (DIR) More posts by mrjunge@outerheaven.club
 (DIR) Post #AG8lBnQjo8a6Az7JFw by mrjunge@outerheaven.club
       2022-02-04T17:42:49.688552Z
       
       0 likes, 0 repeats
       
       @Eidon No idea. I assume it's a routing issue.
       
 (DIR) Post #AG8lfFXyLjLTmCXs2q by alice@bidule.menf.in
       2022-02-04T17:48:07.874098Z
       
       0 likes, 0 repeats
       
       @Eidon it looks like the path to a webpage, and its name suggests it could be a special static page served when a HTTP 500 error is encountered (and that happens to be the HTTP code returned, so it is very likely). Looks like a bug in the software serving it, printing the page's name instead of including it in the returned body. Perhaps this faulty behaviour is somehow linked to the reason behind the actual error encountered when trying to return the main page ? Because there are two errors piled-up here: the server is unable to return the main page to your browser (this is bad in itself), but trying to wrap up and warn you about that, it tripped a second time, producing this cryptic message instead of some useful content that could've translated something like : "ok something's wrong on our end, not something you did, so sorry but you can't browse our site at the mo try later maybe ?"