Hestiacp API error

im trying to setup a master + dns + dns cluster

i have Hestiacp master server setup : s1.domain.com
and Hestiacp setup on : ns1.domain.com
and another hestacp setup on ns2.domain.com

All 3 servers are running
Hestia Control Panel v1.3.5
On Ubuntu 20.04 (x86_64)

i have created the user dns-cluster on ns1 and ns2 when i try to add slave dns to s1
i get this :

[email protected]:~# v-add-remote-dns-host ns1.domain.com 2087 admin password
Error: api connection to ns1.domain.com failed

and same when i try to add ns2.
i have checked $HESTIA/conf/hestia.conf and API is enabled on all 3 servers. i have also tried : v-add-remote-dns-host ns1.domain.com 2087 admin API-KEY with same error.
Any Ideas?

and why is this setting here and why can’t I select yes?

Setting is set when enabling the DNS cluster via command above.

v-add-remote-dns-host ns1.hostname 2087 API-KEY

And not admin api-key

Is API enabled?

and i just tried v-add-remote-dns-host ns1.hostname 2087 API-KEY … same error

Try if this works

Follow this steps:

  1. SSH login into the SLAVE server.
    /usr/local/hestia/bin/v-add-user dns-cluster @secret-password! [email protected]
    /usr/local/hestia/bin/v-generate-api-key

You will get a number such as: znCICA_UsXwmGUB55HXxEyk0MECF_3Sv

  1. SSH login into the MASTER server.
    /usr/local/hestia/bin/v-add-remote-dns-host slave1.mydomain.com 8083 znCICA_UsXwmGUB55HXxEyk0MECF_3Sv

The command will take a while to complete (about 10 minutes for 150 domains)

  1. To test if it works: login to the SLAVE server and enter:
    /usr/local/hestia/bin/v-list-dns-domains dns-cluster
2 Likes

that was basicly how i set it up the first time … so i reformated the vps for ns1 and started over again and followed your steps and got the same results

this is working … but still cannot complete the DNS Cluster command

Maybe it is a stupid question but I hope it helps. Why are you trying port 2087? Is it open in the firewall? Is it configured to listen for api requests?

2087 is my hestiacp admin port… I found out what the problem was … no A Records to ns1 and ns2 …

1 Like