Not 100% sure if this is a Summit issue or something in Lemmy more generally. Here’s the post in question:
https://midwest.social/post/10123989
The link to the blog works on my instance for the desktop. Several other users were reporting the link being broken, and it does break for me on Summit, as well.
When I hit the link on Summit, the requests on the server are GET /api/v3/post?id=2024 and GET /api/v3/comment/list?max_depth=6&post_id=2024&sort=Top&type_=All. It looks like it parsed out the “2024” from the original link and tried to use that in a Lemmy API call.
The site is not serving a valid TLS certificate. I wonder if the app browser is rejecting the site because of that (which IMO would be the correct thing to do).
My LetsEncrypt cert expired yesterday. I’ll update that, but it was failing before then.