It’s happened to us before. What we have done to help prevent that is have two servers up and deploy to one and when (if) it successfully deploys we deploy to the second server. Our load balancer will take the 502 server out of rotation until it passes a health check.
Bad gateway error points to an app problem but if it is accessible
directly, there may be a server side route handler that’s causing the
problem (guessing) or perhaps a problem with spiderable (unlikely) so at
least to be able to cross out app differences would go a long way in
pinpointing the root cause.
agreed, there should be something, but I couldnt get anything on nginx logs, or website logs.
taken into account my limited to no existent linux knowledge, I’ll take that solution for now
anyway, I’m going to check the latest package additions on my app if I can find something.
Of course I have no clue. My experience is limited in this environment.
I cannot even explain why putting these lines anywhere else under the http does not work.
All I know if that after a lot of search this is the only solution I found. Till I get a better one, or a logical explanation I planning to stick with that.
unfortunately, I don’t have the knowledge and the time to try and figure it out. I do not know where to look actually.
I posted here since I couldn’t find anything related to meteor and actually, I was hoping for a meteor related solution.