500 error on Cloudflare ORD datacenter

I’m having 500s error connections, all from the ORD Cloudflare datacenter. This is a Cloudflare error, not from my side.

# 500 Internal Server Error

Edit: This morning I’ed the same errors from MIA datacenter (already fixed)

Cloudflare didn’t said anything yet, but was already resolved.

The incident was between 19:20 to 19:30 UTC

Again incident on ORD datacenter.
21:37 UTC to 21:53 UTC - Oct 23

2021-10-24T02:35:36.194Z UTC - ORD datacenter
500 Internal server error

Error 100% initialized in the CF Datacenter, not from my side. I’m 100% sure (I’m not using Nginx and the 500 was generated by an Nginx server :wink: )

No one from Cloudflare team will fix this, right? (I’ve a Pro plan)

I’m not sure why you’d say that. Have you let them know?

Automatic response from CF support team:

Thank you for contacting Cloudflare Support.

A 500 error is a server-side error indicating that the origin web server had an error during the request. Since Cloudflare does not generate 500s, you would need to work with your hosting provider to examine your error logs and identify potential issues.

This is a CF error (only in ORD datacenter), I’m sure :wink:

If you’re on a paid plan, a reply to their bot will re-open the ticket. If you’re on a free plan, post the ticket # so we can escalate it. Contrary to what you may have heard, Cloudflare does try to fix problems.

I’ve a Pro plan, I already replied the ticket. I’ll you updated if I receive a response from them

1 Like

Let us know if you don’t get a response and we can escalate a ticket # for whoever comes in tomorrow morning.

Since the response body contains “cloudflare-nginx” the issue persists with Cloudflare and is NOT and issue with your website! You should notify Cloudflare of this error, be sure to include the following information

  • Your domain name
  • The time and timezone of the 500 error occurrence
  • The output of from the browser where the 500 error was observed (replace with your actual domain and host name)

Ticket: 2287932
Closed automatically.

@AppleSlayer Yes, I know that the issue is from Cloudflare, but they say that is my issue, since the server name is “cloudflare-nginx” :wink: (and I’m not using Nginx, I’m using HAProxy…)

Timestamps, all in UTC:

• 2021-10-23T12:31:14.601Z - MIA
• 2021-10-23T12:55:45.662Z - MIA
• 2021-10-23T18:12:31.354Z - ORD
• 2021-10-23T19:20:40.397Z - ORD
• 2021-10-23T19:26:27.744Z - ORD
• 2021-10-23T19:29:49.937Z - ORD
• 2021-10-23T21:37:14.694Z - ORD
• 2021-10-23T21:39:03.772Z - ORD
• 2021-10-23T21:53:33.546Z - ORD
• 2021-10-24T02:35:36.194Z - ORD

MIA was already fixed on Oct 23: Cloudflare Status - Miami, FL, United States - (MIA) is experienced degraded network connectivity

I haven’t the trace Ray ID because the server responded a generic 500 error and didn’t generated the Ray ID.

The last error was past Saturday. Maybe was already fixed automatically. I don’t know, but I know that the errors was generated on Cloudflare datacenter. 100% sure.


<head><title>500 Internal Server Error</title></head>
<body bgcolor="white">
  <center><h1>500 Internal Server Error</h1></center>

I’ll keep you updated if I see the error again, thanks for try to help with this. With these type of errors Cloudflare not have the best support team, because the major times the errors cames from the Origin and CF won’t to wast their time, it’s comprensible.

With a Pro plan, you should just be able to reply to the ticket autoresponse to automatically re-open it. Does that not work for you?

@domjh Yes, I’ve a Pro plan. The timeline was.

  1. I sent the first email (open ticket)
  2. Cloudflare bot response: A 500 error is a server-side error indicating that the origin web server had an error…
  3. I replied again
  4. Kay L. from Cloudflare response and close the ticket
  5. I replied again
  6. Bot respond that the ticket was closed ¯\_(ツ)_/¯

But don’t worry, the error didn’t appear again since Saturday. Seems that was fixed lonely.

Did they also say it was an issue on your origin or did they actually look at a potential issue on their side?

I’m glad to hear that, do let us know if it happens again though and we’ll push it through our escalation process.

Said that the issue was on my origin.

I don’t know what happened, was the exact same issue that I get from MIA datacenter when was down last weekend. But there was resolved as mentioned in the CF status page.

And in another news… I’m having a new issue… :roll_eyes:

Now I’m getting errors 502.
I’ve a log each time that a user receive a 5xx error and I had 56 errors at 2021-10-26T00:28:37.024Z UTC.

Endpoint: https://MY_DOMAIN/cdn-cgi/trace


<head><title>502 Bad Gateway</title></head>
  <center><h1>502 Bad Gateway</h1></center>


More timestamps (UTC):

To keep a support ticket open (with a free plan) you may need to reply several times before it remains open and doesn’t close!

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.