I am trying to setup this and do not seem to be able to find the correct format when creating ACME DNS Challenge Plug for dynu "API Data" filed.
Anyone knows/dealt with this ?
Anyone knows/dealt with this ?
Hi
I do not use this plugin.
But these are the required fileds.
#Client ID
#Dynu_ClientId="0b71cae7-a099-4f6b-8ddf-94571cdb760d"
#
#Secret
#Dynu_Secret="aCUEY4BDCV45KI8CSIC3sp2LKQ9"
#
#Token
Dynu_Token=""
#
#Endpoint
Dynu_EndPoint="https://api.dynu.com/v2"
#
#Author: Dynu Systems, Inc.
#Report Bugs here: https://github.com/shar0119/acme.sh
I do not use this plugin.
But these are the required fileds.
#Client ID
#Dynu_ClientId="0b71cae7-a099-4f6b-8ddf-94571cdb760d"
#
#Secret
#Dynu_Secret="aCUEY4BDCV45KI8CSIC3sp2LKQ9"
#
#Token
Dynu_Token=""
#
#Endpoint
Dynu_EndPoint="https://api.dynu.com/v2"
#
#Author: Dynu Systems, Inc.
#Report Bugs here: https://github.com/shar0119/acme.sh
My main question was and is - what exactly goes into the API Data test field f Dynu and in what format ?
I did manage to setup Dynu certificate using this video https://youtu.be/9vVKazwO1s4 as a base
Steps (maybe someone will benefit):
1. created a new domain via dynu.com <DDNS_DOMAIN>
2. install
https://github.com/acmesh-official/acme.sh/wiki/dnsapi#how-to-use-dns-api
3. Run /root/.acme.sh/acme.sh --issue --dns dns_dynu -d <DDNS_DOMAIN>-d <DDNS_DOMAIN>
it will generate "cert key" and "the full chain certs"
4. Upload "cert key" and "the full chain certs" to Proxmox/Custom Certificates
I think these steps are not optimal yet and may not be fully finalized and hope someone can comment and make additions/corrections.
Thx
Steps (maybe someone will benefit):
1. created a new domain via dynu.com <DDNS_DOMAIN>
2. install
https://github.com/acmesh-official/acme.sh/wiki/dnsapi#how-to-use-dns-api
3. Run /root/.acme.sh/acme.sh --issue --dns dns_dynu -d <DDNS_DOMAIN>-d <DDNS_DOMAIN>
it will generate "cert key" and "the full chain certs"
4. Upload "cert key" and "the full chain certs" to Proxmox/Custom Certificates
I think these steps are not optimal yet and may not be fully finalized and hope someone can comment and make additions/corrections.
Thx
The data I have send you.
API Data
Code:
Dynu_ClientId="<your Dynu Client ID>"
Dynu_Secret="<your Dynu Secret>"
Dynu_Token="<Dynu Token>"
Dynu_EndPoint="https://api.dynu.com/v2"Acme.sh is stand alone and not managed by ProxmoxVE
That format was accepted !
I used Dynu API-Key for Dynu_Token=
is it correct?
How does it run cert updates ?
Thx for helping
Last edited:
I guess to get a certificate I can run Order Certificates Now button, but it's disabled ...
Maybe it has to be in the date range before becoming enabled ...
Maybe it has to be in the date range before becoming enabled ...
Finally got it working
Correction the format as below without double quotes
Dynu_ClientId=<your Dynu Client ID>
Dynu_Secret=<your Dynu Secret>
Dynu_Token=<Dynu Token>
Dynu_EndPoint=https://api.dynu.com/v2
Correction the format as below without double quotes
Dynu_ClientId=<your Dynu Client ID>
Dynu_Secret=<your Dynu Secret>
Dynu_Token=<Dynu Token>
Dynu_EndPoint=https://api.dynu.com/v2
I get what you mean, but the problem with the data is that each provider has different names for the keys and the number varies too.
These plugins are not made by us they come from the provider itself.
We have just included them in your tool change.
These plugins are not made by us they come from the provider itself.
We have just included them in your tool change.
This is exactly the point.
To setup acme is painful and there are bunch of them. If you look at this thread this maybe very useful for somebody else.
I get it’s 3D party and you have to spend time and resources but those details differentiate good s/w from great
of cause, up to you ...
To setup acme is painful and there are bunch of them. If you look at this thread this maybe very useful for somebody else.
I get it’s 3D party and you have to spend time and resources but those details differentiate good s/w from great
of cause, up to you ...
Registered just to say this was the solution: removing the quotes.
This made me lose so much time
I edited the wiki here: https://github.com/acmesh-official/acme.sh/wiki/dnsapi#24-use-dynu-api
Last edited:
Hi,
I am currently trying to figure this out as well. Thank you everyone for the posts above. My current stumbling block is that I could not find where my client_ID is on dynu. Is it the OAUTH2 generated key pair? I was not sure? Eventually I found that was the case, and have made an account to share:
Dynu_ClientId=<your Dynu OAuth2 Client ID>
Dynu_Secret=<your Dynu OAuth2 Secret>
Dynu_Token=<Dynu API>
Dynu_EndPoint=https://api.dynu.com/v2
I am currently trying to figure this out as well. Thank you everyone for the posts above. My current stumbling block is that I could not find where my client_ID is on dynu. Is it the OAUTH2 generated key pair? I was not sure? Eventually I found that was the case, and have made an account to share:
Dynu_ClientId=<your Dynu OAuth2 Client ID>
Dynu_Secret=<your Dynu OAuth2 Secret>
Dynu_Token=<Dynu API>
Dynu_EndPoint=https://api.dynu.com/v2
