I've no idea what or where you are getting that error from.
Investigating Error 527 (also included are errors 520, 522, 524, and 525)
- Thread starter casportpony
- Start date
It appeared a moment ago when refreshing the BYC page while I was engaged in conversation.
Saying the website cannot be loaded because the authenticity of the data cannot be verified.
It says to contact the owner of the website to inform them about the problem..
Saying the website cannot be loaded because the authenticity of the data cannot be verified.
It says to contact the owner of the website to inform them about the problem..
That's not an error we or Cloudflare generate.
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.
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.
I am not complaining, just letting you know about it.
As I am logging in from Germany, Europe, with an old laptop using firefox, who knows what might come in between?
Yeah, the error you reported if you Google it suggests it's something with Mozilla.
These are the only errors railgun has logged
Time is CDT.
It can't happen to everyone, unless there is an actual server outage, because Cloudflare takes incoming connections from their multiple datacentres (closest to your location), and routes the connection internally on their network to the railgun handler on the server. Each of their datacentres has a permanent connection to the server.
Code:
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
May 23 21:40:01 coop rg-listener: [65432828187e0fb7-SJC] Error getting item cf_rg_v5_s_dict_0_4bf1516e5222384f1aca565aa763d7d7 from memcached: read tcp 127.0.0.1:32726->127.0.0.1:11212: i/o timeout
May 23 23:21:57 coop rg-listener: [6543bd77dac4100c-ATL] cacheDictionary: memcached error write tcp 127.0.0.1:40862->127.0.0.1:11212: i/o timeout adding cf_rg_v5_s_dict_0_ea046d32f840e708c186a73817bae40b
May 24 00:19:22 coop rg-listener: [65441137994b3776-MEL] origin timeout: dial tcp 209.222.104.187:443: connect: connection timed out
May 24 00:19:53 coop rg-listener: [654411fa0f9d17cc-MEL] origin timeout: dial tcp 209.222.104.187:443: connect: connection timed out
May 24 00:20:27 coop rg-listener: [654412cc7f2afe8d-MEL] origin timeout: dial tcp 209.222.104.187:443: connect: connection timed out
May 24 00:38:11 coop rg-listener: [654428bf8acf0803-ATL] origin timeout: net/http: timeout awaiting response headers
May 24 09:04:17 coop rg-listener: [6547127c9cc35d98-IAD] cacheDictionary: memcached error write tcp 127.0.0.1:59546->127.0.0.1:11212: i/o timeout adding cf_rg_v5_s_dict_0_cf5ee6b2d80a516fa18cac35fda80ede
May 24 10:38:22 coop rg-listener: [654797edb9e0f77c-DEN] origin timeout: net/http: timeout awaiting response headersTime is CDT.
It can't happen to everyone, unless there is an actual server outage, because Cloudflare takes incoming connections from their multiple datacentres (closest to your location), and routes the connection internally on their network to the railgun handler on the server. Each of their datacentres has a permanent connection to the server.
Similar threads
New posts New threads Active threads
-
Threads with more replies in the last 15 days
-
-
-
24 hour old chick with legs and feet issue.- Started by Beckys Birds
- Replies: 111
-
-
Need advice for the best vines and plants for in a chicken run!- Started by ChickenShepherd_6116
- Replies: 98
-
