502's don't affect a single page, they are site wide.
Really, there's often only one thread or part of the site, such as the projects index page that we can't get to.
Yes, 502 means that there is an internal server error where the PHP process is not availble for Nginx to communicate with. For those that don't understand the process, this is how an incoming HTTP request is served.
1) Your client establishes a connection with the server (Nginx)
2) Your client asks the server for a resource
3) The server determines if the resource is a static file (ie, image), or dynamic (php script in this instance).
4a) For static the webserver just grabs the file on disk and send's it out.
4b) For dynamic the webserver connects internally to the PHP service on the server and asks it to run the script
502 errors are when the webserver can't connect to a non busy PHP service... the cause can be any number of things, bad script, PHP crashed, MySQL didnt return in a timely manner and all the PHP processes are hung up waiting. etc...
It doesn't matter what page, it doesn't care at this point. It can happen on any page at any time. Unfortunately CF do strange things with caching the 502 error (this likely can be resolved but up till now I have not investigated this aspect of the issue yet).
Because tons of people use the 'show new replies' feature, when we get 502 errors it has a high probability of being cached at cloud flare as broken. CF starts dishing out the static 502 even after the issue has been resolved for that particular page, which is why a force refresh will resolve it as this instructs CloudFlare to go and fetch the content again anyway.