Node Connectivity

This guide will assist you in troubleshooting Nodes that are not connecting to the Nova Cloud platform.

Outbound Connection

Nodes connect out to the Nova control plane, there is no inbound access requirement for the communication of a Node.

This is done via an HTTPS wrapped connection to the Nova poll server, which by default is on port 443.

To test this communication you can use curl from the system with Nova installed:


404 page not found

You should receive that exact 404 message back. If you do not, use -v with curl to add additional information:

curl -v

*   Trying
* Connected to ( port 443 (#0)
*  subjectAltName: host "" matched cert's "*"
> GET / HTTP/2
> Host:
> user-agent: curl/7.68.0
> accept: */*
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* Connection state changed (MAX_CONCURRENT_STREAMS == 250)!
< HTTP/2 404
< content-type: text/plain; charset=utf-8
< x-content-type-options: nosniff
< content-length: 19
< date: Fri, 11 Mar 2022 08:02:39 GMT
404 page not found
* Connection #0 to host left intact

novac and novac.toml

The Nova client is shipped as two components:

  1. novac the binary which needs to run
  2. novac.toml the config file for the above binary

toml Example

Your .toml file should look like this:


You can see the Id and Key fields, obtained via the Node Install page, and then the Host to connect to.

This host can be different for other Nova installations - hosted clients, clients in different territories, etc. Ensure it is correct for your system, but for most cases the default is fine.

Manually running novac

To debug further, you may manually run "novac" after ensuring it's stopped (don't run two copies) to see debug output about connectivity.

service nova stop
killall novac