{"timestamp": "2026-07-10T22:20:44.160046", "data": {"url": "https://github.com/CaddyBuilds/caddy-namecheap", "title": "GitHub - CaddyBuilds/caddy-namecheap: A fully integrated Caddy Docker image featuring Namecheap DNS-01 ACME validation \u00b7 GitHub", "content": "Skip to content You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert Uh oh! There was an error while loading. Please reload this page . CaddyBuilds / caddy-namecheap Public Notifications You must be signed in to change notification settings Fork 5 Star 6 main Branches Tags Go to file Code Open more actions menu Folders and files Name Name Last commit message Last commit date Latest commit History 8 Commits 8 Commits .github/ workflows .github/ workflows scripts scripts Caddyfile_global Caddyfile_global Caddyfile_per_site Caddyfile_per_site Dockerfile Dockerfile Dockerfile.alpine Dockerfile.alpine LICENSE LICENSE README.md README.md View all files Repository files navigation Caddy Namecheap A fully integrated Caddy Docker image featuring Namecheap DNS-01 ACME validation Deploy a hassle-free Caddy server with built-in support for Namecheap DNS-01 ACME challenges. Streamline your SSL certificate management and ensure your server stays secure without manual updates, making it an effortless and reliable solution. Table of Contents Features Usage Using the Pre-built Docker Image Building Your Own Docker Image Sample Caddyfile Configuration ACME DNS Challenge Configuration Creating Namecheap API Credentials Platform Support Raspberry Pi Tags Contributing License Features Automated Builds : Automatically checks for new Caddy releases and builds Docker images. Continuous Integration : Utilizes GitHub Actions for seamless CI/CD. Namecheap DNS Integration : Integrates Namecheap DNS for automatic SSL certificate management. Multi-Platform Support : Builds images for multiple architectures, including amd64 , arm64 , arm/v7 (Raspberry Pi), ppc64le , and s390x , ensuring compatibility across a wide range of devices and systems. Alpine-based Image : Provides a lightweight Alpine-based image for smaller size and faster deployment. Manual Trigger : Allows manual triggering of the build process. Open Source : Contributions are welcome under the MIT License. Usage Using the Pre-built Docker Image To use the pre-built Docker image, pull it from the GitHub Container Registry: docker pull ghcr.io/caddybuilds/caddy-namecheap:latest docker pull caddybuilds/caddy-namecheap:latest # alpine docker pull ghcr.io/caddybuilds/caddy-namecheap:alpine docker pull caddybuilds/caddy-namecheap:alpine You can use the image in your Docker setup. Here is an example docker-compose.yml file: services : caddy : image : ghcr.io/caddybuilds/caddy-namecheap:latest restart : unless-stopped cap_add : - NET_ADMIN ports : - \" 80:80 \" - \" 443:443 \" - \" 443:443/udp \" volumes : - $PWD/Caddyfile:/etc/caddy/Caddyfile - $PWD/site:/srv - caddy_data:/data - caddy_config:/config environment : - NAMECHEAP_API_KEY=your_namecheap_api_key - NAMECHEAP_API_USER=your_namecheap_username - NAMECHEAP_CLIENT_IP=your_client_ip volumes : caddy_data : external : true caddy_config : Defining the data volume as external makes sure docker-compose down does not delete the volume. You may need to create it manually using docker volume create caddy_data . Replace your_namecheap_api_key , your_namecheap_username , and your_client_ip with your actual Namecheap API credentials. Sample Caddyfile Here is a sample Caddyfile configuration to get you started. This configuration sets up the ACME DNS challenge provider to use Namecheap and serves a simple static site. Global Configuration (Use DNS Challenge for All Sites) In this configuration, the ACME DNS challenge provider is set globally, so it applies to all sites served by Caddy. # To use your own domain name (with automatic HTTPS), first make # sure your domain's A/AAAA DNS records are properly pointed to # this machine's public IP, then replace \"example.com\" below with your # domain name. { # Set the ACME DNS challenge provider to use Namecheap for all sites acme_dns namecheap { api_key {env.NAMECHEAP_API_KEY} user {env.NAMECHEAP_API_USER} api_endpoint https://api.namecheap.com/xml.response client_ip {env.NAMECHEAP_CLIENT_IP} } } example.com { # Set this path to your site's directory. root * /usr/share/caddy # Enable the static file server. file_server # Another common task is to set up a reverse proxy: # reverse_proxy localhost:8080 # Or serve a PHP site through php-fpm: # php_fastcgi localhost:9000 encode gzip tls { # No need to specify dns here, it's already set globally } } another-example.com { root * /usr/share/caddy file_server encode gzip tls { # No need to specify dns here, it's already set globally } } Per-site Configuration example.com { # Set this path to your site's directory. root * /usr/share/caddy # Enable the static file server. file_server # Another common task is to set up a reverse proxy: # reverse_proxy localhost:8080 # Or serve a PHP site through php-fpm: # php_fastcgi localhost:9000 encode gzip tls { dns namecheap { api_key {env.NAMECHEAP_API_KEY} user {env.NAMECHEAP_API_USER} api_endpoint https://api.namecheap.com/xml.response client_ip {env.NAMECHEAP_CLIENT_IP} } } } another-example.com { root * /usr/share/caddy file_server encode gzip tls { dns namecheap { api_key {env.NAMECHEAP_API_KEY} user {env.NAMECHEAP_API_USER} api_endpoint https://api.namecheap.com/xml.response client_ip {env.NAMECHEAP_CLIENT_IP} } } } Configuration Creating Namecheap API Credentials To use the Namecheap DNS challenge provider, you'll need to create API credentials in your Namecheap account. Follow these steps: Log in to Namecheap : Go to the Namecheap dashboard at namecheap.com and log in with your account credentials. Enable API Access : Navigate to \"Account\" > \"Profile\" > \"Tools\" > \"API Access\". Follow the instructions to enable API access for your account. Note that Namecheap may require that you whitelist your public IP address. Get API Credentials : Once API access is enabled, you'll be able to see your API Key. You will need: API Key : Your API key from the Namecheap dashboard. Username : Your Namecheap username. Client IP : Your public IP address that has been whitelisted with Namecheap. Set Environment Variables : In your deployment environment, set the following environment variables: NAMECHEAP_API_KEY : Your Namecheap API key. NAMECHEAP_API_USER : Your Namecheap username. NAMECHEAP_CLIENT_IP : Your client IP address (optional if Namecheap can automatically detect it). For example, in a Docker environment, you can set these environment variables in your docker-compose.yml file: services : caddy : image : ghcr.io/caddybuilds/caddy-namecheap:latest restart : unless-stopped cap_add : - NET_ADMIN ports : - \" 80:80 \" - \" 443:443 \" - \" 443:443/udp \" volumes : - $PWD/Caddyfile:/etc/caddy/Caddyfile - $PWD/site:/srv - caddy_data:/data - caddy_config:/config environment : - NAMECHEAP_API_KEY=your_namecheap_api_key - NAMECHEAP_API_USER=your_namecheap_username - NAMECHEAP_CLIENT_IP=your_client_ip volumes : caddy_data : external : true caddy_config : Defining the data volume as external makes sure docker-compose down does not delete the volume. You may need to create it manually using docker volume create caddy_data . Replace your_namecheap_api_key , your_namecheap_username , and your_client_ip with your actual credentials. ACME DNS Challenge Configuration To configure the ACME DNS challenge provider for all ACME transactions, add the following to your Caddyfile: { acme_dns namecheap { api_key {env.NAMECHEAP_API_KEY} user {env.NAMECHEAP_API_USER} api_endpoint https://api.namecheap.com/xml.response client_ip {env.NAMECHEAP_CLIENT_IP} } } This configuration sets up the provider to use the Namecheap DNS module with the API credentials provided as environment variables. It ensures that your Caddy server can automatically issue and renew SSL certificates using DNS-01 challenges via Namecheap. This setup is the same as specifying the provider in the tls directive's ACME issuer configuration. Sample Caddyfile Tags The caddy-namecheap image on GitHub Container Registry and Docker Hub provides the following tags: latest : Always points to the most recent stable release of Caddy with the Namecheap DNS module. Automatically updated to ensure you have the latest features and improvements. <version> : Specific version tags for precise version control and consistency in deployments. Examples include: 2.7.6 : Full version tag for Caddy version 2.7.6, ensuring you are using this exact release. (eg: docker pull ghcr.io/caddybuilds/caddy-namecheap:2.8.0 ) 2.7 : Minor version tag for the latest patch release within the 2.7 series, allowing for minor updates without breaking changes. 2 : Major version tag for the latest release within the 2.x series, providing updates within the major version while maintaining compatibility. alpine : Always points to the latest stable release of the Alpine-based image. <version>-alpine : Specific version tags for the Alpine-based image (e.g., 2.7.6-alpine ). Platform Support The caddybuilds/caddy-namecheap image is built to support multiple platforms, ensuring compatibility across a wide range of devices and systems. The supported platforms include: linux/amd64 : Standard x86_64 architecture, commonly used in desktop and server environments. linux/arm64 : ARM 64-bit architecture, used in many modern servers and high-end ARM devices. linux/arm/v7 : ARM 32-bit architecture, widely used in devices like Raspberry Pi. linux/ppc64le : 64-bit PowerPC Little Endian architecture. linux/s390x : 64-bit IBM System z architecture. Alpine Support The Alpine-based image provides a lightweight alternative, based on the popular Alpine Linux project. Alpine Linux is much smaller than most distribution base images (~5MB), leading to much slimmer images in general. Benefits of Alpine-based Image Smaller Size : The image size is significantly reduced, which can be beneficial for faster downloads and reduced storage usage. Minimal Base : Alpine Linux uses musl libc instead of glibc, making it lightweight. However, this may lead to compatibility issues with software that requires glibc. Customization : To keep the image minimal, additional tools (such as git or bash) are not included by default. You can customize the image by adding the necessary packages in your Dockerfile. To use the Alpine-based image, pull it from the GitHub Container Registry or Docker Hub: docker pull ghcr.io/caddybuilds/caddy-namecheap:alpine docker pull caddybuilds/caddy-namecheap:alpine Raspberry Pi Support This Docker image is optimized for Raspberry Pi, allowing you to deploy Caddy with Namecheap DNS integration on these popular single-board computers. Whether you are using a Raspberry Pi 3 or the latest Raspberry Pi 4, this image provides the necessary support for seamless operation. To use the image on a Raspberry Pi, ensure you are running a compatible operating system (such as Raspberry Pi OS) and have Docker installed. You can then pull the image and run it as you would on any other system: docker pull ghcr.io/caddybuilds/caddy-namecheap:latest Building Your Own Docker Image If you prefer to build your own Docker image, follow these steps: Prerequisites GitHub account DockerHub account (if you wish to push the image to DockerHub as well) GitHub Secrets configured: GITHUB_TOKEN (automatically available in GitHub Actions) DOCKERHUB_USERNAME (optional, if you want to push to DockerHub) DOCKERHUB_TOKEN (optional, if you want to push to DockerHub) Setup Instructions Fork this repository to your GitHub account. Clone the forked repository to your local machine: git clone https://github.com/YOUR_GITHUB_USERNAME/caddy-namecheap.git cd caddy-namecheap Set up GitHub Secrets : Go to your repository on GitHub. Navigate to Settings > Secrets and variables > Actions . Add the following secrets: GITHUB_TOKEN : This is automatically available in GitHub Actions. DOCKERHUB_USERNAME : Your DockerHub username (optional). DOCKERHUB_TOKEN : Your DockerHub access token (optional). Customize the workflow (if needed): The workflow file .github/workflows/check-caddy-release.yml is configured to check for new Caddy releases and build the Docker image. You can customize the schedule or any other part of the workflow as needed. Commit and push any changes (if you made customizations): git add . git commit -m \" Customize workflow \" git push origin main Manually trigger the workflow (optional): Go to the Actions tab in your GitHub repository. Select the Build and Push Docker Image workflow. Click the Run workflow button to trigger the build process manually. Monitor the workflow : You can monitor the progress and logs of the workflow in the Actions tab of your GitHub repository. Docker image : Once the workflow completes successfully, the Docker image will be available in the GitHub Container Registry under your repository. You can pull the image using: docker pull ghcr.io/YOUR_GITHUB_USERNAME/caddy-namecheap:latest Usage You can use the built Docker image in your projects. Here is an example of how to use it in a docker-compose.yml file: services : caddy : image : ghcr.io/YOUR_GITHUB_USERNAME/caddy-namecheap:latest restart : unless-stopped cap_add : - NET_ADMIN ports : - \" 80:80 \" - \" 443:443 \" - \" 443:443/udp \" volumes : - $PWD/Caddyfile:/etc/caddy/Caddyfile - $PWD/site:/srv - caddy_data:/data - caddy_config:/config environment : - NAMECHEAP_API_KEY=your_namecheap_api_key - NAMECHEAP_API_USER=your_namecheap_username - NAMECHEAP_CLIENT_IP=your_client_ip volumes : caddy_data : external : true caddy_config : Defining the data volume as external makes sure docker-compose down does not delete the volume. You may need to create it manually using docker volume create caddy_data . Replace YOUR_GITHUB_USERNAME with your GitHub username and your Namecheap API credentials. Contributing Feel free to open issues or submit pull requests if you have any improvements or bug fixes. License This project is licensed under the MIT License. See the LICENSE file for details. About A fully integrated Caddy Docker image featuring Namecheap DNS-01 ACME validation Topics dns docker tls ssl acme caddy namecheap caddy-docker caddy-namecheapdns namecheap-dns caddy-namecheap Resources Readme License MIT license Uh oh! There was an error while loading. Please reload this page . Activity Custom properties Stars 6 stars Watchers 0 watching Forks 5 forks Report repository Releases 4 Caddy v2.11.2 Latest Mar 7, 2026 + 3 releases Packages 0 Uh oh! There was an error while loading. Please reload this page . Uh oh! There was an error while loading. Please reload this page . Contributors Uh oh! There was an error while loading. Please reload this page . Languages Python 96.8% Dockerfile 3.2% You can\u2019t perform that action at this time.", "lists": [["Platform AI CODE CREATION GitHub Copilot Write better code with AI GitHub Copilot app Direct agents from issue to merge MCP Registry New Integrate external tools DEVELOPER WORKFLOWS Actions Automate any workflow Codespaces Instant dev environments Issues Plan and track work Code Review Manage code changes APPLICATION SECURITY GitHub Advanced Security Find and fix vulnerabilities Code security Secure your code as you build Secret protection Stop leaks before they start EXPLORE Why GitHub Documentation Blog Changelog Marketplace View all features", "AI CODE CREATION GitHub Copilot Write better code with AI GitHub Copilot app Direct agents from issue to merge MCP Registry New Integrate external tools", "GitHub Copilot Write better code with AI", "GitHub Copilot app Direct agents from issue to merge", "MCP Registry New Integrate external tools", "DEVELOPER WORKFLOWS Actions Automate any workflow Codespaces Instant dev environments Issues Plan and track work Code Review Manage code changes", "Actions Automate any workflow", "Codespaces Instant dev environments", "Issues Plan and track work", "Code Review Manage code changes", "APPLICATION SECURITY GitHub Advanced Security Find and fix vulnerabilities Code security Secure your code as you build Secret protection Stop leaks before they start", "GitHub Advanced Security Find and fix vulnerabilities", "Code security Secure your code as you build", "Secret protection Stop leaks before they start", "EXPLORE Why GitHub Documentation Blog Changelog Marketplace", "Why GitHub", "Documentation", "Blog", "Changelog", "Marketplace", "Solutions BY COMPANY SIZE Enterprises Small and medium teams Startups Nonprofits BY USE CASE App Modernization DevSecOps DevOps CI/CD View all use cases BY INDUSTRY Healthcare Financial services Manufacturing Government View all industries View all solutions", "BY COMPANY SIZE Enterprises Small and medium teams Startups Nonprofits", "Enterprises", "Small and medium teams", "Startups", "Nonprofits", "BY USE CASE App Modernization DevSecOps DevOps CI/CD View all use cases", "App Modernization", "DevSecOps", "DevOps", "CI/CD", "View all use cases", "BY INDUSTRY Healthcare Financial services Manufacturing Government View all industries", "Healthcare", "Financial services", "Manufacturing", "Government", "View all industries", "Resources EXPLORE BY TOPIC AI Software Development DevOps Security View all topics EXPLORE BY TYPE Customer stories Events & webinars Ebooks & reports Business insights GitHub Skills SUPPORT & SERVICES Documentation Customer support Community forum Trust center Partners View all resources", "EXPLORE BY TOPIC AI Software Development DevOps Security View all topics", "AI", "Software Development", "DevOps", "Security", "View all topics", "EXPLORE BY TYPE Customer stories Events & webinars Ebooks & reports Business insights GitHub Skills", "Customer stories", "Events & webinars", "Ebooks & reports", "Business insights", "GitHub Skills", "SUPPORT & SERVICES Documentation Customer support Community forum Trust center Partners", "Documentation", "Customer support", "Community forum", "Trust center", "Partners", "Open Source COMMUNITY GitHub Sponsors Fund open source developers PROGRAMS Security Lab Maintainer Community Accelerator GitHub Stars Archive Program REPOSITORIES Topics Trending Collections", "COMMUNITY GitHub Sponsors Fund open source developers", "GitHub Sponsors Fund open source developers", "PROGRAMS Security Lab Maintainer Community Accelerator GitHub Stars Archive Program", "Security Lab", "Maintainer Community", "Accelerator", "GitHub Stars", "Archive Program", "REPOSITORIES Topics Trending Collections", "Topics", "Trending", "Collections", "Enterprise ENTERPRISE SOLUTIONS Enterprise platform AI-powered developer platform AVAILABLE ADD-ONS GitHub Advanced Security Enterprise-grade security features Copilot for Business Enterprise-grade AI features Premium Support Enterprise-grade 24/7 support", "ENTERPRISE SOLUTIONS Enterprise platform AI-powered developer platform", "Enterprise platform AI-powered developer platform", "AVAILABLE ADD-ONS GitHub Advanced Security Enterprise-grade security features Copilot for Business Enterprise-grade AI features Premium Support Enterprise-grade 24/7 support", "GitHub Advanced Security Enterprise-grade security features", "Copilot for Business Enterprise-grade AI features", "Premium Support Enterprise-grade 24/7 support", "Pricing"], ["AI CODE CREATION GitHub Copilot Write better code with AI GitHub Copilot app Direct agents from issue to merge MCP Registry New Integrate external tools", "GitHub Copilot Write better code with AI", "GitHub Copilot app Direct agents from issue to merge", "MCP Registry New Integrate external tools", "DEVELOPER WORKFLOWS Actions Automate any workflow Codespaces Instant dev environments Issues Plan and track work Code Review Manage code changes", "Actions Automate any workflow", "Codespaces Instant dev environments", "Issues Plan and track work", "Code Review Manage code changes", "APPLICATION SECURITY GitHub Advanced Security Find and fix vulnerabilities Code security Secure your code as you build Secret protection Stop leaks before they start", "GitHub Advanced Security Find and fix vulnerabilities", "Code security Secure your code as you build", "Secret protection Stop leaks before they start", "EXPLORE Why GitHub Documentation Blog Changelog Marketplace", "Why GitHub", "Documentation", "Blog", "Changelog", "Marketplace"], ["GitHub Copilot Write better code with AI", "GitHub Copilot app Direct agents from issue to merge", "MCP Registry New Integrate external tools"], ["Actions Automate any workflow", "Codespaces Instant dev environments", "Issues Plan and track work", "Code Review Manage code changes"], ["GitHub Advanced Security Find and fix vulnerabilities", "Code security Secure your code as you build", "Secret protection Stop leaks before they start"], ["Why GitHub", "Documentation", "Blog", "Changelog", "Marketplace"], ["BY COMPANY SIZE Enterprises Small and medium teams Startups Nonprofits", "Enterprises", "Small and medium teams", "Startups", "Nonprofits", "BY USE CASE App Modernization DevSecOps DevOps CI/CD View all use cases", "App Modernization", "DevSecOps", "DevOps", "CI/CD", "View all use cases", "BY INDUSTRY Healthcare Financial services Manufacturing Government View all industries", "Healthcare", "Financial services", "Manufacturing", "Government", "View all industries"], ["Enterprises", "Small and medium teams", "Startups", "Nonprofits"], ["App Modernization", "DevSecOps", "DevOps", "CI/CD", "View all use cases"], ["Healthcare", "Financial services", "Manufacturing", "Government", "View all industries"], ["EXPLORE BY TOPIC AI Software Development DevOps Security View all topics", "AI", "Software Development", "DevOps", "Security", "View all topics", "EXPLORE BY TYPE Customer stories Events & webinars Ebooks & reports Business insights GitHub Skills", "Customer stories", "Events & webinars", "Ebooks & reports", "Business insights", "GitHub Skills", "SUPPORT & SERVICES Documentation Customer support Community forum Trust center Partners", "Documentation", "Customer support", "Community forum", "Trust center", "Partners"], ["AI", "Software Development", "DevOps", "Security", "View all topics"], ["Customer stories", "Events & webinars", "Ebooks & reports", "Business insights", "GitHub Skills"], ["Documentation", "Customer support", "Community forum", "Trust center", "Partners"], ["COMMUNITY GitHub Sponsors Fund open source developers", "GitHub Sponsors Fund open source developers", "PROGRAMS Security Lab Maintainer Community Accelerator GitHub Stars Archive Program", "Security Lab", "Maintainer Community", "Accelerator", "GitHub Stars", "Archive Program", "REPOSITORIES Topics Trending Collections", "Topics", "Trending", "Collections"], ["GitHub Sponsors Fund open source developers"], ["Security Lab", "Maintainer Community", "Accelerator", "GitHub Stars", "Archive Program"], ["Topics", "Trending", "Collections"], ["ENTERPRISE SOLUTIONS Enterprise platform AI-powered developer platform", "Enterprise platform AI-powered developer platform", "AVAILABLE ADD-ONS GitHub Advanced Security Enterprise-grade security features Copilot for Business Enterprise-grade AI features Premium Support Enterprise-grade 24/7 support", "GitHub Advanced Security Enterprise-grade security features", "Copilot for Business Enterprise-grade AI features", "Premium Support Enterprise-grade 24/7 support"], ["Enterprise platform AI-powered developer platform"], ["GitHub Advanced Security Enterprise-grade security features", "Copilot for Business Enterprise-grade AI features", "Premium Support Enterprise-grade 24/7 support"], ["Notifications You must be signed in to change notification settings", "Fork 5", "Star 6"], ["Code", "Issues 1", "Pull requests 0", "Actions", "Projects", "Security and quality 0", "Insights"], ["Code", "Issues", "Pull requests", "Actions", "Projects", "Security and quality", "Insights"], ["README", "MIT license"], ["Features", "Usage Using the Pre-built Docker Image Building Your Own Docker Image Sample Caddyfile", "Using the Pre-built Docker Image", "Building Your Own Docker Image", "Sample Caddyfile", "Configuration ACME DNS Challenge Configuration Creating Namecheap API Credentials", "ACME DNS Challenge Configuration", "Creating Namecheap API Credentials", "Platform Support Raspberry Pi", "Raspberry Pi", "Tags", "Contributing", "License"], ["Using the Pre-built Docker Image", "Building Your Own Docker Image", "Sample Caddyfile"], ["ACME DNS Challenge Configuration", "Creating Namecheap API Credentials"], ["Raspberry Pi"], ["Automated Builds : Automatically checks for new Caddy releases and builds Docker images.", "Continuous Integration : Utilizes GitHub Actions for seamless CI/CD.", "Namecheap DNS Integration : Integrates Namecheap DNS for automatic SSL certificate management.", "Multi-Platform Support : Builds images for multiple architectures, including amd64 , arm64 , arm/v7 (Raspberry Pi), ppc64le , and s390x , ensuring compatibility across a wide range of devices and systems.", "Alpine-based Image : Provides a lightweight Alpine-based image for smaller size and faster deployment.", "Manual Trigger : Allows manual triggering of the build process.", "Open Source : Contributions are welcome under the MIT License."], ["Log in to Namecheap : Go to the Namecheap dashboard at namecheap.com and log in with your account credentials.", "Go to the Namecheap dashboard at namecheap.com and log in with your account credentials.", "Enable API Access : Navigate to \"Account\" > \"Profile\" > \"Tools\" > \"API Access\". Follow the instructions to enable API access for your account. Note that Namecheap may require that you whitelist your public IP address.", "Navigate to \"Account\" > \"Profile\" > \"Tools\" > \"API Access\".", "Follow the instructions to enable API access for your account.", "Note that Namecheap may require that you whitelist your public IP address.", "Get API Credentials : Once API access is enabled, you'll be able to see your API Key. You will need: API Key : Your API key from the Namecheap dashboard. Username : Your Namecheap username. Client IP : Your public IP address that has been whitelisted with Namecheap.", "Once API access is enabled, you'll be able to see your API Key.", "You will need: API Key : Your API key from the Namecheap dashboard. Username : Your Namecheap username. Client IP : Your public IP address that has been whitelisted with Namecheap.", "API Key : Your API key from the Namecheap dashboard.", "Username : Your Namecheap username.", "Client IP : Your public IP address that has been whitelisted with Namecheap.", "Set Environment Variables : In your deployment environment, set the following environment variables: NAMECHEAP_API_KEY : Your Namecheap API key. NAMECHEAP_API_USER : Your Namecheap username. NAMECHEAP_CLIENT_IP : Your client IP address (optional if Namecheap can automatically detect it).", "In your deployment environment, set the following environment variables: NAMECHEAP_API_KEY : Your Namecheap API key. NAMECHEAP_API_USER : Your Namecheap username. NAMECHEAP_CLIENT_IP : Your client IP address (optional if Namecheap can automatically detect it).", "NAMECHEAP_API_KEY : Your Namecheap API key.", "NAMECHEAP_API_USER : Your Namecheap username.", "NAMECHEAP_CLIENT_IP : Your client IP address (optional if Namecheap can automatically detect it)."], ["Go to the Namecheap dashboard at namecheap.com and log in with your account credentials."], ["Navigate to \"Account\" > \"Profile\" > \"Tools\" > \"API Access\".", "Follow the instructions to enable API access for your account.", "Note that Namecheap may require that you whitelist your public IP address."], ["Once API access is enabled, you'll be able to see your API Key.", "You will need: API Key : Your API key from the Namecheap dashboard. Username : Your Namecheap username. Client IP : Your public IP address that has been whitelisted with Namecheap.", "API Key : Your API key from the Namecheap dashboard.", "Username : Your Namecheap username.", "Client IP : Your public IP address that has been whitelisted with Namecheap."], ["API Key : Your API key from the Namecheap dashboard.", "Username : Your Namecheap username.", "Client IP : Your public IP address that has been whitelisted with Namecheap."], ["In your deployment environment, set the following environment variables: NAMECHEAP_API_KEY : Your Namecheap API key. NAMECHEAP_API_USER : Your Namecheap username. NAMECHEAP_CLIENT_IP : Your client IP address (optional if Namecheap can automatically detect it).", "NAMECHEAP_API_KEY : Your Namecheap API key.", "NAMECHEAP_API_USER : Your Namecheap username.", "NAMECHEAP_CLIENT_IP : Your client IP address (optional if Namecheap can automatically detect it)."], ["NAMECHEAP_API_KEY : Your Namecheap API key.", "NAMECHEAP_API_USER : Your Namecheap username.", "NAMECHEAP_CLIENT_IP : Your client IP address (optional if Namecheap can automatically detect it)."], ["latest : Always points to the most recent stable release of Caddy with the Namecheap DNS module. Automatically updated to ensure you have the latest features and improvements.", "Always points to the most recent stable release of Caddy with the Namecheap DNS module.", "Automatically updated to ensure you have the latest features and improvements.", "<version> : Specific version tags for precise version control and consistency in deployments. Examples include: 2.7.6 : Full version tag for Caddy version 2.7.6, ensuring you are using this exact release. (eg: docker pull ghcr.io/caddybuilds/caddy-namecheap:2.8.0 ) 2.7 : Minor version tag for the latest patch release within the 2.7 series, allowing for minor updates without breaking changes. 2 : Major version tag for the latest release within the 2.x series, providing updates within the major version while maintaining compatibility.", "Specific version tags for precise version control and consistency in deployments.", "Examples include: 2.7.6 : Full version tag for Caddy version 2.7.6, ensuring you are using this exact release. (eg: docker pull ghcr.io/caddybuilds/caddy-namecheap:2.8.0 ) 2.7 : Minor version tag for the latest patch release within the 2.7 series, allowing for minor updates without breaking changes. 2 : Major version tag for the latest release within the 2.x series, providing updates within the major version while maintaining compatibility.", "2.7.6 : Full version tag for Caddy version 2.7.6, ensuring you are using this exact release. (eg: docker pull ghcr.io/caddybuilds/caddy-namecheap:2.8.0 )", "2.7 : Minor version tag for the latest patch release within the 2.7 series, allowing for minor updates without breaking changes.", "2 : Major version tag for the latest release within the 2.x series, providing updates within the major version while maintaining compatibility.", "alpine : Always points to the latest stable release of the Alpine-based image. <version>-alpine : Specific version tags for the Alpine-based image (e.g., 2.7.6-alpine ).", "<version>-alpine : Specific version tags for the Alpine-based image (e.g., 2.7.6-alpine )."], ["Always points to the most recent stable release of Caddy with the Namecheap DNS module.", "Automatically updated to ensure you have the latest features and improvements."], ["Specific version tags for precise version control and consistency in deployments.", "Examples include: 2.7.6 : Full version tag for Caddy version 2.7.6, ensuring you are using this exact release. (eg: docker pull ghcr.io/caddybuilds/caddy-namecheap:2.8.0 ) 2.7 : Minor version tag for the latest patch release within the 2.7 series, allowing for minor updates without breaking changes. 2 : Major version tag for the latest release within the 2.x series, providing updates within the major version while maintaining compatibility.", "2.7.6 : Full version tag for Caddy version 2.7.6, ensuring you are using this exact release. (eg: docker pull ghcr.io/caddybuilds/caddy-namecheap:2.8.0 )", "2.7 : Minor version tag for the latest patch release within the 2.7 series, allowing for minor updates without breaking changes.", "2 : Major version tag for the latest release within the 2.x series, providing updates within the major version while maintaining compatibility."], ["2.7.6 : Full version tag for Caddy version 2.7.6, ensuring you are using this exact release. (eg: docker pull ghcr.io/caddybuilds/caddy-namecheap:2.8.0 )", "2.7 : Minor version tag for the latest patch release within the 2.7 series, allowing for minor updates without breaking changes.", "2 : Major version tag for the latest release within the 2.x series, providing updates within the major version while maintaining compatibility."], ["<version>-alpine : Specific version tags for the Alpine-based image (e.g., 2.7.6-alpine )."], ["linux/amd64 : Standard x86_64 architecture, commonly used in desktop and server environments.", "linux/arm64 : ARM 64-bit architecture, used in many modern servers and high-end ARM devices.", "linux/arm/v7 : ARM 32-bit architecture, widely used in devices like Raspberry Pi.", "linux/ppc64le : 64-bit PowerPC Little Endian architecture.", "linux/s390x : 64-bit IBM System z architecture."], ["Smaller Size : The image size is significantly reduced, which can be beneficial for faster downloads and reduced storage usage.", "Minimal Base : Alpine Linux uses musl libc instead of glibc, making it lightweight. However, this may lead to compatibility issues with software that requires glibc.", "Customization : To keep the image minimal, additional tools (such as git or bash) are not included by default. You can customize the image by adding the necessary packages in your Dockerfile."], ["GitHub account", "DockerHub account (if you wish to push the image to DockerHub as well)", "GitHub Secrets configured: GITHUB_TOKEN (automatically available in GitHub Actions) DOCKERHUB_USERNAME (optional, if you want to push to DockerHub) DOCKERHUB_TOKEN (optional, if you want to push to DockerHub)", "GITHUB_TOKEN (automatically available in GitHub Actions)", "DOCKERHUB_USERNAME (optional, if you want to push to DockerHub)", "DOCKERHUB_TOKEN (optional, if you want to push to DockerHub)"], ["GITHUB_TOKEN (automatically available in GitHub Actions)", "DOCKERHUB_USERNAME (optional, if you want to push to DockerHub)", "DOCKERHUB_TOKEN (optional, if you want to push to DockerHub)"], ["Fork this repository to your GitHub account.", "Clone the forked repository to your local machine: git clone https://github.com/YOUR_GITHUB_USERNAME/caddy-namecheap.git cd caddy-namecheap", "Set up GitHub Secrets : Go to your repository on GitHub. Navigate to Settings > Secrets and variables > Actions . Add the following secrets: GITHUB_TOKEN : This is automatically available in GitHub Actions. DOCKERHUB_USERNAME : Your DockerHub username (optional). DOCKERHUB_TOKEN : Your DockerHub access token (optional).", "Go to your repository on GitHub.", "Navigate to Settings > Secrets and variables > Actions .", "Add the following secrets: GITHUB_TOKEN : This is automatically available in GitHub Actions. DOCKERHUB_USERNAME : Your DockerHub username (optional). DOCKERHUB_TOKEN : Your DockerHub access token (optional).", "GITHUB_TOKEN : This is automatically available in GitHub Actions.", "DOCKERHUB_USERNAME : Your DockerHub username (optional).", "DOCKERHUB_TOKEN : Your DockerHub access token (optional).", "Customize the workflow (if needed): The workflow file .github/workflows/check-caddy-release.yml is configured to check for new Caddy releases and build the Docker image. You can customize the schedule or any other part of the workflow as needed.", "The workflow file .github/workflows/check-caddy-release.yml is configured to check for new Caddy releases and build the Docker image. You can customize the schedule or any other part of the workflow as needed.", "Commit and push any changes (if you made customizations): git add . git commit -m \" Customize workflow \" git push origin main", "Manually trigger the workflow (optional): Go to the Actions tab in your GitHub repository. Select the Build and Push Docker Image workflow. Click the Run workflow button to trigger the build process manually.", "Go to the Actions tab in your GitHub repository.", "Select the Build and Push Docker Image workflow.", "Click the Run workflow button to trigger the build process manually.", "Monitor the workflow : You can monitor the progress and logs of the workflow in the Actions tab of your GitHub repository.", "You can monitor the progress and logs of the workflow in the Actions tab of your GitHub repository.", "Docker image : Once the workflow completes successfully, the Docker image will be available in the GitHub Container Registry under your repository. You can pull the image using: docker pull ghcr.io/YOUR_GITHUB_USERNAME/caddy-namecheap:latest", "Once the workflow completes successfully, the Docker image will be available in the GitHub Container Registry under your repository.", "You can pull the image using: docker pull ghcr.io/YOUR_GITHUB_USERNAME/caddy-namecheap:latest"], ["Go to your repository on GitHub.", "Navigate to Settings > Secrets and variables > Actions .", "Add the following secrets: GITHUB_TOKEN : This is automatically available in GitHub Actions. DOCKERHUB_USERNAME : Your DockerHub username (optional). DOCKERHUB_TOKEN : Your DockerHub access token (optional).", "GITHUB_TOKEN : This is automatically available in GitHub Actions.", "DOCKERHUB_USERNAME : Your DockerHub username (optional).", "DOCKERHUB_TOKEN : Your DockerHub access token (optional)."], ["GITHUB_TOKEN : This is automatically available in GitHub Actions.", "DOCKERHUB_USERNAME : Your DockerHub username (optional).", "DOCKERHUB_TOKEN : Your DockerHub access token (optional)."], ["The workflow file .github/workflows/check-caddy-release.yml is configured to check for new Caddy releases and build the Docker image. You can customize the schedule or any other part of the workflow as needed."], ["Go to the Actions tab in your GitHub repository.", "Select the Build and Push Docker Image workflow.", "Click the Run workflow button to trigger the build process manually."], ["You can monitor the progress and logs of the workflow in the Actions tab of your GitHub repository."], ["Once the workflow completes successfully, the Docker image will be available in the GitHub Container Registry under your repository.", "You can pull the image using: docker pull ghcr.io/YOUR_GITHUB_USERNAME/caddy-namecheap:latest"], ["", "", ""], ["Python 96.8%", "Dockerfile 3.2%"], ["Terms", "Privacy", "Security", "Status", "Community", "Docs", "Contact", "Manage cookies", "Do not share my personal information"]], "tables": [[["Name", "Name", "Last commit message", "Last commit date"], ["Latest commit History 8 Commits 8 Commits"], [".github/ workflows", ".github/ workflows", "", ""], ["scripts", "scripts", "", ""], ["Caddyfile_global", "Caddyfile_global", "", ""], ["Caddyfile_per_site", "Caddyfile_per_site", "", ""], ["Dockerfile", "Dockerfile", "", ""], ["Dockerfile.alpine", "Dockerfile.alpine", "", ""], ["LICENSE", "LICENSE", "", ""], ["README.md", "README.md", "", ""], ["View all files"]]], "code_blocks": ["amd64", "arm64", "arm/v7", "ppc64le", "s390x", "docker pull ghcr.io/caddybuilds/caddy-namecheap:latest\ndocker pull caddybuilds/caddy-namecheap:latest # alpine docker pull ghcr.io/caddybuilds/caddy-namecheap:alpine\ndocker pull caddybuilds/caddy-namecheap:alpine", "docker-compose.yml", "services : caddy : image : ghcr.io/caddybuilds/caddy-namecheap:latest restart : unless-stopped cap_add :\n      - NET_ADMIN ports :\n      - \" 80:80 \" - \" 443:443 \" - \" 443:443/udp \" volumes :\n      - $PWD/Caddyfile:/etc/caddy/Caddyfile - $PWD/site:/srv - caddy_data:/data - caddy_config:/config environment :\n      - NAMECHEAP_API_KEY=your_namecheap_api_key - NAMECHEAP_API_USER=your_namecheap_username - NAMECHEAP_CLIENT_IP=your_client_ip volumes : caddy_data : external : true caddy_config :", "docker-compose down", "docker volume create caddy_data", "your_namecheap_api_key", "your_namecheap_username", "your_client_ip", "# To use your own domain name (with automatic HTTPS), first make\n# sure your domain's A/AAAA DNS records are properly pointed to\n# this machine's public IP, then replace \"example.com\" below with your\n# domain name.\n\n{\n  # Set the ACME DNS challenge provider to use Namecheap for all sites\n  acme_dns namecheap {\n    api_key {env.NAMECHEAP_API_KEY}\n    user {env.NAMECHEAP_API_USER}\n    api_endpoint https://api.namecheap.com/xml.response\n    client_ip {env.NAMECHEAP_CLIENT_IP}\n  }\n}\n\nexample.com {\n\n    # Set this path to your site's directory.\n    root * /usr/share/caddy\n\n    # Enable the static file server.\n    file_server\n\n    # Another common task is to set up a reverse proxy:\n    # reverse_proxy localhost:8080\n\n    # Or serve a PHP site through php-fpm:\n    # php_fastcgi localhost:9000\n\n    encode gzip\n\n    tls {\n      # No need to specify dns here, it's already set globally\n    }\n}\n\nanother-example.com {\n    root * /usr/share/caddy\n    file_server\n    encode gzip\n\n    tls {\n        # No need to specify dns here, it's already set globally\n    }\n}", "# To use your own domain name (with automatic HTTPS), first make\n# sure your domain's A/AAAA DNS records are properly pointed to\n# this machine's public IP, then replace \"example.com\" below with your\n# domain name.\n\n{\n  # Set the ACME DNS challenge provider to use Namecheap for all sites\n  acme_dns namecheap {\n    api_key {env.NAMECHEAP_API_KEY}\n    user {env.NAMECHEAP_API_USER}\n    api_endpoint https://api.namecheap.com/xml.response\n    client_ip {env.NAMECHEAP_CLIENT_IP}\n  }\n}\n\nexample.com {\n\n    # Set this path to your site's directory.\n    root * /usr/share/caddy\n\n    # Enable the static file server.\n    file_server\n\n    # Another common task is to set up a reverse proxy:\n    # reverse_proxy localhost:8080\n\n    # Or serve a PHP site through php-fpm:\n    # php_fastcgi localhost:9000\n\n    encode gzip\n\n    tls {\n      # No need to specify dns here, it's already set globally\n    }\n}\n\nanother-example.com {\n    root * /usr/share/caddy\n    file_server\n    encode gzip\n\n    tls {\n        # No need to specify dns here, it's already set globally\n    }\n}", "example.com {\n  \n    # Set this path to your site's directory.\n    root * /usr/share/caddy\n\n    # Enable the static file server.\n    file_server\n\n    # Another common task is to set up a reverse proxy:\n    # reverse_proxy localhost:8080\n\n    # Or serve a PHP site through php-fpm:\n    # php_fastcgi localhost:9000\n\n    encode gzip\n\n    tls {\n        dns namecheap {\n            api_key {env.NAMECHEAP_API_KEY}\n            user {env.NAMECHEAP_API_USER}\n            api_endpoint https://api.namecheap.com/xml.response\n            client_ip {env.NAMECHEAP_CLIENT_IP}\n        }\n    }\n}\n\nanother-example.com {\n    root * /usr/share/caddy\n    file_server\n    encode gzip\n\n    tls {\n        dns namecheap {\n            api_key {env.NAMECHEAP_API_KEY}\n            user {env.NAMECHEAP_API_USER}\n            api_endpoint https://api.namecheap.com/xml.response\n            client_ip {env.NAMECHEAP_CLIENT_IP}\n        }\n    }\n}", "example.com {\n  \n    # Set this path to your site's directory.\n    root * /usr/share/caddy\n\n    # Enable the static file server.\n    file_server\n\n    # Another common task is to set up a reverse proxy:\n    # reverse_proxy localhost:8080\n\n    # Or serve a PHP site through php-fpm:\n    # php_fastcgi localhost:9000\n\n    encode gzip\n\n    tls {\n        dns namecheap {\n            api_key {env.NAMECHEAP_API_KEY}\n            user {env.NAMECHEAP_API_USER}\n            api_endpoint https://api.namecheap.com/xml.response\n            client_ip {env.NAMECHEAP_CLIENT_IP}\n        }\n    }\n}\n\nanother-example.com {\n    root * /usr/share/caddy\n    file_server\n    encode gzip\n\n    tls {\n        dns namecheap {\n            api_key {env.NAMECHEAP_API_KEY}\n            user {env.NAMECHEAP_API_USER}\n            api_endpoint https://api.namecheap.com/xml.response\n            client_ip {env.NAMECHEAP_CLIENT_IP}\n        }\n    }\n}", "NAMECHEAP_API_KEY", "NAMECHEAP_API_USER", "NAMECHEAP_CLIENT_IP", "docker-compose.yml", "services : caddy : image : ghcr.io/caddybuilds/caddy-namecheap:latest restart : unless-stopped cap_add :\n      - NET_ADMIN ports :\n      - \" 80:80 \" - \" 443:443 \" - \" 443:443/udp \" volumes :\n      - $PWD/Caddyfile:/etc/caddy/Caddyfile - $PWD/site:/srv - caddy_data:/data - caddy_config:/config environment :\n      - NAMECHEAP_API_KEY=your_namecheap_api_key - NAMECHEAP_API_USER=your_namecheap_username - NAMECHEAP_CLIENT_IP=your_client_ip volumes : caddy_data : external : true caddy_config :", "docker-compose down", "docker volume create caddy_data", "your_namecheap_api_key", "your_namecheap_username", "your_client_ip", "{\n   acme_dns namecheap {\n       api_key {env.NAMECHEAP_API_KEY}\n       user {env.NAMECHEAP_API_USER}\n       api_endpoint https://api.namecheap.com/xml.response\n       client_ip {env.NAMECHEAP_CLIENT_IP}\n   }\n}", "{\n   acme_dns namecheap {\n       api_key {env.NAMECHEAP_API_KEY}\n       user {env.NAMECHEAP_API_USER}\n       api_endpoint https://api.namecheap.com/xml.response\n       client_ip {env.NAMECHEAP_CLIENT_IP}\n   }\n}", "latest", "<version>", "2.7.6", "docker pull ghcr.io/caddybuilds/caddy-namecheap:2.8.0", "2.7", "2", "alpine", "<version>-alpine", "2.7.6-alpine", "caddybuilds/caddy-namecheap", "docker pull ghcr.io/caddybuilds/caddy-namecheap:alpine\ndocker pull caddybuilds/caddy-namecheap:alpine", "docker pull ghcr.io/caddybuilds/caddy-namecheap:latest", "GITHUB_TOKEN", "DOCKERHUB_USERNAME", "DOCKERHUB_TOKEN", "git clone https://github.com/YOUR_GITHUB_USERNAME/caddy-namecheap.git cd caddy-namecheap", "Settings", "Secrets and variables", "Actions", "GITHUB_TOKEN", "DOCKERHUB_USERNAME", "DOCKERHUB_TOKEN", ".github/workflows/check-caddy-release.yml", "git add . git commit -m \" Customize workflow \" git push origin main", "Actions", "Build and Push Docker Image", "Run workflow", "Actions", "docker pull ghcr.io/YOUR_GITHUB_USERNAME/caddy-namecheap:latest", "docker-compose.yml", "services : caddy : image : ghcr.io/YOUR_GITHUB_USERNAME/caddy-namecheap:latest restart : unless-stopped cap_add :\n      - NET_ADMIN ports :\n      - \" 80:80 \" - \" 443:443 \" - \" 443:443/udp \" volumes :\n      - $PWD/Caddyfile:/etc/caddy/Caddyfile - $PWD/site:/srv - caddy_data:/data - caddy_config:/config environment :\n      - NAMECHEAP_API_KEY=your_namecheap_api_key - NAMECHEAP_API_USER=your_namecheap_username - NAMECHEAP_CLIENT_IP=your_client_ip volumes : caddy_data : external : true caddy_config :", "docker-compose down", "docker volume create caddy_data", "YOUR_GITHUB_USERNAME"], "meta_description": "A fully integrated Caddy Docker image featuring Namecheap DNS-01 ACME validation  - GitHub - CaddyBuilds/caddy-namecheap: A fully integrated Caddy Docker image featuring Namecheap DNS-01 ACME validation", "meta_keywords": "", "og_image": "https://opengraph.githubassets.com/8607ced3f56d1e2e08c1a4b010cb1ff8bcd1edfb09fb7e58ff7f106148befb2b/CaddyBuilds/caddy-namecheap", "js_rendered": true, "js_message": "Page appears to be rendered by a JavaScript framework; content may be incomplete.", "success": true, "error": "", "truncated": false, "fetched_bytes": 368414, "total_bytes": null}}