Report bugs to FreeDNS dns api #2305
Comments
Neilpang
added
the
3rd party api
|
api not working :( this is my personal domain in the TOP zone |
|
@maks2018 also... you are using a domain that you personally own right? It is not possible to use one of the FreeDNS shared domain names as they cannot be automatically validated (requires human to fill out a captcha). |
I am using version 2.8.2
Yes, you're right, domain name like xxxxxx.top. Changing DNS does not require input the captcha |
|
@maks2018 I'll need a full debug log. Preferably not posted here but by email. |
|
dkerr64, i sent the log to you |
Thanks, I got it. Will reply directly by email. |
Fix bug reported by @maks2018 in issue acmesh-official#2305 by updating the regex in egrep of the subdomain html page.
|
For anyone that would like to test the fix for bug reported by @maks2018 please try this version of the dns_freedns.sh file... https://github.com/dkerr64/acme.sh/blob/FreeDNS/dnsapi/dns_freedns.sh Thanks |
_egrep_o() function accepts extended regex and on systems that do not have egrep uses sed to emulate egrep. This is failing on the specific regex I was using before my last commit... ae66c6f The problem is that I fixed it by passing in non-extended regex which then fails on systems that do have egrep. So I am no longer using _egrep_o.
|
Im having problems generating a certificate. The record is not being generated in free_dns. Debug output
|
|
@felixgonsug you are not calling acme.sh with the correct parameters. For FreeDNS the correct flag to use is --dns dns_freedns so you are not even getting as far as calling the plugin that talks to FreeDNS. Also, is subdomain.domain.com the real domain or did you edit the debug output to mask the real domain? I ask because the dns_freedns plugin will not work with a "public" domain shared by FreeDNS... it will only work with a domain that you own. Thanks. |
|
@dkerr64 Thank you very much, shame on me, year and a half using acme but was a long time ago i used the issue command. The domain was to mask the real domain. |
|
Hi, old problem not fixed :(
acme.sh - 2.8.4
|
|
@maks2018 Can you try with the version of the plugin at https://github.com/dkerr64/acme.sh/blob/FreeDNS/dnsapi/dns_freedns.sh |
:(
full log in your mail |
|
Adding a note to this thread that issue #2536 was opened reporting a problem with use of [:space:] in tr command. Unfortunately this did not get to my attention until today (because @master-nevi opened a separate issue instead of adding to this issue). And @Neilpang has merged a fix in pull request #2537 which has unfortunately introduced a new bug that now needs fixed. I have added comments to the above issue and pull request pointing this out. With luck this will get addressed before next version released. I believe that this will also fix @maks2018 problem. |
|
@dkerr64 Apologies, I misunderstood the issue opening process thinking that's just what you title new issues for that dns provider. Would it be possible to correct the options on the |
|
Whenever I enter the correct user credentials for FreeDNS in the acme package of PFsense I get: FreeDNS login failed for user xxxx |
The only thing I can think of is whether your userid or password contains any special characters (like a backslash) as I don't think the code does anything to escape those. The way it is supposed to work is that you set the FREEDNS_User and FREEDNS_Password only once (or only once after changing either). Login obtains a "cookie" from freedns and then saves it in /etc/acme/account.conf and then all future logins will use that cookie unless you pass in new user/passwords. So can you look in account.conf and see if a cookie has been saved. If so then run without passing in any user/password and see if that works. If yes, have you changed your password recently? That will require generating a new cookie. David. |
|
I too am getting a login error from the script. I also thought it might be special characters in the password. I changed the password to only alphanumeric and no change. The error from the script is: Checking the content of the file, I see this: So it appears that the while the response is a 200, meaning a successful login, the response content being saved from the script logging in does not include the login cookie and so the script is failing. proxmox: 6.2-4 |
A return code of 200 does not mean login was successful, it means web server successfully replied to the request... that reply could indicate that login was not successful. The FreeDNS script requires the login cookie set by freedns.afraid.org when you login... without that cookie you are not logged in and there is nothing more that the script can do. You should look at the contents of the full HTML page sent back and see what it says -- do that by running with debug level 3 enabled... you will get a lot of debug output but immediately preceeding the statement "FreeDNS login failed for user" you should see the full raw HTML file... here in the source code... Line 165 in 9190fdd |
You're absolutely right. That's actually likely a login failure. I say likely because a successful login should come back with a 302 response redirecting to https://freedns.afraid.org/menu/?ls=1 as well as setting the dns_cookie in that response. The site should probably be throwing a 403 or some other auth error instead of a 200, but whatever. I would like to help with the debug to check out the actual html response, but the script as I'm using it is actually installed as part of another product. Proxmox in my case. So not sure how to enable a debug level or run it independently. Any suggestion on that? Could I replace that line 165 with something else or add a line there that would make it dump that html to a /tmp file? |
|
Figured out my issue in proxmox. The credentials should not have parenthesis around them. Examples suggested entering credentials like this: But changing it to this is what worked for me: |
Good, I'm glad you figured it out. To reply to your earlier question, you could simply have run acme.sh from a command line on any system (that acme.sh would run on) using their test server (--test or --staging) and observe the trace/debug statements. Thanks. |
|
Hi, Old problem is back: [Mon 05 Oct 2020 09:45:28 AM CEST] Domain my.net.pl not found. Retry loading subdomain page (0 attempts remaining) |
|
@as400l I just saw a similar error myself when trying to renew a certificate with an overnight cron job. Unfortunately when I tried to manually renew from command line it just worked. I don't run my cron with debug (maybe I should) so I did not capture what went wrong. Do you see this problem consistently or just occasionally? Thanks. |
|
@dkerr64 I just run it manually with debug and the same thing happens. Maybe it's because i have -d my.net.pl -d *.my.net.pl ? |
|
Anyone ever faced this one? error code 60? |
|
curl error 60 is a SSL certificate problem accessing FreeDNS web site. I'm not sure why this would fail, but that is where to start looking. It may just be temporary problem. |
|
Hey- I seem to be having an issue with the freedns acme script in Proxmox 7.2. It's able to authenticate and get a certificate, but it can't delete the TXT record upon completion. Subsequent certificate renewals fail because the old TXT is still there and needs to be manually deleted. Any help is greatly appreciated! |
|
I have seen occasional problems with DNS verification that magically resolve themselves on subsequent retry. The error you see is very odd because it states that record does not exist when it clearly must have existed to get the 'valid' status. If this persists then have to decide whether failure to delete a TXT record should be fatal or not. Is it safe to continue or not? It may depend on what happens next time around when trying to create a TXT record if one still exists (because attempt to delete it last time failed). |
|
Hi there. Tried the procedure a year ago, got a ban (account closed) and Josh after unblocking me it told me it was flaged for misuse.
Saw on top that sometimes it fails due because the export should be done without quotes? He did it with the quotes, following the wiki. |
Please report any issues with the FreeDNS api script by appending a comment to this issue.
Thank you,
David Kerr
The text was updated successfully, but these errors were encountered: