Failed to renew certification npm-1 with error: urn:ietf:params:acme:error:malformed :: The request message was malformed :: No such authorization

[kmanwar89]

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 After bringing up a container with the latest NPM release (2.10.3), and taking no other action while observing the docker-compose logs, I observed the error message text below:

npm  | 2023-06-06T23:34:27.236480542Z [6/6/2023] [11:34:27 PM] [SSL      ] › ✖  error     Error: Command failed: certbot renew --non-interactive --quiet --config "/etc/letsencrypt.ini" --work-dir "/tmp/letsencrypt-lib" --logs-dir "/tmp/letsencrypt-log" --preferred-challenges "dns,http" --disable-hook-validation  
npm  | 2023-06-06T23:34:27.236526744Z Failed to renew certificate npm-1 with error: urn:ietf:params:acme:error:malformed :: The request message was malformed :: No such authorization
npm  | 2023-06-06T23:34:27.236535271Z All renewals failed. The following certificates could not be renewed:
npm  | 2023-06-06T23:34:27.236541895Z   /etc/letsencrypt/live/npm-1/fullchain.pem (failure)
npm  | 2023-06-06T23:34:27.236548518Z 1 renew failure(s), 0 parse failure(s)
npm  | 2023-06-06T23:34:27.236554770Z 
npm  | 2023-06-06T23:34:27.236560993Z     at ChildProcess.exithandler (node:child_process:402:12)
npm  | 2023-06-06T23:34:27.236567405Z     at ChildProcess.emit (node:events:513:28)
npm  | 2023-06-06T23:34:27.236573888Z     at maybeClose (node:internal/child_process:1100:16)
npm  | 2023-06-06T23:34:27.236580772Z     at Process.ChildProcess._handle.onexit (node:internal/child_process:304:5)

The full, timestamped logs are attached to this issue

Nginx Proxy Manager Version Just upgraded to 2.10.3; error was not present in 2.9.19

To Reproduce Steps to reproduce the behavior:

1. Remove all traces of existing NPM container (docker compose --rmi all -v)
2. Set the compose file to the latest version of NPM (2.10.3)
3. Prune any existing images with docker image prune -f
4. Bring up the container with docker compose up --d
5. Monitor the compose logs using docker compose logs --follow -t
6. Wait a few seconds and the logs will present themselves

Expected behavior This error message should not be present in the logs

Screenshots N/A - logs directly attached

NPM error 6 JUN 2023.txt

Operating System Ubuntu Server 22.04.2 LTS

Additional context There's not much additional context to add - I saw there was a new release and, after backing up my data and letsencrypt folder, decided to update. I monitored the compose logs and after a few minutes, the errors in the attached logs appeared. It's unclear if there's any impact caused by these, or if they are cosmetic, but the "All renewals failed" message is a bit concerning.

No such logs were ever present in 2.9.19 and nothing has changed in my environment other than upgrading NPM today - I did not modify any other containers on my machine.

[danmed]

You'll need to go back to 2.10.2.. this error has been mentioned a lot but the conversation around it is over my head.. something about an incorrect --user argument in the pip install command.. I'm not really sure why it's not yet been fixed.

[github-actions[bot]]

Issue is now considered stale. If you want to keep it open, please comment :+1:

[kmanwar89]

6+ months later, maintainers have still not commented on what is causing this issue. Commenting to keep it open.

[github-actions[bot]]

Issue is now considered stale. If you want to keep it open, please comment :+1: