{"id":451,"date":"2025-09-26T22:37:35","date_gmt":"2025-09-27T02:37:35","guid":{"rendered":"https:\/\/www.grumpyland.com\/blog\/?p=451"},"modified":"2025-09-27T02:33:41","modified_gmt":"2025-09-27T06:33:41","slug":"directadmin-automatic-ssl-certificates-with-3rd-party-dns-and-reverse-proxy-example-with-cloudflare","status":"publish","type":"post","link":"https:\/\/www.grumpyland.com\/blog\/451\/directadmin-automatic-ssl-certificates-with-3rd-party-dns-and-reverse-proxy-example-with-cloudflare\/","title":{"rendered":"DirectAdmin Automatic SSL Certificates with 3rd Party DNS and reverse proxy (example with CloudFlare)"},"content":{"rendered":"\n

This is a fairly simple solution done entirely in GUI, but something I had great difficulty finding the answer to from anywhere else.<\/p>\n\n\n\n

If you use another DNS and\/or reverse proxy service such as CloudFlare, the DirectAdmin’s auto SSL feature doesn’t work anymore since both ZeroSSL and Let’s Encrypt provided in DirectAdmin is no longer capable of verifying your domain as DNS verification fails.<\/p>\n\n\n\n

So your other services such as mail server, etc. will now fail to validate SSL while CloudFlare serves your website since CloudFlare doesn’t support your other services.<\/p>\n\n\n\n

To solve this, DirectAdmin already has a feature to update DNS elsewhere during SSL verification for certain services that provide API access. This tutorial will use CloudFlare as an example as that’s most likely the most common usage as well as mine. If you use another service that’s supported in DirectAdmin, steps might look a bit different, but the process will be similar.<\/p>\n\n\n\n

Part 1: Setup API keys and tokens on CloudFlare<\/h2>\n\n\n\n
\"CloudFlare<\/figure>\n\n\n\n

Direct Admin requires 4 fields. Though, seems like over-reach of token requirements, but the ones you need are: Account email, API key, API token with DNS, and API token with Zone.<\/p>\n\n\n\n

    \n
  1. Log in to CloudFlare<\/li>\n\n\n\n
  2. Go to Profile <\/em>(click the user icon on top right corner)<\/li>\n\n\n\n
  3. Go to API Tokens<\/em> (Left)<\/li>\n\n\n\n
  4. Retrieve the Global API Key<\/em> and keep this for later. This step will require further verification.<\/li>\n\n\n\n
  5. We’re now going to create a token that does both DNS and Zone.<\/li>\n\n\n\n
  6. Click Create Token<\/em><\/li>\n\n\n\n
  7. Create Custom Token<\/em><\/li>\n\n\n\n
  8. Create Permissions like this:<\/li>\n<\/ol>\n\n\n\n
    \"Configuration<\/figure>\n\n\n\n
    Zone Settings: Read\nZone: Edit\nDNS: Edit<\/code><\/pre>\n\n\n\n
    <\/p>\n\n\n\n
      \n
    1. For zones, you can do All Zones or specify which domains this applies to.<\/li>\n\n\n\n
    2. For Client IP Address Filtering, add your server’s public IP address(es).<\/li>\n\n\n\n
    3. Create the token and you’ll get a long token string.<\/li>\n<\/ol>\n\n\n\n
      Part 2: Configuration in Direct Admin<\/h2>\n\n\n\n
      \"Direct<\/figure>\n\n\n\n
      We will now setup auto SSL so that it updates CloudFlare accordingly to verify the DNS. We will be using the Evolution skin for this.<\/p>\n\n\n\n
        \n
      1. Login as the user which has the relevant domain<\/li>\n\n\n\n
      2. Go to SSL Certificates<\/em><\/li>\n\n\n\n
      3. Select the domain on top right if you have more than one.<\/li>\n\n\n\n
      4. Go to Get automatic certificate from ACME Provider<\/em> tab<\/li>\n\n\n\n
      5. Now you MUST <\/strong>select the wildcard checkmark. If you do not, the next options will not be visible.<\/li>\n\n\n\n
      6. When checked a new row will appear with the option of DNS provider<\/em>.<\/li>\n\n\n\n
      7. Select CloudFlare (or any other third party DNS you’re using) and then a modal window will popup. This only appears now and will not be visible again, even if you come back to this screen later. For CloudFlare, it will look like so:<\/li>\n<\/ol>\n\n\n\n
        \"direct<\/figure>\n\n\n\n
          \n
        1. Fill in the details with the information you got from Part 1. The token goes into both the DNS and Zone section.<\/li>\n\n\n\n
        2. Hit Save on the popup window.<\/li>\n\n\n\n
        3. Hit Save again for the auto SSL.<\/li>\n<\/ol>\n\n\n\n
          That’s it! Now you have automatic SSL with Let’s Encrypt\/ZeroSSL for your domain and all your subdomains, allowing all services to connect securely while also using CloudFlare for serving the web.<\/p>\n\n\n\n
          Bonus Tidbit<\/h2>\n\n\n\n
          \"daflare<\/figure>\n\n\n\n
          If you’d like to automatically synchronize your DirectAdmin DNS and CloudFlare DNS, you can use a plugin called daflare<\/a>.<\/p>\n\n\n\n
          This will copy all of your DNS data from your DA to your CF. If you’ve followed this setup, you’ve already got almost all the credentials you need for daflare. Just need to grab the account ID from CF from Account home page.<\/p>\n\n\n\n
          \"cloudflare's<\/figure>\n\n\n\n
          Just be warned that this plugin saves DNS information in ONE direction. From DA to CF. So all information in CF that’s not in DA will be deleted.<\/p>\n","protected":false},"excerpt":{"rendered":"
          This is a fairly simple solution done entirely in GUI, but something I had great difficulty finding the answer to from anywhere else. If you use another DNS and\/or reverse proxy service such as CloudFlare, the DirectAdmin’s auto SSL feature doesn’t work anymore since both ZeroSSL and Let’s Encrypt provided in DirectAdmin is no longer […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"_vp_format_video_url":"","_vp_image_focal_point":[],"footnotes":""},"categories":[15],"tags":[68,67,69],"class_list":["post-451","post","type-post","status-publish","format-standard","hentry","category-tutorial","tag-cloudflare","tag-directadmin","tag-dns"],"_links":{"self":[{"href":"https:\/\/www.grumpyland.com\/blog\/wp-json\/wp\/v2\/posts\/451","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.grumpyland.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.grumpyland.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.grumpyland.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.grumpyland.com\/blog\/wp-json\/wp\/v2\/comments?post=451"}],"version-history":[{"count":9,"href":"https:\/\/www.grumpyland.com\/blog\/wp-json\/wp\/v2\/posts\/451\/revisions"}],"predecessor-version":[{"id":479,"href":"https:\/\/www.grumpyland.com\/blog\/wp-json\/wp\/v2\/posts\/451\/revisions\/479"}],"wp:attachment":[{"href":"https:\/\/www.grumpyland.com\/blog\/wp-json\/wp\/v2\/media?parent=451"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.grumpyland.com\/blog\/wp-json\/wp\/v2\/categories?post=451"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.grumpyland.com\/blog\/wp-json\/wp\/v2\/tags?post=451"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}