Report bugs to one.com dns api #2103
Assignees
Labels
3rd party api
report bugs to dns api, deploy hooks and notification hooks
Comments
Merged
Neilpang
added
the
3rd party api
|
please consider the pull request |
|
The one.com DNS API no longer seem to work. It just keeps looping over and over and finally times out. |
|
Could you please verify in the control panel that the txt records are created? and could you try to use the google dns lookup: |
|
Yes, the txt records are created. What I don't understand is why it's using cloudflare/google dns servers? Edit: |
|
I have tested this for my domains and the result is like yours. I have verified in other tools, that the txt records and some other domains without the txt records and it seems that one.com uses internaly a CNAME "_acme-challenge.yourdomain.com" which will conflict with your acme txt records. Look at: https://help.one.com/hc/en-us/articles/360000297458-Why-is-SSL-HTTPS-not-working-on-my-site-#step-5 With the online tool: https://dnslookup.online/txt.html Some of my domain without the txt "_acme-challenge" record are getting a CNAME pointing "yourdomain.com.acme.webpod11-cph3.one.com". In your case: _acme-challenge.primlogic.se => primlogic.se.acme.webpod9-cph3.one.com I am now testing, to not remove the txt records, so that the records are not internaly fallback to the CNAME. this change can take 24h to take effect. |
|
Okay i have talkt with the support of one.com. |
|
Alright, thanks! |
|
Hey there,
Thanks for the help! |
|
Did you clean up the log? The domain is missing, I see only the TLD. |
|
Hey there, |
|
Can I help in anyway with resolving my issue? |
|
I no longer have an account on one.com, so it is hard for me to support here. Please contact me via email. |
|
i unfortunately, don't have a one.com account since a longer time. i'll request to unassign me. anyone who can take it over? |
|
@DavidOffermanns fixed, please try again with the |
|
Hi, im using a pfSense box with acme cert but to my knowledge its just like using acme.sh like on any linux machine. |
I am seeing exactly the same behavior, it might have something to do with me not correctly interpreting the proxy_acme-challenge cname but I've tried multiple variations and everything returns the error: |
|
Had the same issue and spent the better part of my weekend on solving it. https://github.com/acmesh-official/acme.sh/wiki/dnsapi#77-use-your-onecom-credentials-as-you-would-login-into-the-control-panel I am using the ACME package in pfsense, my solution was:
Now it should work, at least id did for me. |
|
I have the same issue, and I was also using the acme package in pfsense. First I thought it was because I have two factor auth setup for my one.com control panel, but after removing the two factor auth the issue was the same: If I can help debugging this, please let me know. |
|
I can't get the One.com API to add TXT records for a wildcard certificate. First I tried this: Added CNAME record: _acme-challenge.mydomain.com => proxy_acme-challenge.mydomain.com And then ran the command to generate certificate:
This returns the error: But with this setup, the CNAMe record does not even respond, because the record Then I tried something different: Added CNAME record: _acme-challenge.mydomain.com => _acme-challenge.proxy-acme-challenge.mydomain.com (It's intentional that it's Added a "dummy" text record: _acme-challenge.proxy-acme-challenge.mydomain.com = RANDOM_TEXT_STRING And then ran the command to generate certificate:
This returns a similar error: So I get the same It seems no matter what I try, it can't generate the TXT records, and it seems you can't create a sub DNS Zone for a subdomain on One.com either. Also, the target for the CNAME record needs to exist for the CNAME to work, so the documentation under One.com API can't be right. Any ideas, or should I just move my DNS to Cloudflare? |
|
There should be no need for the proxy-cname thing. I'm not sure why that was ever a thing, but it certainly isn't anymore. I just tested today. I'm not certain about the "RESTEASY003065: Cannot consume content type" but do suspect that it's related to a change in authentication system a while back. |
|
Thanks Jacob. What exactly did you test? Can you get the script to add TXT records for DNS validation? I still get the "RESTEASY003065" error, even when trying the normal routine without the Cname proxy. 🤔 |
|
@ameinild - I logged into the control panel and created a TXT record for _acme-challenge. with some random content. I did not test the code provided in this repo, but working at one.com, I'm surprised about the cname-proxy-thing, I can't think of a reason such a thing would be necessary. |
|
Cannot get it to work either, also getting: |
|
hi @jacobbunk , I also get this error. based on your comment, I also tried: Control panel Command executed: acme.sh --issue --force --dns dns_one -d mydomain.one -d '*.mydomain.one' Error log As it seems everything else looks correct before, it might be related to the endpoint custom_records
I would love to make it work to get a wildcard certificate. |
|
@dlegranddk - I have no insights into how that API works, but I would guess that you need to specify 'mydomain.one' rather than '_acme-challenge.mydomain.one' in the POST URL. |
Thanks, I was just reacting as you tested earlier this year. Thanks for the info, so we would need to understand which part of the code is doing this as it seems the "_acme-challenge" is added outside of the specific dns_one.sh code and I understood that the _acme-challenge subdomain is the whole point of let's encrypt certification :/ For the others, as I was looking on One.com FAQ, I also found this SSL documentation, I created a new CNAME and now will see in 24h but I'm pessimistic. |
|
@dlegranddk - if you are using one.com name servers, forget about https://help.one.com/hc/en-us/articles/360000297458-Why-is-SSL-HTTPS-not-working-on-my-site-#step-5 - creating those CNAMEs only makes sense for users that use external DNS and want a certificate for their website hosted at one.com. |
|
Hello, I patched the One.com DynDNS api in pfSense today and now I took a quick initial look at this as well which isn't working either. I can say for sure that there are two problems here:
For now I have to go to bed and I'm not sure when or if I'll even continue with this but for now I have left this comment as a note if anyone else wants to work on implementing a fix. My pull request that fixes the pfSense DynDNS login procedure can be seen here: AnonymousRetard/pfsense@80e1ef0 I took inspiration from this python code which seems to be working, but I never actually tested it (but my php implementation for pfSense logs in similarily): What seems to work now is that we need to get redirected to the login form so we can get the "action" attribute of the "form" tag to learn where to post the login data. Then all we need to do is post "username=USERNAME&password=PASSWORD&credentialId=" to this address. Through this process we need to make sure we keep all the cookies we are asked to set as well. |
|
I'm not really sure how to contribute to this project... or what tools I could use from the shell scripts. But assuming I only have cURL, grep and sed I have figured out that the correct login url could be retrieved like this: Extracting the action attribute from the form tag would be more robust to smaller changes I did not forsee though if some kind of HTML DOM-parser library could be used. The postdata variable will have to be constructed as I documented above: I'm not sure how to handle the required cookies though. I'm not so sure it'll be enough to just try to extract the "OneSIDCrmAdmin" cookie as the code seems to be trying to do today. But the file that will need patching is this one: https://github.com/acmesh-official/acme.sh/blob/master/dnsapi/dns_one.sh and the largest changes would have to be made to the _dns_one_login() function. Other than that I only think it has to be ensured that the $maindomain variable is not prefixed with "_acme-challenge." and the rest should just work. |
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is the place to report bugs in the one.com DNS API.
If you experience a bug, please report it in this issue.
Thanks!
The text was updated successfully, but these errors were encountered: