Errors when connecting nodes

Errors that occur when connecting nodes may be incompletely displayed in the KUMA web interface. You can use the developer's console of your browser to view the full server report.

The table below lists the errors that may arise when connecting KUMA nodes into a hierarchy, and includes recommendations on resolving those errors.

Errors that occur when establishing a connection to a node are displayed in pop-up windows in the lower part of the screen. Errors in already connected nodes can be viewed in the KUMA web interface under Settings → Hierarchy → Structure. The error text is displayed when you move your mouse cursor over the red triangle icon next to the node that encountered the error.

Error message	Possible cause of the error	Recommended remediation
`failed to exchange settings with child: <Post request for child node address>: connect: connection refused`	Connection refused. There was an attempt to add a child node that did not add the certificate of the parent node.	First connect the parent node on the child node, then add the child node on the parent node. Verify that the hierarchy is enabled on the child node.
`You cannot add your own KUMA node as a parent node or child node.`	You cannot generate a cyclical structure out of KUMA nodes.	Make sure that the hierarchical structure you are creating is a tree structure.
`corrupted certificate`	Invalid certificate.	You must check the certificate file.
`failed to exchange settings with child: <Post request for child node address>: context deadline exceeded`	Connection could not be established due to exceeded response timeout.	Verify that the child node machine is running.
`failed to exchange settings with child: <Post request for child node address>: x509: certificate has expired or is not yet valid`	Connection refused due to invalid certificate.	Make sure that the child node certificate is valid. Make sure that the system time of nodes is synchronized with the NTP server.
`failed to exchange settings with child: <Post request for child node address>: certificate signed by unknown authority (possibly because of "x509: invalid signature: parent certificate cannot sign this kind of certificate" while trying to verify candidate authority certificate "<node name>"`	Connection refused due to invalid certificate.	Make sure that the parent node certificate is valid.
`failed to exchange settings with child: <Post request for child node address>: dial tcp: lookup <child node address> on <IP address of child node>: no such host`	Child node certificate contains a non-existent FQDN.	Make sure that the child node certificate is valid.
`Already exists`	This node already exists within the structure.	Check the hierarchical structure that you are trying to build.
`The parent node is already indicated as a child node.`		Do not connect a parent node that is already a child node within this hierarchy.
`Failed to query branch {"branchID":"<branch ID>","branchName":"<node name>","branchFQDN":"<node FQDN>","error":"Get \"<URL of child node>/children\": remote error: tls: bad certificate"}`	Child node deleted the parent.	The child node must connect the parent node.
`error: <Post request for child node address>: read tcp <IP addresses of nodes>: read: connection reset by peer`	Invalid ports are indicated in node connection settings.	Make sure that the correct port is indicated in the node settings and that a valid certificate is being used.
`"error":"Get \"<Child node URL>/children\": proxyconnect tcp: x509: certificate signed by unknown authority"`	Connecting to a node using wrong proxy server settings.	Make sure correct proxy server settings are used.

Page top