NPM Plus sometimes gives wildcard dummy certificate instead of cerbot's #3183
-
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 8 replies
-
|
so the issue only appears when using local dns rewrites? |
Beta Was this translation helpful? Give feedback.
-
|
Also started happening to me as well, haven't looked too deep into it yet, but I keep my public facing subdomains on a separate port with forwarding from my router like this: Works perfectly fine from cloudflare with proxy on and off, but local connections get the dummy cert. Also using Bitwarden lol. Weirdly enough, it starts working fine when I access an internal subdomain at the same time, which is running default on 443. My blind guess is that it might be some nginx ordering jank, since putting in the custom config from npm puts it at the bottom of the conf file, but I'm pretty sure that shouldn't matter for defining a listener. Not sure if you have the same setup or if this is a deeper issue somewhere else. |
Beta Was this translation helpful? Give feedback.
-
|
Also seeing this with porkbun dns certificate, the cert worked fine in zoraxy but I had to switch to npm due to the headscale and matrix header issues. Both firefox and chromium show the same certificate issue, and curl -v shows the following:
|
Beta Was this translation helpful? Give feedback.















what does the dns page in chrome://net-internals/#dns resolve your domain to?