Skip to content

RFC2136 DNS updates using CertifyTheWeb Hub docker container #756

Description

@kbekus

hi there,

I'm trying to evaluate the CertifyTheWeb Management Hub docker container and I'm having an issue. I have the docker container running on a minimal Debian 13 installation using a docker compose file:
name: certify-management-hub services: certify-hubservice: image: docker.io/certifytheweb/management-hub:latest ports: - "8080:8080" volumes: - ./certifydata:/usr/share/certify/ - /usr/bin/nsupdate:/usr/bin/nsupdate - /usr/lib/x86_64-linux-gnu/:/usr/lib/x86_64-linux-gnu/ restart: unless-stopped

I've needed to manually map an nsupdate binary and the library folder because the docker image doesn't contain nsupdate natively. This is fine, I can shell in to the container and run nsupdate and it seems to work OK. Now I've set up an Let's Encrypt certificate request with suitable details and when I test a retrieve I get the following:

RFC2136 with nsupdate as DNS API (using Posh-ACME) :: PowerShell Execution Mode: InProcess.
PowerShell Host: Core 7.6.5
Error: nsupdate returned non-zero exit code which indicates failure. Check -Verbose output for details. at Send-DynamicTXTUpdate, /app/Scripts/DNS/PoshACME/Plugins/RFC2136.ps1: line 319
at Add-DnsTxt, /app/Scripts/DNS/PoshACME/Plugins/RFC2136.ps1: line 64
at , : line 44

at this point I'm not sure where to look and would love some guidance. Thanks in advance.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions