I even just tried stripping the core database data transfer just to see if there's too much going on, but it still throws the error. The hell of it is that it was working totally fine all week lol

Hello. I recently experienced 502 issues as well. Being new to the framework, I have been adding comments in my code to remind myself whats going on. After adding comments in a partial, by pushing cmd / , Sublime added html comment syntax and an additional '-->' because I had a comment already. This was breaking my code giving me the 502 Bad Gateway. @including this into a view with even more comments inside, I think was the issue. I also use the Blade comment syntax now {{-- --}} Try clearing any comments that could be breaking code. I hope this helps.

Thank you shabushabu! With your help I was able to see the error log and continue! <3

I have the same issue, I'm in root but the logs files are not helping at all... I've created a post here http://stackoverflow.com/questions/31832714/laravel-4-502-bad-gateway-with-nginx-only-in-one-view