Hi. Welcome! 
https://secure.orangewebsite.com/index.php
can you use caddy with this domain host site, is it supported?
1 Like
There’s no such thing as “support of domain site”. Configure your DNS properly and Caddy can do its job accordingly.
2 Likes
Thanks I’m inexperienced, so now on caddy once I have entered my ipv4 and ipv6, and open the doors, do I have to enter the dns of my domain on caddy?
{ email myemail@gmail.com } test.my.com { reverse_proxy localhost:5050 }
this is my config and i am getting tls errors
1 Like
Please fill out the help template which you have seen when creating new topic, and include the error message with full logs.
1 Like
actually i understood what is my problem, i don’t have a “supported” dns.providers.domain i managed to setup caddy with google ad plugin (dns.providers.google_domains) with ease, but now i need to use this host, I saw that there is a “dns.providers.lego_deprecated” plugin for unsupported dns but this publici doesn’t support orangewebsite either. in the orange website settings i set the dns in my public address but i miss the cname records, i.e. moreover i didn’t find any “token” settings, i’m in the open sea i don’t know how to configure a domain “not supported by plugins” with caddy 2…
What are you trying to do with the plugin you’re searching for? Do you actually need wildcard certificate? Why are you concerning yourself with the CNAME record? Without full details, we can’t really help.
1 Like
this is my current configuration:
{
http_port 12345
https_port 45678
email email@gmail.com
}
https://media.my.com {
reverse_proxy 10.0.0.70:34567
}
it doesn’t work, however my configuration with another host, google domains by adding this string works perfectly
{
http_port 12345
https_port 45678
email email@gmail.com
acme_dns google_domains mytoken==
}
https://media.my.com {
reverse_proxy 10.0.0.70:34567
}
these are the errors i get with my current config (no acme) how can i configure change my current config to make it work? thank you in advance for your patience
http.acme_client challenge failed {"identifier": "media.my.com", "challenge_type": "tls-alpn-01", "problem": {"type": "urn:ietf:params:acme:error:connection", "title": "", "detail": "123.12.123.123: Timeout during connect (likely firewall problem)", "instance": "", "subproblems": []}}
2023/04/16 22:27:33.891 ERROR http.acme_client validating authorization {"identifier": "media.my.com", "problem": {"type": "urn:ietf:params:acme:error:connection", "title": "", "detail": "123.12.123.123: Timeout during connect (likely firewall problem)", "instance": "", "subproblems": []}, "order": "https://acme-v02.api.letsencrypt.org/acme/order/123456789/123456789", ({
"type": "urn:ietf:params:acme:error:malformed",
"detail": "Invalid order ID",
"status": 400
})"attempt": 2, "max_attempts": 3}
2023/04/16 22:27:33.892 ERROR tls.obtain could not get certificate from issuer {"identifier": "media.my.com", "issuer": "acme-v02.api.letsencrypt.org-directory", "error": "HTTP 400 urn:ietf:params:acme:error:connection - 123.12.123.123: Timeout during connect (likely firewall problem)"}
2023/04/16 22:27:33.894 INFO http waiting on internal rate limiter {"identifiers": ["media.my.com"], "ca": "https://acme.zerossl.com/v2/DV90", "account": "email@gmail.com"}
2023/04/16 22:27:33.894 INFO http done waiting on internal rate limiter {"identifiers": ["media.my.com"], "ca": "https://acme.zerossl.com/v2/DV90", "account": "email@gmail.com"}
2023/04/16 22:27:34.764 INFO http.acme_client trying to solve challenge {"identifier": "media.my.com", "challenge_type": "http-01", "ca": "https://acme.zerossl.com/v2/DV90"}
2023/04/16 22:27:50.562 ERROR http.acme_client challenge failed {"identifier": "media.my.com", "challenge_type": "http-01", "problem": {"type": "", "title": "", "detail": "", "instance": "", "subproblems": []}}
2023/04/16 22:27:50.563 ERROR http.acme_client validating authorization {"identifier": "media.my.com", "problem": {"type": "", "title": "", "detail": "", "instance": "", "subproblems": []}, "order": "https://acme.zerossl.com/v2/DV90/order/123456789", "attempt": 1, "max_attempts": 3}({"type":"urn:ietf:params:acme:error:malformed","status":405,"detail":"The request message was malformed"})
2023/04/16 22:27:50.563 ERROR tls.obtain could not get certificate from issuer {"identifier": "media.my.com", "issuer": "acme.zerossl.com-v2-DV90", "error": "HTTP 0 - "}
2023/04/16 22:27:50.563 ERROR tls.obtain will retry {"error": "[media.my.com] Obtain: [media.my.com solving challenge: media.my.com: [media.my.com] authorization failed: HTTP 0 - (ca=https://acme.zerossl.com/v2/DV90)", "attempt": 1, "retrying_in": 60, "elapsed": 41.739094786, "max_duration": 2592000}
2023/04/16 22:28:50.565 INFO tls.obtain obtaining certificate {"identifier": "media.my.com"}
2023/04/16 22:28:51.852 INFO http.acme_client trying to solve challenge {"identifier": "media.my.com", "challenge_type": "tls-alpn-01", "ca": "https://acme-staging-v02.api.letsencrypt.org/directory"}
2023/04/16 22:29:03.415 ERROR http.acme_client challenge failed {"identifier": "media.my.com", "challenge_type": "tls-alpn-01", "problem": {"type": "urn:ietf:params:acme:error:connection", "title": "", "detail": "134.19.179.211: Timeout during connect (likely firewall problem)", "instance": "", "subproblems": []}}
2023/04/16 22:29:03.415 ERROR http.acme_client validating authorization {"identifier": "media.my.com", "problem": {"type": "urn:ietf:params:acme:error:connection", "title": "", "detail": "123.12.123.123: Timeout during connect (likely firewall problem)", "instance": "", "subproblems": []}, "order": "https://acme-staging-v02.api.letsencrypt.org/acme/order/123456789", "attempt": 1, "max_attempts": 3} {
"status": "invalid",
"expires": "2023-04-23T22:28:51Z",
"identifiers": [
{
"type": "dns",
"value": "media.my.com"
}
],
"authorizations": [
"https://acme-staging-v02.api.letsencrypt.org/acme/authz-v3/123456789"
],
"finalize": "https://acme-staging-v02.api.letsencrypt.org/acme/finalize/123456789" ({
"identifier": {
"type": "dns",
"value": "media.my.com"
},
"status": "invalid",
"expires": "2023-04-23T22:28:51Z",
"challenges": [
{
"type": "tls-alpn-01",
"status": "invalid",
"error": {
"type": "urn:ietf:params:acme:error:connection",
"detail": "123.12.123.123: Timeout during connect (likely firewall problem)",
"status": 400
},
"url": "https://acme-staging-v02.api.letsencrypt.org/acme/chall-v3/123456789",
"token": "123456789",
"validationRecord": [
{
"hostname": "media.my.com",
"port": "443",
"addressesResolved": [
"123.12.123.123"
],
"addressUsed": "123.12.123.123"
}
],
"validated": "2023-04-16T22:28:51Z"
}
]
}
}
Thanks a lot, if it helps I also found this which explains what I would like to do:
and this too
basically there is no plugin from what I understand, by domain support I meant this.
For example with cloudflared it’s very simple with example plugin: Caddy server acme challenge with Cloudflare DNS – ookangzheng
but without plugins I don’t know how to do it
What do you mean by “doesn’t work”? Please be specific.
If you have a single domain name, you most likely don’t need wildcard certificates, which means yeu don’t need to look at all the “DNS providers”.
Your logs seem to indicate you have a firewall problem. Ensure ports 80 and 443 are unblocked.
1 Like
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.