Search results for query: *

Infrequent occurrences of these....we can't really do anything about them, if you aren't having to do anything on your end to recover, other than try again, suggests this is just a temporary issue.

These are the only errors railgun has logged May 23 15:38:07 coop rg-listener: [654111a29edc02b0-SEA] origin timeout: net/http: timeout awaiting response headers May 23 16:37:57 coop rg-listener: [65416d506ce0f321-ATL] origin timeout: dial tcp 209.222.104.187:443: connect: connection timed out...

Yeah, the error you reported if you Google it suggests it's something with Mozilla.

But there isn't anything wrong with the authenticity of the data. Please all bare in mind, the site serves almost 2 million page views per day, so a few errors (based on the fact it's the internet), can be expected as we can't control every aspect of peoples access.

That's not an error we or Cloudflare generate.

I've no idea what or where you are getting that error from.

It's similar, because basically Cloudflare are saying they can't access the server, but there are hundreds of requests in that same minute 18:20 UTC (server time is UTC -5) grep "23/May/2021:13:20:" access.log | wc -l 3226

I'm seeing quite a few sites behind Cloudflare having issues at the minute, not specific to this one.

You got this error specifically at the time when we restart the railgun application on the server. Nov 22 07:30:01 coop systemd: Stopping LSB: Railgun listener... Nov 22 07:30:01 coop railgun: Stopping railgun: [ OK ] Nov 22 07:30:01 coop systemd: Stopped LSB: Railgun listener. Nov 22...

So you have issues with cloudflare enabled, and now reporting it's slow with cloudflare disabled? With the amount of people on here, @Nifty-Chicken will have to make a decision about how this goes further.

Has anyone seen any issues since we disabled Cloudflare (other than the recent SSL issue that has been reported)?

I've fully disabled cloudflare, so all access will be straight to the server. Let me know if you have any further issues.

Thanks, if it happens again, we do need the specific example, as it provides a unique reference that we can pass back to Cloudflare.

When? That's a different error, this is pointing very much at Cloudare or your connection through cloudflares specific site. @Nifty-Chicken

See how it goes the rest of today, and if you get any more, please post them here :)

I honestly have no idea why you specifically are getting all these errors. There are thousands of visitors on the site constantly, all connecting the same way.

Any errors just now was due to me restarting a process, no need to report them.

Thanks, I can tie that error up with errors from the logs on the server. It's connectivity back to Cloudflare from the server that appears to be causing the issue.