If your Awesomate-hosted n8n instance is showing a 502 Bad Gateway error, don't worry — this is a server-side response, not something caused by anything you've done. In most cases it's down to a small mistake in the address you're visiting, and it's quick to resolve. This article explains what the error means and walks you through what to do.

Image Placeholder

What a 502 Bad Gateway error means

A 502 Bad Gateway error is returned by a server when it can't get a valid response from the service it's trying to reach. In the context of your Awesomate-hosted n8n instance, it generally means your browser reached our infrastructure but couldn't be connected through to a running n8n instance at the address you requested.

This is a server-side condition. It is not caused by your workflows, your login, your browser, or anything you've configured — so there's nothing on your end that's "broken". The most common reason you'll see it is simply that the URL being used isn't quite right.

First, check you're on the correct URL

Before anything else, confirm you're visiting the exact address for your n8n instance. A surprising number of 502 errors come down to a small difference in the domain. Your n8n instance lives at:

https://subdomain.awesomate.io

where subdomain is replaced with your own subdomain.

  1. Check the domain ending. Your instance uses .awesomate.io. Make sure you haven't accidentally used .awesomate.ai instead.
  2. Check the subdomain. The part before .awesomate.io must be your own subdomain, spelt exactly as it was provided to you.
  3. Check for typos. Even a single misplaced character will route you somewhere that isn't your instance and can return a 502.
  4. Try loading the corrected URL again. If the address was the issue, your n8n instance should now load normally.

If the URL is correct and you still see the error

If you're 100% certain the URL you're visiting is the exact, correct address for your n8n instance and you're still getting a 502, then it's likely an infrastructure issue on our side rather than anything to do with your setup.

The good news is that this is very unlikely thanks to the fallbacks we have in place to keep instances up and online. In the rare event it does happen, our monitoring alarms are designed to alert our team automatically so we can investigate and, where needed, restart the affected container.

To make sure we're aware of your specific situation and can confirm everything is back to normal for you, we recommend you also get in touch so we can check your instance directly.

How to get help

If you've confirmed your URL is correct and the 502 error persists, submit a support ticket so our team can investigate and restart your container if required. When you reach out, it helps us if you include:

  • The exact URL of your n8n instance (e.g. https://subdomain.awesomate.io).
  • The time you first noticed the error.
  • A screenshot of the 502 page, if you have one.

You can contact us at hello@awesomate.ai, and you can manage the rest of your account from the Awesomate Hub. We'll get your instance back online as quickly as we can.