502 - Bad Gateway BUT...My website is up live - Google Crawl/Fetch 502 - Nginx re-direct loop SSL? - 29/04/2018 14:25 EDT

I've recently launched a website in the past few months and it hasn't been ranking in Google that well so I checked out Google Crawl (in search console) and Fetch as Google (fetch the website via Mobile or Desktop). It never works when fetching on desktop, it gives a 502 - Bad Gateway--something I've never seen before because I can access the website just fine myself, and people are using it fine. So, I thought let me try to fetch the website via Google's Mobile viewer, and it works completely fine (as you can see in the screenshot), so I'm baffled at this point. I have tried other services like Screaming Frog SEO/[login to view URL] and both services give me a 502 - bad gateway, but the site is live and running! My site is running behind Cloudflare via a simple Node.js stack. There's no [login to view URL] file blocking anything, or anything like that. On Cloudflare I have a 'Full (strict)' SSL policy, Always use HTTPS, Automatic HTTPS Rewrites. I have Nginx running using the following (sensitive data removed for security reasons). I've put Cloudflare to SSL off but then I get a bunch of re-directs back to [login to view URL] and I can't load the site, maybe this has something to do with it? I do have sub-domains enabled as well for users websites. I've tried [login to view URL] and it shows my website to be down, but it's actually up...it's very strange! I've attached my Nginx configuration.