Skip to content

Commit 6dbebab

Browse files
authored
Create cloudflare.md
1 parent e83292e commit 6dbebab

File tree

1 file changed

+21
-0
lines changed

1 file changed

+21
-0
lines changed

docs/cloudflare.md

+21
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
# Cloudflare integration
2+
3+
If using Cloudflare services, an API Token to allow your server to validate your domain with DNS-01 might be needed.
4+
5+
> We recommend using Cloudflare for a couple of reasons...
6+
7+
## API Token - ACME - DNS-01
8+
9+
In Cloudflare go to your profile and find API Token option:
10+
![image](https://github.com/user-attachments/assets/bbc3d316-7f71-4022-abf5-dfe0e704dadf)
11+
12+
You can manually create one or use the _'Edit zone DNS'_ template. Remember to add your domains which you would like to allow this token to have access to it and the source IP address:
13+
![image](https://github.com/user-attachments/assets/42bc2833-6ddb-44ac-9e6b-cea72d0f0ee5)
14+
15+
Save your token and place it in .env at CLOUDFLARE_DNS_TOKEN.
16+
17+
## Disclaimer
18+
19+
As of [acme-compnation](https://github.com/nginx-proxy/acme-companion) if we can not comply to use HTTP-01, using DNS-01 could be used, as also per [acme.sh](https://github.com/acmesh-official/acme.sh/wiki/dnsapi) as well.
20+
So, following [acme-compnation instruction ](https://github.com/nginx-proxy/acme-companion/blob/main/docs/Let's-Encrypt-and-ACME.md#dns-01-acme-challenge) a global API Key could be used, but we do not like this idea much due to security resons, reason why we suggest creating a more restrict API Token as indicated above.
21+

0 commit comments

Comments
 (0)