[GH-ISSUE #2196] Unable to create certificates #1571

New issue

Closed

opened 2026-02-26 07:31:36 +03:00 by kerem · 1 comment

kerem commented

2026-02-26 07:31:36 +03:00

Owner

Originally created by @amrap030 on GitHub (Aug 11, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2196

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
I am trying to add a new proxy host with the domain name: vue4.amrap030.duckdns.org. (See following config)

Now when I try to access this domein via the browser, everything works fine and I can enter the application behind this domain, but only via plain http.

When I try to add a SSL certificate, I am getting an internal error with the following logs:

Certbot failed to authenticate some domains (authenticator: webroot). The Certificate Authority reported these problems:
  Domain: vue4.amrap030.duckdns.org
  Type:   unauthorized
  Detail: 130.61.125.198: Invalid response from http://vue4.amrap030.duckdns.org/.well-known/acme-challenge/89Uw3KIs4vcCAS1oWMjBMSikn3Kqxtszg6TqmxDEOms: 404

Hint: The Certificate Authority failed to download the temporary challenge files created by Certbot. Ensure that the listed domains serve their content from the provided --webroot-path/-w and that files created there can be downloaded from the internet.

Do you have any idea how to fix this?

Nginx Proxy Manager Version
v2.9.18

Expected behavior
Successfull SSL certificate creation.

Operating System
Mac

Additional context
The vue application I am trying to access runs on the localhost and NPM runs with docker, that's why I use host.docker.internal for the proxying. But as I said, with HTTP I can access the application publicly.

Originally created by @amrap030 on GitHub (Aug 11, 2022). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2196 **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** I am trying to add a new proxy host with the domain name: `vue4.amrap030.duckdns.org`. (See following config) <img width="492" alt="Bildschirmfoto 2022-08-11 um 18 03 43" src="https://user-images.githubusercontent.com/35061229/184178470-8a71ec51-2811-4e54-ac99-f45a6f922e2e.png"> Now when I try to access this domein via the browser, everything works fine and I can enter the application behind this domain, but only via plain http. When I try to add a SSL certificate, I am getting an internal error with the following logs: ``` Certbot failed to authenticate some domains (authenticator: webroot). The Certificate Authority reported these problems: Domain: vue4.amrap030.duckdns.org Type: unauthorized Detail: 130.61.125.198: Invalid response from http://vue4.amrap030.duckdns.org/.well-known/acme-challenge/89Uw3KIs4vcCAS1oWMjBMSikn3Kqxtszg6TqmxDEOms: 404 Hint: The Certificate Authority failed to download the temporary challenge files created by Certbot. Ensure that the listed domains serve their content from the provided --webroot-path/-w and that files created there can be downloaded from the internet. ``` Do you have any idea how to fix this? **Nginx Proxy Manager Version** v2.9.18 **Expected behavior** Successfull SSL certificate creation. **Operating System** Mac **Additional context** The vue application I am trying to access runs on the localhost and NPM runs with docker, that's why I use `host.docker.internal` for the proxying. But as I said, with HTTP I can access the application publicly.

kerem

2026-02-26 07:31:36 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-26 07:31:37 +03:00

Author

Owner

@amrap030 commented on GitHub (Aug 11, 2022):

I fixed it with the toggle Use DNS Challenge.

@amrap030 commented on GitHub (Aug 11, 2022): I fixed it with the toggle `Use DNS Challenge`.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/nginx-proxy-manager-NginxProxyManager#1571

No description provided.

Rows
Columns