Never seen this error before - Railgun

BYC has been very slow for about 2 days now. I'm relieved to see that it isn't just me :)
Same here. Why I made a thread as I was pretty sure it wasn't just my computer.
It is still lagging badly, and sometimes I get the railgun error, sometimes not.

they won't disappear after I hit reply
Just found a reply that stayed in reply box even tho it posted hours ago.
 
Code:
Nov 21 12:15:20 roost rg-listener: [e273e7091b] could not read request: WAN timeout
Nov 21 12:15:21 roost rg-listener: [45ef825df1] could not read request: WAN timeout
Nov 21 12:15:24 roost rg-listener: [307cdb89bb] could not read request: WAN timeout
Nov 21 12:15:35 roost rg-listener: [b8eac82a0e] could not read request: WAN timeout
Nov 21 12:15:57 roost rg-listener: [43bec93f57] could not read request: ID canceled
Nov 21 12:16:12 roost rg-listener: [c92a58d14f] could not read request: ID canceled
Nov 21 12:16:15 roost rg-listener: [5fd73f23b0] could not read request: ID canceled
Nov 21 12:16:15 roost rg-listener: [ec953f8825] could not read request: ID canceled
Nov 21 12:16:15 roost rg-listener: [ea2d12aca4] could not read request: ID canceled
Nov 21 12:17:40 roost rg-listener: [1061fac26b] could not read request: ID canceled
There were errors today reporting that the railgun listener was timing out on the WAN connection (that's indicative of an issue between the server and Cloudflare) but those stopped at 12:15 CST

Nothing has changed on the server in terms on config in weeks. No other errors are being logged in terms of server errors / nginx / php issues.
 
1669077057772.png


Looking at my external monitoring, something has been happening with the network being slow, but then as stated, it's been resolved around 6 hours now. It's more obvious from certain monitoring locations (San Francisco was really obviously impacted, but Amsterdam wasn't)

1669077149627.png
 

New posts New threads Active threads

Back
Top Bottom