Author Topic: 502 bad gateway error  (Read 248 times)

0 Members and 1 Guest are viewing this topic.

Offline
*
502 bad gateway error
« on: July 02, 2019, 02:36:04 PM »
After os update all my domains were running perfectly.

But today when i access all my domains.

it shows 502 bad gateway error.

Prior to this i only used one command i.e.
Code: [Select]
sh /scripts/update_cwp
This is annoying as it happened suddenly.


Offline
***
Re: 502 bad gateway error
« Reply #1 on: July 02, 2019, 02:50:17 PM »
After os update all my domains were running perfectly.

But today when i access all my domains.

it shows 502 bad gateway error.

Prior to this i only used one command i.e.
Code: [Select]
sh /scripts/update_cwp
This is annoying as it happened suddenly.


Are you using CloudFlare? It had an issue a few minutes ago.
All my sites showed 502 for 6-7 minutes due to that.

Offline
*
Re: 502 bad gateway error
« Reply #2 on: July 02, 2019, 03:14:45 PM »
Its due to cloudflare

Offline
*
Re: 502 bad gateway error
« Reply #3 on: July 03, 2019, 08:00:50 AM »
After os update all my domains were running perfectly.

But today when i access all my domains.

it shows 502 bad gateway error.

Prior to this i only used one command i.e.
Code: [Select]
sh /scripts/update_cwp
This is annoying as it happened suddenly.


Are you using CloudFlare? It had an issue a few minutes ago.
All my sites showed 502 for 6-7 minutes due to that.

Yes i am using CloudFlare. But Cloudflare says its because of the status sent by origin server.

Offline
*
Re: 502 bad gateway error
« Reply #4 on: July 03, 2019, 05:33:08 PM »
Its due to cloudflare

Yes confirmed by cloudflare..
Received a mail for the same:

Quote
Today at approximately 13:42 UTC we experienced a global service disruption that affected most Cloudflare traffic for 27 minutes.

The issue was triggered by a bug in a software deploy of the Cloudflare Web Application Firewall (WAF) which resulted in a CPU usage spike globally, and 502 errors for our customers. To restore global traffic we temporarily disabled certain WAF capabilities, removed the underlying software bug, then verified and re-enabled all WAF services.