I have published a release for libdns/godaddy but when trying to register the package under my Caddy account I get this error
Sorry, something went wrong:
unable to scan modules in package github.com/caddy-dns/godaddy
Please include this error ID if reporting:
199f8114-9506-4053-b056-d04e74f2c0f8
The module I am trying to register is github.com/caddy-dns/godaddy.
What am I doing wrong?
@matt will need to look into that when he finds the time, to take a look at what that error ID reported. But he’s busy for the next few days so it make take some time.
Thank you for the explanation! I think I got spoiled with getting my issues addressed almost immediately by the Caddy team… kuddos!!! I will wait patiently 
First though, you can make sure the plugin actually builds.
Try building with xcaddy:
can’t seem to figure out how to run xcaddy. I pulled down the repo and downloaded the binaries. Running xcaddy yields zsh: command not found: xcaddy.
Note, I did install Go 1.176 globally.
Did you move it to /usr/bin/xcaddy? Did you give it executable permissions with chmod +x?
So, I ended up moving the file to /usr/local/bin and then it worked. I was able to successfully build the plugin with this cmd 
xcaddy build --with github.com/caddy-dns/godaddy@v1.0.1
@francislavoie So I was able to register the github.com/caddy-dns/godaddy module! It also appeared in the plugin list. After creating a custom build I tried using it.
I added this to the *.honeystalk.io block
tls {
dns godaddy <api_key>:<api_secret>
}
I am seeing these errors now in the console
2022/01/28 20:40:10.320 WARN tls.issuance.acme.acme_client HTTP request failed; retrying {"url": "https://acme.zerossl.com/v2/DV90", "error": "performing request: Get \"https://acme.zerossl.com/v2/DV90\": dial tcp 91.199.212.80:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond."}
2022/01/28 20:40:31.605 WARN tls.issuance.acme.acme_client HTTP request failed; retrying {"url": "https://acme.zerossl.com/v2/DV90", "error": "performing request: Get \"https://acme.zerossl.com/v2/DV90\": dial tcp 91.199.212.80:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond."}
2022/01/28 20:40:31.609 ERROR tls.obtain could not get certificate from issuer {"identifier": "honeystalk.io", "issuer": "acme.zerossl.com-v2-DV90", "error": "[honeystalk.io] creating new order: provisioning client: performing request: Get \"https://acme.zerossl.com/v2/DV90\": dial tcp 91.199.212.80:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (ca=https://acme.zerossl.com/v2/DV90)"}
2022/01/28 20:40:31.615 ERROR tls.obtain will retry {"error": "[honeystalk.io] Obtain: [honeystalk.io] creating new order: provisioning client: performing request: Get \"https://acme.zerossl.com/v2/DV90\": dial tcp 91.199.212.80:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (ca=https://acme.zerossl.com/v2/DV90)", "attempt": 1, "retrying_in": 60, "elapsed": 70.1781477, "max_duration": 2592000}
2022/01/28 20:40:52.634 WARN tls.issuance.acme.acme_client HTTP request failed; retrying {"url": "https://acme.zerossl.com/v2/DV90", "error": "performing request: Get \"https://acme.zerossl.com/v2/DV90\": dial tcp 91.199.212.80:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond."}
2022/01/28 20:41:13.954 WARN tls.issuance.acme.acme_client HTTP request failed; retrying {"url": "https://acme.zerossl.com/v2/DV90", "error": "performing request: Get \"https://acme.zerossl.com/v2/DV90\": dial tcp 91.199.212.80:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond."}
2022/01/28 20:41:35.251 WARN tls.issuance.acme.acme_client HTTP request failed; retrying {"url": "https://acme.zerossl.com/v2/DV90", "error": "performing request: Get \"https://acme.zerossl.com/v2/DV90\": dial tcp 91.199.212.80:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond."}
2022/01/28 20:41:35.255 ERROR tls.obtain could not get certificate from issuer {"identifier": "www.honeystalk.io", "issuer": "acme.zerossl.com-v2-DV90", "error": "[www.honeystalk.io] creating new order: provisioning client: performing request: Get \"https://acme.zerossl.com/v2/DV90\": dial tcp 91.199.212.80:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (ca=https://acme.zerossl.com/v2/DV90)"}
2022/01/28 20:41:35.261 ERROR tls.obtain will retry {"error": "[www.honeystalk.io] Obtain: [www.honeystalk.io] creating new order: provisioning client: performing request: Get \"https://acme.zerossl.com/v2/DV90\": dial tcp 91.199.212.80:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (ca=https://acme.zerossl.com/v2/DV90)", "attempt": 1, "retrying_in": 60, "elapsed": 133.817242, "max_duration": 2592000}
2022/01/28 20:41:35.826 INFO tls.issuance.acme.acme_client trying to solve challenge {"identifier": "honeystalk.io", "challenge_type": "tls-alpn-01", "ca": "https://acme-staging-v02.api.letsencrypt.org/directory"}
2022/01/28 20:41:36.257 ERROR tls.issuance.acme.acme_client challenge failed {"identifier": "honeystalk.io", "challenge_type": "tls-alpn-01", "problem": {"type": "urn:ietf:params:acme:error:tls", "title": "", "detail": "remote error: tls: internal error", "instance": "", "subproblems": []}}
2022/01/28 20:41:36.262 ERROR tls.issuance.acme.acme_client validating authorization {"identifier": "honeystalk.io", "problem": {"type": "urn:ietf:params:acme:error:tls", "title": "", "detail": "remote error: tls: internal error", "instance": "", "subproblems": []}, "order": "https://acme-staging-v02.api.letsencrypt.org/acme/order/41202868/1654264298", "attempt": 1, "max_attempts": 3}
2022/01/28 20:41:37.452 INFO tls.issuance.acme.acme_client trying to solve challenge {"identifier": "honeystalk.io", "challenge_type": "http-01", "ca": "https://acme-staging-v02.api.letsencrypt.org/directory"}
2022/01/28 20:41:38.876 ERROR tls.issuance.acme.acme_client challenge failed {"identifier": "honeystalk.io", "challenge_type": "http-01", "problem": {"type": "urn:ietf:params:acme:error:unauthorized", "title": "", "detail": "Invalid response from https://honeystalk.io/ [38.95.5.78]: \"<!doctype html>\\n<html lang=\\\"en\\\">\\n<head>\\n<title>Cogency.io</title>\\n<meta charset=\\\"utf-8\\\">\\n<meta http-equiv=\\\"X-UA-Compatible\\\" cont\"", "instance": "", "subproblems": []}}
2022/01/28 20:41:38.880 ERROR tls.issuance.acme.acme_client validating authorization {"identifier": "honeystalk.io", "problem": {"type": "urn:ietf:params:acme:error:unauthorized", "title": "", "detail": "Invalid response from https://honeystalk.io/ [38.95.5.78]: \"<!doctype html>\\n<html lang=\\\"en\\\">\\n<head>\\n<title>Cogency.io</title>\\n<meta charset=\\\"utf-8\\\">\\n<meta http-equiv=\\\"X-UA-Compatible\\\" cont\"", "instance": "", "subproblems": []}, "order": "https://acme-staging-v02.api.letsencrypt.org/acme/order/41202868/1654264508", "attempt": 2, "max_attempts": 3}
2022/01/28 20:41:40.150 ERROR tls.obtain could not get certificate from issuer {"identifier": "honeystalk.io", "issuer": "acme-v02.api.letsencrypt.org-directory", "error": "[honeystalk.io] solving challenges: honeystalk.io: no solvers available for remaining challenges (configured=[http-01 tls-alpn-01] offered=[http-01 dns-01 tls-alpn-01] remaining=[dns-01]) (order=https://acme-staging-v02.api.letsencrypt.org/acme/order/41202868/1654264768) (ca=https://acme-staging-v02.api.letsencrypt.org/directory)"}
2022/01/28 20:42:01.173 WARN tls.issuance.acme.acme_client HTTP request failed; retrying {"url": "https://acme.zerossl.com/v2/DV90", "error": "performing request: Get \"https://acme.zerossl.com/v2/DV90\": dial tcp 91.199.212.80:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond."}
Seems like ACME HTTP challenge requests aren’t reaching Caddy, but are being intercepted by some other server.
I was under the impression that the acme challenge would be done through TXT records, since I specified dns godaddy...?
I could have sworn I read somewhere that for wildcard certs dns acme was needed?!
Yes, but those are logs for honeystalk.io, not *.honeystalk.io.
Ok, so I have these two blocks. Do I need to change anything? … like remove on_demand and place the dns godaddy in there instead?
Please let me know what corrections I need to make 
https:// {
encode gzip
# log {
# output file logs/honeystalk_https_access.log
# format json
# }
tls {
on_demand
}
import ../security-headers.conf
import ../lucee.conf
handle_path /shared/* {
header Access-Control-Allow-Headers "Content-Type"
header Access-Control-Allow-Origin *
root * d:/web/honeystalk.io/shared
file_server
}
root * d:/web/honeystalk.io/account
import redirected
}
*.honeystalk.io {
encode gzip
# log {
# output file logs/honeystalk_account_access.log
# format json
# }
import ../security-headers.conf
import ../lucee.conf
handle_path /shared/* {
header Access-Control-Allow-Headers "Content-Type"
header Access-Control-Allow-Origin *
root * d:/web/honeystalk.io/shared
file_server
}
root * d:/web/honeystalk.io/account
import redirected
tls {
dns godaddy <token>
}
}
No that looks correct.
It would help to see the logs from the start, i.e. when it first starts TLS maintenance. Just looking at the end only gives a narrow view of what happened.
Here you go.
admin@SUPER2 C:\Apps\caddy
# caddy_windows_amd64_custom run
2022/01/28 22:01:20.730 INFO using adjacent Caddyfile
2022/01/28 22:01:20.752 WARN input is not formatted with 'caddy fmt' {"adapter": "caddyfile", "file": "Caddyfile", "line": 2}
2022/01/28 22:01:20.771 INFO admin admin endpoint started {"address": "tcp/localhost:2019", "enforce_origin": false, "origins": ["localhost:2019", "[::1]:2019", "127.0.0.1:2019"]}
2022/01/28 22:01:20.772 INFO tls.cache.maintenance started background certificate maintenance {"cache": "0xc00033c4d0"}
2022/01/28 22:01:20.773 INFO http enabling automatic HTTP->HTTPS redirects {"server_name": "srv0"}
2022/01/28 22:01:20.788 INFO tls cleaning storage unit {"description": "FileStorage:C:\\Users\\Administrator\\AppData\\Roaming\\Caddy"}
2022/01/28 22:01:20.789 INFO http enabling automatic TLS certificate management {"domains": ["www.honeystalk.io", "honeystalk.io", "*.honeystalk.io", "ws-dev.honeystalk.io"]}
2022/01/28 22:01:20.806 INFO tls finished cleaning storage units
2022/01/28 22:01:20.809 INFO autosaved config (load with --resume flag) {"file": "C:\\Users\\Administrator\\AppData\\Roaming\\Caddy\\autosave.json"}
2022/01/28 22:01:20.817 INFO serving initial configuration
2022/01/28 22:01:20.816 INFO tls.obtain acquiring lock {"identifier": "honeystalk.io"}
2022/01/28 22:01:20.813 INFO tls.obtain acquiring lock {"identifier": "www.honeystalk.io"}
2022/01/28 22:01:20.866 INFO tls.obtain lock acquired {"identifier": "honeystalk.io"}
2022/01/28 22:01:20.871 INFO tls.obtain lock acquired {"identifier": "www.honeystalk.io"}
2022/01/28 22:01:20.874 INFO tls.issuance.acme waiting on internal rate limiter {"identifiers": ["honeystalk.io"], "ca": "https://acme-v02.api.letsencrypt.org/directory", "account": "asieler@honeystalk.io"}
2022/01/28 22:01:20.879 INFO tls.issuance.acme done waiting on internal rate limiter {"identifiers": ["honeystalk.io"], "ca": "https://acme-v02.api.letsencrypt.org/directory", "account": "asieler@honeystalk.io"}
2022/01/28 22:01:20.878 INFO tls.issuance.acme waiting on internal rate limiter {"identifiers": ["www.honeystalk.io"], "ca": "https://acme-v02.api.letsencrypt.org/directory", "account": "asieler@honeystalk.io"}
2022/01/28 22:01:20.888 INFO tls.issuance.acme done waiting on internal rate limiter {"identifiers": ["www.honeystalk.io"], "ca": "https://acme-v02.api.letsencrypt.org/directory", "account": "asieler@honeystalk.io"}
2022/01/28 22:01:21.604 INFO tls.issuance.acme.acme_client trying to solve challenge {"identifier": "honeystalk.io", "challenge_type": "http-01", "ca": "https://acme-v02.api.letsencrypt.org/directory"}
2022/01/28 22:01:21.743 INFO tls.issuance.acme.acme_client trying to solve challenge {"identifier": "www.honeystalk.io", "challenge_type": "http-01", "ca": "https://acme-v02.api.letsencrypt.org/directory"}
2022/01/28 22:01:23.396 ERROR tls.issuance.acme.acme_client challenge failed {"identifier": "honeystalk.io", "challenge_type": "http-01", "problem": {"type": "urn:ietf:params:acme:error:unauthorized", "title": "", "detail": "Invalid response from https://honeystalk.io/ [38.95.5.78]: \"<!doctype html>\\n<html lang=\\\"en\\\">\\n<head>\\n<title>Cogency.io</title>\\n<meta charset=\\\"utf-8\\\">\\n<meta http-equiv=\\\"X-UA-Compatible\\\" cont\"", "instance": "", "subproblems": []}}
2022/01/28 22:01:23.397 ERROR tls.issuance.acme.acme_client validating authorization {"identifier": "honeystalk.io", "problem": {"type": "urn:ietf:params:acme:error:unauthorized", "title": "", "detail": "Invalid response from https://honeystalk.io/ [38.95.5.78]: \"<!doctype html>\\n<html lang=\\\"en\\\">\\n<head>\\n<title>Cogency.io</title>\\n<meta charset=\\\"utf-8\\\">\\n<meta http-equiv=\\\"X-UA-Compatible\\\" cont\"", "instance": "", "subproblems": []}, "order": "https://acme-v02.api.letsencrypt.org/acme/order/372953220/59293982370", "attempt": 1, "max_attempts": 3}
2022/01/28 22:01:23.592 ERROR tls.issuance.acme.acme_client challenge failed {"identifier": "www.honeystalk.io", "challenge_type": "http-01", "problem": {"type": "urn:ietf:params:acme:error:unauthorized", "title": "", "detail": "Invalid response from https://honeystalk.io/ [38.95.5.78]: \"<!doctype html>\\n<html lang=\\\"en\\\">\\n<head>\\n<title>Cogency.io</title>\\n<meta charset=\\\"utf-8\\\">\\n<meta http-equiv=\\\"X-UA-Compatible\\\" cont\"", "instance": "", "subproblems": []}}
2022/01/28 22:01:23.595 ERROR tls.issuance.acme.acme_client validating authorization {"identifier": "www.honeystalk.io", "problem": {"type": "urn:ietf:params:acme:error:unauthorized", "title": "", "detail": "Invalid response from https://honeystalk.io/ [38.95.5.78]: \"<!doctype html>\\n<html lang=\\\"en\\\">\\n<head>\\n<title>Cogency.io</title>\\n<meta charset=\\\"utf-8\\\">\\n<meta http-equiv=\\\"X-UA-Compatible\\\" cont\"", "instance": "", "subproblems": []}, "order": "https://acme-v02.api.letsencrypt.org/acme/order/372953220/59293982880", "attempt": 1, "max_attempts": 3}
2022/01/28 22:01:24.734 INFO tls.issuance.acme.acme_client trying to solve challenge {"identifier": "honeystalk.io", "challenge_type": "tls-alpn-01", "ca": "https://acme-v02.api.letsencrypt.org/directory"}
2022/01/28 22:01:25.022 INFO tls.issuance.acme.acme_client trying to solve challenge {"identifier": "www.honeystalk.io", "challenge_type": "tls-alpn-01", "ca": "https://acme-v02.api.letsencrypt.org/directory"}
2022/01/28 22:01:25.195 ERROR tls.issuance.acme.acme_client challenge failed {"identifier": "honeystalk.io", "challenge_type": "tls-alpn-01", "problem": {"type": "urn:ietf:params:acme:error:tls", "title": "", "detail": "remote error: tls: internal error", "instance": "", "subproblems": []}}
2022/01/28 22:01:25.198 ERROR tls.issuance.acme.acme_client validating authorization {"identifier": "honeystalk.io", "problem": {"type": "urn:ietf:params:acme:error:tls", "title": "", "detail": "remote error: tls: internal error", "instance": "", "subproblems": []}, "order": "https://acme-v02.api.letsencrypt.org/acme/order/372953220/59293992040", "attempt": 2, "max_attempts": 3}
2022/01/28 22:01:25.470 ERROR tls.issuance.acme.acme_client challenge failed {"identifier": "www.honeystalk.io", "challenge_type": "tls-alpn-01", "problem": {"type": "urn:ietf:params:acme:error:tls", "title": "", "detail": "remote error: tls: internal error", "instance": "", "subproblems": []}}
2022/01/28 22:01:25.472 ERROR tls.issuance.acme.acme_client validating authorization {"identifier": "www.honeystalk.io", "problem": {"type": "urn:ietf:params:acme:error:tls", "title": "", "detail": "remote error: tls: internal error", "instance": "", "subproblems": []}, "order": "https://acme-v02.api.letsencrypt.org/acme/order/372953220/59293992650", "attempt": 2, "max_attempts": 3}
2022/01/28 22:01:26.659 ERROR tls.obtain could not get certificate from issuer {"identifier": "honeystalk.io", "issuer": "acme-v02.api.letsencrypt.org-directory", "error": "[honeystalk.io] solving challenges: honeystalk.io: no solvers available for remaining challenges (configured=[http-01 tls-alpn-01] offered=[http-01 dns-01 tls-alpn-01] remaining=[dns-01]) (order=https://acme-v02.api.letsencrypt.org/acme/order/372953220/59293997330) (ca=https://acme-v02.api.letsencrypt.org/directory)"}
2022/01/28 22:01:26.666 INFO tls.issuance.acme waiting on internal rate limiter {"identifiers": ["honeystalk.io"], "ca": "https://acme.zerossl.com/v2/DV90", "account": "asieler@honeystalk.io"}
2022/01/28 22:01:26.668 INFO tls.issuance.acme done waiting on internal rate limiter {"identifiers": ["honeystalk.io"], "ca": "https://acme.zerossl.com/v2/DV90", "account": "asieler@honeystalk.io"}
2022/01/28 22:01:26.955 ERROR tls.obtain could not get certificate from issuer {"identifier": "www.honeystalk.io", "issuer": "acme-v02.api.letsencrypt.org-directory", "error": "[www.honeystalk.io] solving challenges: www.honeystalk.io: no solvers available for remaining challenges (configured=[http-01 tls-alpn-01] offered=[http-01 dns-01 tls-alpn-01] remaining=[dns-01]) (order=https://acme-v02.api.letsencrypt.org/acme/order/372953220/59293998190) (ca=https://acme-v02.api.letsencrypt.org/directory)"}
2022/01/28 22:01:26.958 INFO tls.issuance.acme waiting on internal rate limiter {"identifiers": ["www.honeystalk.io"], "ca": "https://acme.zerossl.com/v2/DV90", "account": "asieler@honeystalk.io"}
2022/01/28 22:01:26.959 INFO tls.issuance.acme done waiting on internal rate limiter {"identifiers": ["www.honeystalk.io"], "ca": "https://acme.zerossl.com/v2/DV90", "account": "asieler@honeystalk.io"}
2022/01/28 22:01:47.746 WARN tls.issuance.acme.acme_client HTTP request failed; retrying {"url": "https://acme.zerossl.com/v2/DV90", "error": "performing request: Get \"https://acme.zerossl.com/v2/DV90\": dial tcp 91.199.212.80:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond."}
2022/01/28 22:02:09.031 WARN tls.issuance.acme.acme_client HTTP request failed; retrying {"url": "https://acme.zerossl.com/v2/DV90", "error": "performing request: Get \"https://acme.zerossl.com/v2/DV90\": dial tcp 91.199.212.80:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond."}
2022/01/28 22:02:12.145 INFO shutting down {"signal": "SIGINT"}
2022/01/28 22:02:12.146 WARN exiting; byeee!! � {"signal": "SIGINT"}
2022/01/28 22:02:12.182 INFO tls.cache.maintenance stopped background certificate maintenance {"cache": "0xc00033c4d0"}
2022/01/28 22:02:12.183 WARN tls.issuance.acme.acme_client HTTP request failed; retrying {"url": "https://acme.zerossl.com/v2/DV90", "error": "performing request: Get \"https://acme.zerossl.com/v2/DV90\": context canceled"}
2022/01/28 22:02:12.201 ERROR tls.obtain could not get certificate from issuer {"identifier": "honeystalk.io", "issuer": "acme.zerossl.com-v2-DV90", "error": "[honeystalk.io] creating new order: provisioning client: performing request: Get \"https://acme.zerossl.com/v2/DV90\": context canceled (ca=https://acme.zerossl.com/v2/DV90)"}
2022/01/28 22:02:12.205 WARN tls.issuance.acme.acme_client HTTP request failed; retrying {"url": "https://acme.zerossl.com/v2/DV90", "error": "performing request: Get \"https://acme.zerossl.com/v2/DV90\": context canceled"}
2022/01/28 22:02:12.205 INFO admin stopped previous server {"address": "tcp/localhost:2019"}
2022/01/28 22:02:12.208 INFO tls.obtain releasing lock {"identifier": "honeystalk.io"}
2022/01/28 22:02:12.211 ERROR tls.obtain could not get certificate from issuer {"identifier": "www.honeystalk.io", "issuer": "acme.zerossl.com-v2-DV90", "error": "[www.honeystalk.io] creating new order: provisioning client: context canceled (ca=https://acme.zerossl.com/v2/DV90)"}
Again, all those logs are problems with the explicitly configured, non-wildcard domains, which use the HTTP challenge. Like I said, make sure you don’t have some other server or load balancer responding instead of Caddy for the HTTP challenge requests.
If Caddy was working on issuance for your wildcard domain, you would see "identifier": "*.honeystalk.io" in the logs. But I think you probably already have a cert for that in storage considering there was no log messages for it after the initial startup.
Is there a better way to test the dns godaddy implementation? I was actually just trying to test that to make sure my plugin is working.
In regards to the wildcard cert, I was originally linking an existing cert that I had purchased so it most likely has it in cache.
Delete the cert from storage and reload Caddy.
I actually think it probably succeeded in a previous run but you just missed the log message.
how do you delete that?
If you run Caddy with the --environ flag it’ll show you Caddy’s storage location. Go there, browse around and find the dir for your wildcard cert and delete it.
Yes Sir, it did obtain the wildcard cert successfully!!
2022/01/28 23:13:37.911 INFO tls.issuance.acme.acme_client successfully downloaded available certificate chains {"count": 2, "first_url": "https://acme-v02.api.letsencrypt.org/acme/cert/044bfe233a9a78c1cd44116e34a550ec3310"}
2022/01/28 23:13:37.926 INFO tls.obtain certificate obtained successfully {"identifier": "*.honeystalk.io"}