Nockchain-backbone-zorp.io server down from too much traffic?

General
1
  • Lots of folks posting issues with Timeout error for nockchain-backbone-zorp.io - me included.
  • The nockchain twitter appears to acknowledge that there may be a server overload issue?
  • curl request of this domain fails as well.
  • Has anyone seen any logs related to a nock being created?

https://x.com/nockchain/status/1925370913605783790

image
image882Ă—210 20.8 KB

1 Like
2

So I guess the endpoint is down

3

Is this similar to what y’all are seeing?

image
image1471Ă—935 24.6 KB

1 Like
4

yes it is. Wait for backbone node improvements

1 Like
5

many guys have the same peer connection issue, what’s the fix for now?

6

image
image1711Ă—670 59.2 KB

start？

7

really thanks for your team’s hard work~

8

we have now fixed the peering issue and miners are connecting to the backbone nodes and to each other to mine

1 Like
9

I still can saw the below errors randomly from the console output, not sure if that’s issue need to be fixed.

"ERROR nockchain_libp2p_io::nc: Failed outgoing connection to Some(PeerId(“12D3KooWEEJuqehkW68pskLwZpfn3ynLjAAGjQazaZRTZikdhb3P”)): Failed to negotiate transport protocol(s): [(/ip4/120.226.158.34/udp/3024/quic-v1/p2p/12D3KooWEEJuqehkW68pskLwZpfn3ynLjAAGjQazaZRTZikdhb3P: : Multiple dial errors occurred:

  • Handshake with the remote timed out.: Multiple dial errors occurred:
  • Handshake with the remote timed out.: Handshake with the remote timed out.)(/ip4/120.226.158.34/udp/39238/quic-v1/p2p/12D3KooWEEJuqehkW68pskLwZpfn3ynLjAAGjQazaZRTZikdhb3P: : Multiple dial errors occurred:
  • Handshake with the remote timed out.: Multiple dial errors occurred:
  • Handshake with the remote timed out.: Handshake with the remote timed out.)]"
10

This is also what I see