Skip to content

Error with DNS Challenge (Plesk) – xmltodict not defined #4673

@lberrezoug

Description

@lberrezoug

Checklist

  • Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
    • Yes
  • Are you sure you're not using someone else's docker image?
    • Yes
  • Have you searched for similar issues (both open and closed)?
    • Yes

Describe the bug

When trying to issue an SSL certificate using DNS Challenge with Plesk in Nginx Proxy Manager, the process fails with the following error:
`CommandError: Saving debug log to /tmp/letsencrypt-log/letsencrypt.log
Unexpected error determining zone identifier for domain.tld: name 'xmltodict' is not defined
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /tmp/letsencrypt-log/letsencrypt.log or re-run Certbot with -v for more details.

at /app/lib/utils.js:16:13
at ChildProcess.exithandler (node:child_process:430:5)
at ChildProcess.emit (node:events:524:28)
at maybeClose (node:internal/child_process:1104:16)
at ChildProcess._handle.onexit (node:internal/child_process:304:5)`

Nginx Proxy Manager Version

2.12.6

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'Add a new SSL certificate using the DNS Challenge method with the Plesk DNS provider'
  2. Click on 'save'
  3. See error

Expected behavior

A certificate should be issued successfully using the DNS challenge with Plesk.

Screenshots

Image

Operating System

The system is running on Rocky Linux 9.3. Nginx Proxy Manager is deployed using Docker.

Additional context

No

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      pFad - Phonifier reborn

      Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

      Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


      Alternative Proxies:

      Alternative Proxy

      pFad Proxy

      pFad v3 Proxy

      pFad v4 Proxy