-
Notifications
You must be signed in to change notification settings - Fork 31
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
Cannot get certificate with latest Rout53 plugin using docker #29
Comments
I just verified something even more interesting. But it seems to never work on .com adresses.. Same account, same api key same server. May be this is only amazon speciality. |
And counter verified the whole thing again... Tried with a .com subdomain with latest version for about 30 minutes without sucess. Same domain.. same config, but different caddyaws plugin |
This has currently broken my system. Any updates on this? Edit for anyone else: v1.2.1 works fine everything above is broken |
- Chunk strings longer than 255 - Quote TXT/SPF strings and escape special characters Fixes: #21 Fixes: #20 Fixes: caddy-dns/route53#29 Reference: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/ResourceRecordTypes.html#TXTFormat
Can you try this libdns/route53#45? |
I'd really like to but I'm really not sure how to do that.
…On Tue., Apr. 11, 2023, 5:31 p.m. Ayman Bagabas, ***@***.***> wrote:
Can you try this libdns/route53#45
<libdns/route53#45>?
—
Reply to this email directly, view it on GitHub
<#29 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATSSEBNUQOA5TODAS4M5TEDXAXEUNANCNFSM6AAAAAAUKKK62M>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Following this guide, you can build caddy with a custom module using I've pushed a new branch that uses the xcaddy build --with github.com/caddy-dns/route53@quote |
- Chunk strings longer than 255 - Quote TXT/SPF strings and escape special characters Fixes: #21 Fixes: #20 Fixes: caddy-dns/route53#29 Reference: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/ResourceRecordTypes.html#TXTFormat
- Chunk strings longer than 255 - Quote TXT/SPF strings and escape special characters Fixes: #21 Fixes: #20 Fixes: caddy-dns/route53#29 Reference: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/ResourceRecordTypes.html#TXTFormat
- Chunk strings longer than 255 - Quote TXT/SPF strings and escape special characters Fixes: #21 Fixes: #20 Fixes: caddy-dns/route53#29 Reference: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/ResourceRecordTypes.html#TXTFormat
- Chunk strings longer than 255 - Quote TXT/SPF strings and escape special characters Fixes: #21 Fixes: #20 Fixes: caddy-dns/route53#29 Reference: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/ResourceRecordTypes.html#TXTFormat
- Chunk strings longer than 255 - Quote TXT/SPF strings and escape special characters Fixes: #21 Fixes: #20 Fixes: caddy-dns/route53#29 Reference: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/ResourceRecordTypes.html#TXTFormat
I tested this manually and it appears to fix the issue not. Route53 treats TXT & SPF records in a weird way ref. If anyone could test the package one more time before I create a new release it would be appreciated. |
I can confirm that the |
- Chunk strings longer than 255 - Quote TXT/SPF strings and escape special characters Fixes: #21 Fixes: #20 Fixes: caddy-dns/route53#29 Reference: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/ResourceRecordTypes.html#TXTFormat
This is now fixed in https://github.com/caddy-dns/route53/releases/tag/v1.3.3 |
Hi, this problem started (iguess) on release 1.3
If I,m using a previous version of the plugin, it works. I get this error:
"type":"urn:ietf:params:acme:error:malformed","status":405,"detail":"The request message was malformed"
I get this error from the logs:
caddyaws2023 | {"level":"error","ts":1675007436.1783702,"logger":"tls.obtain","msg":"could not get certificate from issuer","identifier":"HOST.DOMAINEXEMPLE.com","issuer":"acme.zerossl.com-v2-DV90","error":"[HOST.DOMAINEXEMPLE.com] solving challenges: presenting for challenge: adding temporary record for zone \"DOMAINEXAMPLE.com.\": Error unquoting TXT/SPF record: invalid syntax (order=https://acme.zerossl.com/v2/DV90/order/dkpx3lDTGufoX8eT6p3Tvw) (ca=https://acme.zerossl.com/v2/DV90)"}
Then, I let the whole configuration intact and just replace the custom caddy file for the older version and I get a Zerossl certificate.
Still it seems it to fail getting the letsencrypt one but I still get a Zerossl cert at least.:
Example of caddyfile
May be am I missing a parameter for the new version?
Also, I got some servers working with Letsencrypt certs with this exact config.. This time, it pumped a Zero ssl, I have no clue why this happens.
Thanks for any help
The text was updated successfully, but these errors were encountered: