User / DNS / Ports / TLS
To properly configure Node Pilot, you need to direct a domain or subdomain to the Public IP address of this Node Pilot instance. We recommend using a subdomain so you can add more instances of Node Pilot to the same domain in the future.
Subdomain
Domain
Add these three DNS entries:
- 1.Hostname = [subdomain of your choosing]
- 2.Hostname = *.[subdomain from the step above]
The " * " hostname allows Node Pilot to create second-level subdomains automatically for your nodes. This " * " entry is known as a "wildcard", which is supported by most DNS providers. If your DNS provider does not support wildcards, then you may need to purchase a domain from another provider (we recommend iwantmyname.com).
GoDaddy does not work with 2 letter subdomains. For those using GoDaddy use at least 3 letters.
Example of DNS settings
It is recommended you use a subdomain instead of the top level domain. Unless you have a specific reason to use a top level domain, we advise following the subdomain instructions.
Add these two DNS entries:
- 1.Hostname = @
- 2.Hostname = *
The " * " hostname allows Node Pilot to create subdomains automatically for your nodes. This " * " entry is known as a "wildcard", which is supported by most DNS providers. If your DNS provider does not support wildcards, then you may need to purchase a domain from another provider (we recommend iwantmyname.com).
Example of DNS settings.
PORT FORWARDING: We strongly recommend you always run Node Pilot behind a firewall or home router. This means you will need to set up port forwarding for ports 80, 443, and 26656 to the servers local IP address. Node Pilot requires those ports to operate.
Inside the main screen, Node Pilot displays the status of the state of your ports, DNS, and TLS settings.
Click on each status to configure, and follow the in-app instruction.
Once TLS is configured, Node Pilot will automatically logout your user and reload your instance from your domain.
Last modified 9mo ago