Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds dnsapi support for HestiaCP control panel.
There are some prerequisites before trying to use this dns api script:
Log in to HestiaCP panel as admin or user
Go to Server -> Configure -> API if logged in as admin otherwise if a normal user, click on your profile on top right, and click Access Keys on the upper menu above "Edit User" field
Choose update-dns-records as Access key role
Copy Host, Access Key, and Secret Key
Login to our HestiaCP server as root, and go to /usr/local/hestia/data/api
The file "update-dns-records" should contain this line in order for this script to work:
ROLE='user'
COMMANDS='v-list-dns-records,v-change-dns-record,v-delete-dns-record,v-add-dns-record'
By default, only v-list-dns-records and v-change-dns-record are enabled.
export these variables in your shell or add them in a file and source them.
export HESTIA_HOST="https://panel.domain.com:8083"
export HESTIA_ACCESS="your_access_key"
export HESTIA_SECRET="your_secret_key"
export HESTIA_USER="your_username"
NOTES:
for wildcard certificates to work, you need to use LetsEncrypt V2 provider, not Alpha ZeroSSL which is default in acme.sh
domains available for requesting SSL certificates will be the ones defined under your HestiaCP username (HESTIA_USER).
Issues:
DNS test is successful but your Github actions randomly fails on docker acmetest in the middle of acme.sh processing stuff.