Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No peer certificate for SSL resulting in UNRECOGNIZED NAME error #3752

Open
krojew opened this issue May 14, 2024 · 0 comments
Open

No peer certificate for SSL resulting in UNRECOGNIZED NAME error #3752

krojew opened this issue May 14, 2024 · 0 comments
Labels

Comments

@krojew
Copy link

krojew commented May 14, 2024

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 installing NPM using the official instructions and setting up a certificate for domain x.y.com, https connections do not work at all, including the congratulations page. Trying to access the congratulations page via https results in a UNRECOGNIZED NAME error in the browser. Inspecting the certificate via openssl results in:

openssl s_client -showcerts -connect x.y.com:443
CONNECTED(00000003)
40B7D2AD887F0000:error:0A000458:SSL routines:ssl3_read_bytes:tlsv1 unrecognized name:../ssl/record/rec_layer_s3.c:1586:SSL alert number 112
---
no peer certificate available
---
No client certificate CA names sent
---
SSL handshake has read 7 bytes and written 329 bytes
Verification: OK
---
New, (NONE), Cipher is (NONE)
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
Early data was not sent
Verify return code: 0 (ok)
---

Nginx Proxy Manager Version

2.11.2

To Reproduce
Steps to reproduce the behavior:

  1. Install using the quick setup instructions from the README file.
  2. In the portal, add SSL certificate for chosen domain. Using cloudflare DNS challenge, if that makes a difference.
  3. Connect to chosen domain via https. Note the error.

Expected behavior

Congratulations page, as visible via plain HTTP.

Screenshots

n/a

Operating System

TrueNAS custom app deployment.

Additional context

Plain HTTP works. The domain used seems to not be the problem - tried on two different ones.

@krojew krojew added the bug label May 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant