Skip to main content

certbot-dns-regru

Reg.ru DNS authenticator plugin for Certbot

English | Русский

An authenticator plugin for certbot to support Let's Encrypt DNS challenges (dns-01) for domains managed by the nameservers of Reg.ru.

Huge thanks to @free2er for creating initial version

Requirements

  • certbot (>=0.21.1)

For older Ubuntu distributions check out this PPA: ppa:certbot/certbot

Installation

  1. First install the plugin:

    sudo pip install certbot-dns-regru
    
  2. Configure it with your Reg.ru Credentials:

    sudo nano /etc/letsencrypt/regru.ini
    

    Add provider configuration. It is strongly advised to use API password and not your regular password (can be set here)

    dns_regru_username=<USERNAME>
    dns_regru_password=<PASSWORD>
    

    Reg.ru now requires client certificate (mTLS) authentication for its API. If you have enabled SSL authentication for the API, provide the paths to your client certificate and key:

    dns_regru_cert=/path/to/client.crt
    dns_regru_key=/path/to/client.key
    

    dns_regru_cert may also point to a single PEM file containing both the certificate and the private key (in which case dns_regru_key is optional).

    If you use reg.ru's service to manage external domains - no need to worry, plugin tries both plain domain and "servtype":"srv_dns_both"

  3. Make sure the file is only readable by root! Otherwise all your domains might be in danger:

    sudo chmod 0600 /etc/letsencrypt/regru.ini
    

Usage

Request new certificates via a certbot invocation like this (adjust paths as needed):

Linux:

sudo certbot certonly \
   --authenticator dns-regru \
   --dns-regru-credentials /etc/letsencrypt/regru.ini \
   --dns-regru-propagation-seconds 180 \
   -d sub.domain.tld -d '*.wildcard.tld'

Windows (PowerShell):

certbot certonly \
   --authenticator dns-regru \
   --dns-regru-credentials C:\path\to\regru.ini \
   --dns-regru-propagation-seconds 180 \
   -d sub.domain.tld -d '*.wildcard.tld'
  • Note that shell might try to resolve wildcard subdomain (*), you should put in in parentheses

Renewals will automatically be performed using the same authenticator and credentials by certbot.

See also certbot --help certbot-dns-regru for further information.

SWAG

To use this plugin with docker-swag you need to follow their guide

Add the following environment variables to your container:

DOCKER_MODS=linuxserver/mods:universal-package-install
INSTALL_PIP_PACKAGES=certbot-dns-regru

Then modify /config/dns-conf/regru.ini and provide credentials

Removal

   sudo pip uninstall certbot-dns-regru

Metadata

Release files for certbot-dns-regru 1.2.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for certbot-dns-regru 1.2.0
File Size Uploaded Provenance Actions
certbot_dns_regru-1.2.0.tar.gz 9.9 kB Without provenance Details for certbot_dns_regru-1.2.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for certbot-dns-regru 1.2.0
File Interpreter ABI Platform Actions
certbot_dns_regru-1.2.0-py3-none-any.whl Python 3 none any Details for certbot_dns_regru-1.2.0-py3-none-any.whl

Total release size: 20.8 kB

Release files / certbot_dns_regru-1.2.0.tar.gz

Download URL certbot_dns_regru-1.2.0.tar.gz
Size 9.9 kB
Tags Source
SHA-256 checksum
How to use checksums
35354ec926c26cd37bc226dcb78dc53250bca93a5635cf023953947ede23ff9a
BLAKE2b-256 checksum
How to use checksums
4eaefcbe146b9faf34ae561986fce7fce66a90af32d7c62fe67727ff8d194aca
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.12.3

Release files / certbot_dns_regru-1.2.0-py3-none-any.whl

Download URL certbot_dns_regru-1.2.0-py3-none-any.whl
Size 10.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
e59937bf20e5f3d585915eaf74b03c78824c23a5a993077f2118da5072e1db23
BLAKE2b-256 checksum
How to use checksums
c460320a1609147c2f5d20de6088ffe1d1b2718f1e0b138b81ac4cdf7e2ee3c0
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.12.3

Security for certbot-dns-regru 1.2.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page