Topic: Posts page on profile returns a 502 error.

Apologies if I didn't put this into the right forum, I feel it might be feedback if there's a bug with the site. I've been having this problem for the past week or so, whenever I check my posts from my profile, it returns a Cloudflare page with a 502 error. I usually will peek at posts on my profile to find a specific post I posted. I don't know if there's any way to fix it, or if it's a bug no one is aware of. If it's the latter, hope this makes someone aware of it.

I tried going to both your posts page and mine out of curiosity. I did see that mine's been giving the 502 error, too. It did say that something's wrong with the host, though, so it's probably a glitch within the site. Not sure how to fix it myself, but you could try waiting an hour or two, maybe even a day, and see if it's fixed.

@MarioLover92 From the sounds of it, it sounds like when someone is logged in, it only happens when they go to view their own posts page. Now I just tried your posts page and I got the 502 error for that. Weird it's a host thing, since everywhere else works fine on Nintendo Life.

@Sunsy You should ask @antdickens about that. He's NLife's resident site wizard/web master, so he might be able to either help you out or explain what the heck is going on.

@Sunsy By the way: I got the exact same error, both when trying to view your posts page and my own, so it's definitely a site problem, and not just you:

@ThanosReXXX That's a third time. Hopefully @antdickens is aware of this at least, certainly this is a bug of sorts.

@Sunsy Well, to make absolutely sure, you could also ask people in the Chit-Chat thread to try their own posts page and then report back here, and if they too have the problem, which I suspect they do, then it's most definitely a site-wide issue.

@ThanosReXXX @Sunsy thanks for the heads up, if you give it a try now... hopefully it's working again? Cheers!

@antdickens Just tried looking at my posts page, and the posts page of anyone who posted here. Thanks Ant, it's working now.

@Sunsy you're very welcome, thanks again for pointing out the issue!

@antdickens Yup, working on my end as well. So, what exactly causes this? I'd be curious to know, because over the years, this is not the first time that I've personally come across this specific error.

@ThanosReXXX just inefficient code to be honest, which is now dramatically more efficient

@antdickens I'll remember that, the next time the error pops up. Here's hoping it won't...