Skip to content
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

wildcard not working #619

Open
mihsergeev opened this issue May 19, 2024 · 2 comments
Open

wildcard not working #619

mihsergeev opened this issue May 19, 2024 · 2 comments

Comments

@mihsergeev
Copy link

labels:
caddy: *.domain.con
caddy.reverse_proxy: "{{upstreams http 80}}"

how to do it correctly so that it accepts requests from all domains, no need to make ssl-certs

@francislavoie
Copy link
Collaborator

You always needs a TLS cert to serve HTTPS. A wildcard only means you're asking Caddy to issue a special certificate with a wildcard in it, which requires building Caddy with a DNS plugin to connect with your DNS provider, because the ACME DNS challenge requires proving that you are in control of your domain's DNS records. https://caddyserver.com/docs/automatic-https#dns-challenge

@mihsergeev
Copy link
Author

labels:
  caddy: *.domain.com domain.com
  caddy.reverse_proxy: "{{upstreams 80}}"
  caddy.tls.dns: "cloudflare $API-TOKEN" 

doesn't work, how to write correctly?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants