NginxProxyManager / NginxProxyManager/nginx-proxy-manager

how to delete old domains already deleted that do not appear in the web interface

Open
#1,162 13 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug stale
Dominant language
TypeScript
Stars
34.2k
Forks
3.9k
Avg merge
21h 12m
Merged PRs (30d)
20

Description

Hello how to delete old domains ?

Failed to renew certificate npm-2 with error: Some challenges have failed.
proxy_v6 | All renewals failed. The following certificates could not be renewed:
proxy_v6 | /etc/letsencrypt/live/npm-1/fullchain.pem (failure)
proxy_v6 | /etc/letsencrypt/live/npm-10/fullchain.pem (failure)
proxy_v6 | /etc/letsencrypt/live/npm-11/fullchain.pem (failure)
proxy_v6 | /etc/letsencrypt/live/npm-12/fullchain.pem (failure)
proxy_v6 | /etc/letsencrypt/live/npm-13/fullchain.pem (failure)
proxy_v6 | /etc/letsencrypt/live/npm-2/fullchain.pem (failure)
proxy_v6 | 6 renew failure(s), 0 parse failure(s)

at ChildProcess.exithandler (node:child_process:326:12)
proxy_v6 | at ChildProcess.emit (node:events:369:20)
proxy_v6 | at maybeClose (node:internal/child_process:1067:16)
proxy_v6 | at Process.ChildProcess._handle.onexit (node:internal/child_process:301:5)
proxy_v6 | QueryBuilder#allowEager method is deprecated. You should use allowGraph instead. allowEager method will be removed in 3.0
proxy_v6 | `QueryBuilder

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The report names no source file, test, or entry point. Start by tracing how deleted domains remain associated with the listed certificate renewal paths, then verify the behavior through the web interface and renewal logs; done means obsolete domains no longer cause renewal failures or have a documented cleanup path.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, nginx, typescript
Domain
backend, devops, web-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.