[{"_1":2,"_155":-5,"_156":-5},"loaderData",{"_3":4,"_13":14,"_21":22,"_134":135},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","routes/_layout",{"_15":-5,"_16":17,"_18":17,"_19":11,"_20":11},"username","isAskGordonEnabled",true,"isUsingNewTemplate","showMinimalLanding","showHoneypotTrap","routes/_layout.r.$namespace.$reponame",{"_23":24,"_25":-5,"_26":11,"_27":11,"_28":29,"_30":31,"_32":-5,"_33":11,"_34":35,"_84":-5,"_85":86,"_125":-5,"_126":11,"_127":17,"_128":11,"_129":-5,"_130":11,"_131":-5,"_132":133},"canonicalUrl","https://hub.docker.com/r/skyer/letsencrypt/tags","mcpServer","canSeeDockerfile","canSeeAutobuilds","namespace","skyer","reponame","letsencrypt","cloudBuildSource","isAutobuildsAvailable","repo",{"_36":37,"_38":39,"_41":42,"_43":44,"_45":11,"_46":47,"_48":49,"_50":51,"_53":31,"_28":29,"_54":55,"_56":40,"_57":58,"_59":60,"_61":62,"_63":-5,"_64":58,"_65":66,"_67":11,"_68":29,"_69":70,"_75":11,"_76":77,"_81":29,"_82":83},"categories",[],"content_types",[40],"image","date_registered","2019-05-10T04:30:22.565337Z","description","linuxserver/letsencrypt with cerbot-dns-aliyun plugin","is_private","last_updated","2019-08-12T14:37:44.568734Z","last_modified","2024-10-16T13:48:34.145251Z","media_types",[52],"application/vnd.docker.container.image.v1+json","name","pull_count",324,"repository_type","star_count",0,"status",1,"status_description","active","source","collaborator_count","full_description","[![linuxserver.io](https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/linuxserver_medium.png)](https://linuxserver.io)\n\nThe [LinuxServer.io](https://linuxserver.io) team brings you another container release featuring :-\n\n * regular and timely application updates\n * easy user mappings (PGID, PUID)\n * custom base image with s6 overlay\n * weekly base OS updates with common layers across the entire LinuxServer.io ecosystem to minimise space usage, down time and bandwidth\n * regular security updates\n\nFind us at:\n* [Discord](https://discord.gg/YWrKVTn) - realtime support / chat with the community and the team.\n* [IRC](https://irc.linuxserver.io) - on freenode at `#linuxserver.io`. Our primary support channel is Discord.\n* [Blog](https://blog.linuxserver.io) - all the things you can do with our containers including How-To guides, opinions and much more!\n\n# [linuxserver/letsencrypt](https://github.com/linuxserver/docker-letsencrypt)\n[![](https://img.shields.io/discord/354974912613449730.svg?logo=discord&label=LSIO%20Discord&style=flat-square)](https://discord.gg/YWrKVTn)\n[![](https://images.microbadger.com/badges/version/linuxserver/letsencrypt.svg)](https://microbadger.com/images/linuxserver/letsencrypt \"Get your own version badge on microbadger.com\")\n[![](https://images.microbadger.com/badges/image/linuxserver/letsencrypt.svg)](https://microbadger.com/images/linuxserver/letsencrypt \"Get your own version badge on microbadger.com\")\n![Docker Pulls](https://img.shields.io/docker/pulls/linuxserver/letsencrypt.svg)\n![Docker Stars](https://img.shields.io/docker/stars/linuxserver/letsencrypt.svg)\n[![Build Status](https://ci.linuxserver.io/buildStatus/icon?job=Docker-Pipeline-Builders/docker-letsencrypt/master)](https://ci.linuxserver.io/job/Docker-Pipeline-Builders/job/docker-letsencrypt/job/master/)\n[![](https://lsio-ci.ams3.digitaloceanspaces.com/linuxserver/letsencrypt/latest/badge.svg)](https://lsio-ci.ams3.digitaloceanspaces.com/linuxserver/letsencrypt/latest/index.html)\n\n[Letsencrypt](https://letsencrypt.org/) sets up an Nginx webserver and reverse proxy with php support and a built-in letsencrypt client that automates free SSL server certificate generation and renewal processes. It also contains fail2ban for intrusion prevention.\n\n[![letsencrypt](https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/le-logo-wide.png)](https://letsencrypt.org/)\n\n## Supported Architectures\n\nOur images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/). \n\nSimply pulling `linuxserver/letsencrypt` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.\n\nThe architectures supported by this image are:\n\n| Architecture | Tag |\n| :----: | --- |\n| x86-64 | amd64-latest |\n| arm64 | arm64v8-latest |\n| armhf | arm32v7-latest |\n\n\n## Usage\n\nHere are some example snippets to help you get started creating a container.\n\n### docker\n\n```\ndocker create \\\n --name=letsencrypt \\\n --cap-add=NET_ADMIN \\\n -e PUID=1000 \\\n -e PGID=1000 \\\n -e TZ=Europe/London \\\n -e URL=yourdomain.url \\\n -e SUBDOMAINS=www, \\\n -e VALIDATION=http \\\n -e DNSPLUGIN=cloudflare `#optional` \\\n -e DUCKDNSTOKEN= `#optional` \\\n -e EMAIL= `#optional` \\\n -e DHLEVEL=2048 `#optional` \\\n -e ONLY_SUBDOMAINS=false `#optional` \\\n -e EXTRA_DOMAINS= `#optional` \\\n -e STAGING=false `#optional` \\\n -p 443:443 \\\n -p 80:80 `#optional` \\\n -v :/config \\\n --restart unless-stopped \\\n linuxserver/letsencrypt\n```\n\n\n### docker-compose\n\nCompatible with docker-compose v2 schemas.\n\n```\n---\nversion: \"2\"\nservices:\n letsencrypt:\n image: linuxserver/letsencrypt\n container_name: letsencrypt\n cap_add:\n - NET_ADMIN\n environment:\n - PUID=1000\n - PGID=1000\n - TZ=Europe/London\n - URL=yourdomain.url\n - SUBDOMAINS=www,\n - VALIDATION=http\n - DNSPLUGIN=cloudflare #optional\n - DUCKDNSTOKEN= #optional\n - EMAIL= #optional\n - DHLEVEL=2048 #optional\n - ONLY_SUBDOMAINS=false #optional\n - EXTRA_DOMAINS= #optional\n - STAGING=false #optional\n volumes:\n - :/config\n ports:\n - 443:443\n - 80:80 #optional\n restart: unless-stopped\n```\n\n## Parameters\n\nContainer images are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate `:` respectively. For example, `-p 8080:80` would expose port `80` from inside the container to be accessible from the host's IP on port `8080` outside the container.\n\n| Parameter | Function |\n| :----: | --- |\n| `-p 443` | Https port |\n| `-p 80` | Http port (required for http validation only) |\n| `-e PUID=1000` | for UserID - see below for explanation |\n| `-e PGID=1000` | for GroupID - see below for explanation |\n| `-e TZ=Europe/London` | Specify a timezone to use EG Europe/London. |\n| `-e URL=yourdomain.url` | Top url you have control over (`customdomain.com` if you own it, or `customsubdomain.ddnsprovider.com` if dynamic dns). |\n| `-e SUBDOMAINS=www,` | Subdomains you'd like the cert to cover (comma separated, no spaces) ie. `www,ftp,cloud`. For a wildcard cert, set this _exactly_ to `wildcard` (wildcard cert is available via `dns` and `duckdns` validation only) |\n| `-e VALIDATION=http` | Letsencrypt validation method to use, options are `http`, `tls-sni`, `dns` or `duckdns` (`dns` method also requires `DNSPLUGIN` variable set) (`duckdns` method requires `DUCKDNSTOKEN` variable set, and the `SUBDOMAINS` variable must be either empty or set to `wildcard`). |\n| `-e DNSPLUGIN=cloudflare` | Required if `VALIDATION` is set to `dns`. Options are `cloudflare`, `cloudxns`, `digitalocean`, `dnsimple`, `dnsmadeeasy`, `google`, `luadns`, `nsone`, `ovh`, `rfc2136` and `route53`. Also need to enter the credentials into the corresponding ini file under `/config/dns-conf`. |\n| `-e DUCKDNSTOKEN=` | Required if `VALIDATION` is set to `duckdns`. Retrieve your token from https://www.duckdns.org |\n| `-e EMAIL=` | Optional e-mail address used for cert expiration notifications. |\n| `-e DHLEVEL=2048` | Dhparams bit value (default=2048, can be set to `1024` or `4096`). |\n| `-e ONLY_SUBDOMAINS=false` | If you wish to get certs only for certain subdomains, but not the main domain (main domain may be hosted on another machine and cannot be validated), set this to `true` |\n| `-e EXTRA_DOMAINS=` | Additional fully qualified domain names (comma separated, no spaces) ie. `extradomain.com,subdomain.anotherdomain.org` |\n| `-e STAGING=false` | Set to `true` to retrieve certs in staging mode. Rate limits will be much higher, but the resulting cert will not pass the browser's security test. Only to be used for testing purposes. |\n| `-v /config` | All the config files including the webroot reside here. |\n\n## User / Group Identifiers\n\nWhen using volumes (`-v` flags) permissions issues can arise between the host OS and the container, we avoid this issue by allowing you to specify the user `PUID` and group `PGID`.\n\nEnsure any volume directories on the host are owned by the same user you specify and any permissions issues will vanish like magic.\n\nIn this instance `PUID=1000` and `PGID=1000`, to find yours use `id user` as below:\n\n```\n $ id username\n uid=1000(dockeruser) gid=1000(dockergroup) groups=1000(dockergroup)\n```\n\n\n \n## Application Setup\n\n### Validation and initial setup\n* Before running this container, make sure that the url and subdomains are properly forwarded to this container's host, and that port 443 (and/or 80) is not being used by another service on the host (NAS gui, another webserver, etc.).\n* For `http` validation, port 80 on the internet side of the router should be forwarded to this container's port 80\n* For `tls-sni` validation, port 443 on the internet side of the router should be forwarded to this container's port 443\n* For `dns` validation, make sure to enter your credentials into the corresponding ini file under `/config/dns-conf`\n * Cloudflare provides free accounts for managing dns and is very easy to use with this image. Make sure that it is set up for \"dns only\" instead of \"dns + proxy\"\n * Google dns plugin is meant to be used with \"Google Cloud DNS\", a paid enterprise product, and not for \"Google Domains DNS\"\n* For `duckdns` validation, either leave the `SUBDOMAINS` variable empty or set it to `wildcard`, and set the `DUCKDNSTOKEN` variable with your duckdns token. Due to a limitation of duckdns, the resulting cert will only cover either main subdomain (ie. `yoursubdomain.duckdns.org`), or sub-subdomains (ie. `*.yoursubdomain.duckdns.org`), but will not both at the same time. You can use our [duckdns image](https://hub.docker.com/r/linuxserver/duckdns/) to update your IP on duckdns.org.\n* `--cap-add=NET_ADMIN` is required for fail2ban to modify iptables\n* If you need a dynamic dns provider, you can use the free provider duckdns.org where the `URL` will be `yoursubdomain.duckdns.org` and the `SUBDOMAINS` can be `www,ftp,cloud` with http validation, or `wildcard` with dns validation.\n* After setup, navigate to `https://yourdomain.url` to access the default homepage (http access through port 80 is disabled by default, you can enable it by editing the default site config at `/config/nginx/site-confs/default`).\n* Certs are checked nightly and if expiration is within 30 days, renewal is attempted. If your cert is about to expire in less than 30 days, check the logs under `/config/log/letsencrypt` to see why the renewals have been failing. It is recommended to input your e-mail in docker parameters so you receive expiration notices from letsencrypt in those circumstances.\n### Security and password protection\n* The container detects changes to url and subdomains, revokes existing certs and generates new ones during start. It also detects changes to the DHLEVEL parameter and replaces the dhparams file.\n* If you'd like to password protect your sites, you can use htpasswd. Run the following command on your host to generate the htpasswd file `docker exec -it letsencrypt htpasswd -c /config/nginx/.htpasswd `\n* You can add multiple user:pass to `.htpasswd`. For the first user, use the above command, for others, use the above command without the `-c` flag, as it will force deletion of the existing `.htpasswd` and creation of a new one\n* You can also use ldap auth for security and access control. A sample, user configurable ldap.conf is provided, and it requires the separate image [linuxserver/ldap-auth](https://hub.docker.com/r/linuxserver/ldap-auth/) to communicate with an ldap server.\n### Site config and reverse proxy\n* The default site config resides at `/config/nginx/site-confs/default`. Feel free to modify this file, and you can add other conf files to this directory. However, if you delete the `default` file, a new default will be created on container start.\n* Preset reverse proxy config files are added for popular apps. See the `README.md` file under `/config/nginx/proxy_confs` for instructions on how to enable them. The preset confs reside in and get imported from [this repo](https://github.com/linuxserver/reverse-proxy-confs).\n* If you wish to hide your site from search engine crawlers, you may find it useful to add this configuration line to your site config, within the server block, above the line where ssl.conf is included\n`add_header X-Robots-Tag \"noindex, nofollow, nosnippet, noarchive\";`\nThis will *ask* Google et al not to index and list your site. Be careful with this, as you will eventually be de-listed if you leave this line in on a site you wish to be present on search engines\n### Using certs in other containers\n* This container includes auto-generated pfx and private-fullchain-bundle pem certs that are needed by other apps like Emby and Znc.\n * To use these certs in other containers, do either of the following:\n 1. *(Easier)* Mount the letsencrypt config folder in other containers (ie. `-v /path-to-le-config:/le-ssl`) and in the other containers, use the cert location `/le-ssl/keys/letsencrypt/`\n 2. *(More secure)* Mount the letsencrypt folder `etc/letsencrypt` that resides under `/config` in other containers (ie. `-v /path-to-le-config/etc/letsencrypt:/le-ssl`) and in the other containers, use the cert location `/le-ssl/live//` (This is more secure because the first method shares the entire letsencrypt config folder with other containers, including the www files, whereas the second method only shares the ssl certs)\n * These certs include:\n 1. `cert.pem`, `chain.pem`, `fullchain.pem` and `privkey.pem`, which are generated by letsencrypt and used by nginx and various other apps\n 2. `privkey.pfx`, a format supported by Microsoft and commonly used by dotnet apps such as Emby Server (no password)\n 3. `priv-fullchain-bundle.pem`, a pem cert that bundles the private key and the fullchain, used by apps like ZNC\n### Using fail2ban\n* This container includes fail2ban set up with 3 jails by default:\n 1. nginx-http-auth\n 2. nginx-badbots\n 3. nginx-botsearch\n* To enable or disable other jails, modify the file `/config/fail2ban/jail.local`\n* To modify filters and actions, instead of editing the `.conf` files, create `.local` files with the same name and edit those because .conf files get overwritten when the actions and filters are updated. `.local` files will append whatever's in the `.conf` files (ie. `nginx-http-auth.conf` --> `nginx-http-auth.local`)\n* You can check which jails are active via `docker exec -it letsencrypt fail2ban-client status`\n* You can check the status of a specific jail via `docker exec -it letsencrypt fail2ban-client status `\n* You can unban an IP via `docker exec -it letsencrypt fail2ban-client set unbanip `\n* A list of commands can be found here: https://www.fail2ban.org/wiki/index.php/Commands \n\n\n\n## Support Info\n\n* Shell access whilst the container is running: `docker exec -it letsencrypt /bin/bash`\n* To monitor the logs of the container in realtime: `docker logs -f letsencrypt`\n* container version number \n * `docker inspect -f '{{ index .Config.Labels \"build_version\" }}' letsencrypt`\n* image version number\n * `docker inspect -f '{{ index .Config.Labels \"build_version\" }}' linuxserver/letsencrypt`\n\n## Updating Info\n\nMost of our images are static, versioned, and require an image update and container recreation to update the app inside. With some exceptions (ie. nextcloud, plex), we do not recommend or support updating apps inside the container. Please consult the [Application Setup](#application-setup) section above to see if it is recommended for the image. \n \nBelow are the instructions for updating containers: \n \n### Via Docker Run/Create\n* Update the image: `docker pull linuxserver/letsencrypt`\n* Stop the running container: `docker stop letsencrypt`\n* Delete the container: `docker rm letsencrypt`\n* Recreate a new container with the same docker create parameters as instructed above (if mapped correctly to a host folder, your `/config` folder and settings will be preserved)\n* Start the new container: `docker start letsencrypt`\n* You can also remove the old dangling images: `docker image prune`\n\n### Via Docker Compose\n* Update all images: `docker-compose pull`\n * or update a single image: `docker-compose pull letsencrypt`\n* Let compose update all containers as necessary: `docker-compose up -d`\n * or update a single container: `docker-compose up -d letsencrypt`\n* You can also remove the old dangling images: `docker image prune`\n\n### Via Watchtower auto-updater (especially useful if you don't remember the original parameters)\n* Pull the latest image at its tag and replace it with the same env variables in one run:\n ```\n docker run --rm \\\n -v /var/run/docker.sock:/var/run/docker.sock \\\n containrrr/watchtower \\\n --run-once letsencrypt\n ```\n\n**Note:** We do not endorse the use of Watchtower as a solution to automated updates of existing Docker containers. In fact we generally discourage automated updates. However, this is a useful tool for one-time manual updates of containers where you have forgotten the original parameters. In the long term, we highly recommend using Docker Compose.\n\n* You can also remove the old dangling images: `docker image prune`\n\n## Building locally\n\nIf you want to make local modifications to these images for development purposes or just to customize the logic: \n```\ngit clone https://github.com/linuxserver/docker-letsencrypt.git\ncd docker-letsencrypt\ndocker build \\\n --no-cache \\\n --pull \\\n -t linuxserver/letsencrypt:latest .\n```\n\nThe ARM variants can be built on x86_64 hardware using `multiarch/qemu-user-static`\n```\ndocker run --rm --privileged multiarch/qemu-user-static:register --reset\n```\n\nOnce registered you can define the dockerfile to use with `-f Dockerfile.aarch64`.\n\n## Versions\n\n* **06.08.19:** - Add php7-ftp.\n* **04.08.19:** - Add php7-bcmath, php7-pear, php7-xmlrpc.\n* **02.08.19:** - Add php7-ldap, remove geoip v1(deprecated).\n* **01.08.19:** - Mark https redirect block as default_server (effective only for new installs).\n* **31.07.19:** - Create GeoIP2 databse (libmaxminddb) during container start if it doesn't exist.\n* **30.07.19:** - Support main domain via duckdns validation.\n* **29.07.19:** - Enable http to https redirect by default (effective only for new installs).\n* **01.07.19:** - Patch geoip2 module until upstream is fixed.\n* **30.06.19:** - Add geoip2 module.\n* **28.06.19:** - Rebasing to alpine 3.10.\n* **19.06.19:** - Set resolver to docker dns in ssl.conf.\n* **29.05.19:** - Compensate for changes to the reverse-proxy-confs repo.\n* **26.05.19:** - Remove botocore/urllib patch.\n* **08.05.19:** - Remove default.conf when nginx is upgraded in downstream image.\n* **30.04.19:** - Add php-redis.\n* **12.04.19:** - Rebase aarch64 image to 3.9.\n* **25.03.19:** - Rebase aarch64 image back to 3.8 due to python issues (specifically with fail2ban), switch packages to python 3 on amd64 and armhf, clean up pip/python cache to shrink image size.\n* **23.03.19:** - Switching to new Base images, shift to arm32v7 tag.\n* **10.03.19:** - Add TLSv1.3 to ssl.conf.\n* **02.03.19:** - Add php intl and posix modules.\n* **27.02.19:** - Add gnupg package.\n* **22.02.19:** - Rebase to alpine 3.9.\n* **03.02.19:** - Removed memcached due to seccomp errors. Let us know if you need to re-enable memcached.\n* **28.01.19:** - Add pipeline logic and multi arch.\n* **21.01.19:** - Remove client_body_max from proxy.conf (existing users need to manually update).\n* **09.01.19:** - Remove tls v1 and v1.1 from default ssl.conf, update ciphers (existing users need to manually update).\n* **30.12.18:** - Fix bundle key generation.\n* **19.12.18:** - Add ipv6 and http/2 support to default site config.\n* **08.12.18:** - Had to remove cert renewal during container start due to certbot's new undocumented `feature` of up to 8 minute random delay.\n* **03.12.18:** - Fix silly bug resetting the duckdns token.\n* **02.12.18:** - Add dns validation support for ovh.\n* **20.11.18:** - Externalize reverse proxy confs to separate github repo `linuxserver/reverse-proxy-confs`, update baseimage packages during build\n* **19.11.18:** - Add php opcache package.\n* **12.11.18:** - Add support for duckdns wildcard certs via dns validation\n* **31.10.18:** - Add various preset proxy confs and fix others (thanks @nemchik and @hijxf)\n* **02.10.18:** - Fix fail2ban instructions and logrotate conf\n* **11.09.18:** - Add various preset proxy confs and fix others (thanks @nemchik and @LeoVerto)\n* **04.09.18:** - Linting fixes.\n* **30.08.18:** - Add support for ldap auth, add proxy confs for bazarr, couchpotato, headphones, lidarr and plex subfolder (thanks @nemchik and @jedahan)\n* **21.08.18:** - Rebase to alpine 3.8, add info on search engine de-listing\n* **08.08.18:** - Add subdomain proxy conf for plex, update emby proxy confs\n* **25.07.18:** - Add subdomain proxy conf for syncthing\n* **23.07.18:** - Remove backwards compatibility and set default validation method to http. Update portainer proxy config to fix websockets. Add unifi proxy conf.\n* **31.05.18:** - Update ssl.conf and proxy.conf for tighter security (thanks @nemchik)\n* **30.05.18:** - Add reverse proxy configs for jackett, monitorr, nzbget, nzbhydra, organizr, portainer and transmission (thanks @nemchik)\n* **18.05.18:** - Add more info on certs and unraid reverse proxy config\n* **11.05.18:** - Add php pgsql support\n* **24.04.18:** - Auto generate a private key + fullchain bundle pem that is needed by certain apps\n* **20.04.18:** - Add standardized optional reverse proxy conf files\n* **19.04.18:** - Bind memcached to localhost only, add php7-sqlite3\n* **08.04.18:** - Fix renewal hooks\n* **29.03.18:** - Create pfx cert after renewal for dns validation (previous version only created it for http and tls, an oversight)\n* **29.03.18:** - Fix staging for v2 api\n* **13.03.18:** - Support for wildcard cert with dns validation added. Switched to v2 api for ACME.\n* **21.02.18:** - Reduce shellcheck directives by renaming secondary variables\n* **20.02.18:** - Sanitize variables, increase log verbosity\n* **01.02.18:** - Big changes. `VALIDATION` parameter added for choosing letsencrypt validation methods, including dns through official plugins. `HTTPVAL` is deprecated. `STAGING` parameter added for testing. Backwards compatibility for the short term. Since tls-sni is disabled by letsencrypt, most users will have to change their settings and adopt the new parameters within the next 90 days. Reorganized the nginx default config, split ssl settings into new ssl.conf\n* **13.01.18:** - Re-enable ipv6 due to update to fail2ban 0.10.1. Existing users can enable ipv6 by deleting `/config/fail2ban/action.d/iptables-common.local` and restarting the container after updating the image\n* **11.01.18:** - Halt the container if validation fails instead of a stop (so restart=always doesn't get users throttled with letsencrypt)\n* **10.01.18:** - Add option for http validation on port 80\n* **05.01.18:** - Rebase to alpine 3.7\n* **04.11.17:** - Add php7 soap module\n* **31.10.17:** - Add php7 exif and xmlreader modules\n* **25.09.17:** - Manage fail2ban via s6\n* **24.09.17:** - Add memcached service\n* **01.09.17:** - `--privileged` is no longer required as long as `--cap-add=NET_ADMIN` is added, instructions modified accordingly, disabled fail2ban ipv6 actions due to requiring access to host kernel modules\n* **31.08.17:** - Add php7-phar\n* **14.07.17:** - Enable modules dynamically in nginx.conf\n* **06.07.17:** - Add support for multiple domains (thanks @oznu)\n* **22.06.17:** - Add various nginx modules and enable all modules in the default nginx.conf\n* **16.06.17:** - Update deprecated certbot option for https validation, make e-mail entry optional, update readme\n* **05.06.17:** - Add php7-bz2\n* **27.05.17:** - Rebase to alpine 3.6.\n* **03.05.17:** - Fix log permissions.\n* **18.04.17:** - Add php7-sockets, update fail2ban filter and action defaults\n* **27.02.17:** - Add php7-dom, php7-iconv and php7-pdo_sqlite\n* **21.02.17:** - Add php7-xml\n* **10.02.17:** - Switch to alpine 3.5 base and php7, add php zlib module and all nginx modules\n* **13.01.17:** - Add php5-ctype and php5-openssl\n* **04.01.17:** - Add php5-mysqli and php5-pdo_mysql\n* **22.11.16:** - Add gd and mcrypt packages\n* **21.11.16:** - Add curl package\n* **07.11.16:** - Initial Release\n","has_starred","hub_user","immutable_tags_settings",{"_71":11,"_72":73},"enabled","rules",[74],".*","is_automated","permissions",{"_78":17,"_79":11,"_80":11},"read","write","admin","user","storage_size",1008529984,"orgData","recentTags",[87],{"_88":40,"_89":90,"_91":92,"_93":94,"_95":96,"_46":114,"_115":90,"_116":29,"_117":52,"_53":118,"_119":120,"_121":105,"_122":114,"_123":62,"_124":17},"content_type","creator",101646,"full_size",94022099,"id",55179809,"images",[97],{"_98":99,"_100":101,"_102":103,"_104":105,"_106":107,"_108":109,"_110":103,"_111":-5,"_112":92,"_59":62,"_113":-5},"architecture","amd64","digest","sha256:613dc47747d2fcb9a46c16a6f0795a35ed30565f6e524e611b41eb39cafac505","features","","last_pulled","2026-09-23T19:40:59.758540403Z","last_pushed","2019-08-12T14:37:45Z","os","linux","os_features","os_version","size","variant","2019-08-12T14:37:44.292684Z","last_updater","last_updater_username","media_type","latest","repository",7096678,"tag_last_pulled","tag_last_pushed","tag_status","v2","sbxKitMetadata","isPotentialSpam","isHubSbxKitsEnabled","showSbxLogoOverride","sbxTrademarkText","displaySecurityMetadata","tagAttestations","tagsHaveAttestations",[],"routes/_layout.r.$namespace.$reponame.tags",{"_34":136,"_143":144,"_132":153,"_154":11},{"_36":137,"_38":138,"_41":42,"_43":44,"_45":11,"_46":47,"_48":49,"_50":139,"_53":31,"_28":29,"_54":55,"_56":40,"_57":58,"_59":60,"_61":62,"_63":-5,"_64":58,"_65":66,"_67":11,"_68":29,"_69":140,"_75":11,"_76":142,"_81":29,"_82":83},[],[40],[52],{"_71":11,"_72":141},[74],{"_78":17,"_79":11,"_80":11},"tags",{"_145":60,"_146":-5,"_147":-5,"_148":149},"count","next","previous","results",[150],{"_88":40,"_89":90,"_91":92,"_93":94,"_95":151,"_46":114,"_115":90,"_116":29,"_117":52,"_53":118,"_119":120,"_121":105,"_122":114,"_123":62,"_124":17},[152],{"_98":99,"_100":101,"_102":103,"_104":105,"_106":107,"_108":109,"_110":103,"_111":-5,"_112":92,"_59":62,"_113":-5},[],"canDeleteTags","actionData","errors"]

skyer/letsencrypt

Tags for skyer/letsencrypt