Commit Graph

5 Commits (e02f07d3568d411b453b2855072d16bea5e96e82)

Author SHA1 Message Date
Aleksandr Kunin 0717f8591c Update to Vultr Api v2
- change endpoints
- change Api-Key header to Authorization: Bearer
neil 19d7c2b336 fix bug
Vadim Kalinnikov e484f32b1a - Return shell detect via env
Vadim Kalinnikov bc396e7a90 Small fix in dns_vultr.sh
neil 55dea4ee9d
sync ()
* support jdcloud.com

* fix format

* ttl 3000

* Escape slashes ()

* Change 1.1.1.1 to 1.0.0.1 to probe compatibility ()

As we can see, 1.1.1.1 is not routed or routed to an Intranet devices due to historical reason. Change 1.1.1.1 to 1.0.0.1 will have a better compatibility. I found this problem on my Tencent Cloud server.

* check empty id

* fix error

* Add dnsapi for Vultr ()

* Add Vultr dns api

* PushOver notifications ()

* PushOver notifications, using AppToken, UserKey, and optional sounds

* fix errors

* added dns api support for hexonet ()

* update

* minor

* support new Cloudflare Token format
fix https://github.com/Neilpang/acme.sh/issues/2398

* fix wildcard domain name

* add more info

* fix https://github.com/Neilpang/acme.sh/issues/2377

* fix format

* fix format