Hi all, I have recently installed a new version of Hestia on two servers, one is supposed to be a DNS slave.
Issue: v-add-remote-dns-host fails with “api connection failed” despite API responding correctly
Setup:
-
Master: Hestia on Ubuntu 24
-
Slave: Hestia on Ubuntu 24, fresh install
-
Attempting Master → Slave DNS clustering
What’s been confirmed working on Slave:
-
Port 8083 reachable from Master via telnet
-
Master IP whitelisted in API allowed IPs
-
Legacy API enabled
-
dns-user exists with dns-cluster/DNS Sync User role
-
API key created under admin with sync-dns-cluster permission
-
DNS_CLUSTER_SYSTEM set to hestia-zone in hestia.conf
Manual API call works:
bash
curl -s -k "https://slave-ip:8083/api/" -d "access_key=KEY&secret_key=SECRET&cmd=v-list-users&returncode=json"
Returns valid user list.
But this returns nothing:
bash
curl -s -k --data-urlencode "hash=accesskey:secretkey" --data-urlencode "returncode=yes" --data-urlencode "cmd=v-list-sys-config" https://slave-hostname:8083/api/
```
**v-add-remote-dns-host always returns:**
```
Error: api connection to slave failed
Tried both combined hash format and split access/secret key arguments, and legacy admin/password authentication — all fail.