-
-
Notifications
You must be signed in to change notification settings - Fork 5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Report bugs to OpenProvider dns api #2104
Comments
How do I use the Openprovider API? I am trying to use it the following way: Only now I am getting into a finite loop. Do I have to have my DNS records in a specific way to make this work? I am having the following zone file at OpenProvider:
|
Do you have the debug output? I sadly no longer have anything hosted at OpenProvider so it's hard for me to guess what it could be. |
Appears to work when I don't have any A records. Let me try to get a debug log for you :) |
The error is on https://github.com/Neilpang/acme.sh/blob/master/dnsapi/dns_openprovider.sh#L62, the sed statement doesn't seem to see the match and thus the list of records never changes. Not sure yet why this is the case... |
Sorry, my shell scripting skill is like non-existent. Anyway I could assist you? I did notice that when I don't have any A records (e.g. *.domain.co) it's working fine. Could it be falling over the case that A record for *.domain.co exists for which I am also requesting a certificate? |
Nah, it's just not marking an item it dealt with as "done", and thus gets stuck in that loop. The sed statement is supposed to remove the item that it just dealt with from the list of items, but somehow that isn't working. May be some special characters weirdness, not quite sure why, probably someone whose POSIX shell scripting is less rusty could solve it in a second. |
Oh okay, I hope someone can help us then :) |
Not sure, how to progress this. |
I'm having the same loop problem as @weyert. It would be nice if someone could fix it. |
acmesh-official#2104 Fix wildcard handling & custom NS config for OpenProvider DNS
Hi all, Also lowered the TTL for the temporary acme record to 10 min, so you can retry after 10 minutes if it fails and you don't have to wait for a day until the records times out from dns-caches. Will submit a pull-request with the changes. |
Thanks @Ritbit that's great :) |
Tried Acme.sh with openprovider_dns, all I keep getting is a |
Same here... I've used the dns api on openprovider with dehydrated (I wrote that backend for dehydrated), but was looking into acme.sh since it has wider support, but giving me issues with openprovider. It seems that API failures are printed in red, but then don't trigger stopping further requests/tests if the field was added. [Mon 23 Nov 2020 10:01:41 PM CET] existing_items='A45.11.28.1086400NSns3.openprovider.eu3600NSns2.openprovider.be3600NSns1.openprovider.nl3600MXmail.sig-io.nl1086400AAAA2a0e:5700::1086400' |
Removing 'NS' from line 72 worked for me.... the API docs also say the allowed field types are: One of the following data types: A, AAAA, CNAME, MX, SPF, SRV, TXT, TLSA, SSHFP, CAA So... NS is not allowed by default... but is returned from the api (and automatically added it seems) |
It also looks like the dns_openprovider.sh just replaces the entire zone/config, instead of just adding/removing a single record: In the control-panel: As opposed to the script used in dehydrated which adds/removes individual txt records: Doing it this way would avoid issues with unknown or not-allowed record-types, and avoid losing existing records if they might not match the regex (or simultanious updates from other api-calls) |
This plugin should be rewritten to the Openprovider REST API (beta). |
Created a pull request where the NS type is removed so it atleast works again. |
This is the place to report bugs in the OpenProvider DNS API.
If you experience a bug, please report it in this issue.
Thanks!
The text was updated successfully, but these errors were encountered: