Skip to main content
r/nginxproxymanager icon

r/nginxproxymanager

8.9K members
4 online

All my proxies redirect to my TrueNAS Scale dashboard. • All my proxies redirect to my TrueNAS Scale dashboard.

As the title says, whenever I make a proxy, it redirects to my main TrueNAS Scale dashboard, even if I change the port.

I followed this tutorial: https://www.youtube.com/watch?v=qlcVx-k-02E&t=489s&ab_channel=Wolfgang%27sChannel, except I am using Cloudflare instead.

I don’t know why it’s not working.

these are my DNS records: https://imgur.com/a/E5enmfP


BISSELL® portable deep cleaners tackle messes anywhere. From quick cleanups to deep stains, there’s a powerful cleaner for every spill, splash, and oops.
media poster


NPM to Cloudflare not working only on new proxy hosts? • NPM to Cloudflare not working only on new proxy hosts?

Hey I've been trying to add a new service and I've been getting a 525 SSL Handshake Error, but only on new subdomains I add. I have 6 other subdomains that work perfectly fine with the Cloudflare cert. When I do the curl command on the new subdomain as shown in the cloudflare troubleshooting I get this error

* ALPN: curl offers h2,http/1.1
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
*  CAfile: none
*  CApath: /etc/ssl/certs
* TLSv1.3 (IN), TLS alert, unrecognized name (624):
* OpenSSL/1.1.1v: error:14094458:SSL routines:ssl3_read_bytes:tlsv1 unrecognized name
* Closing connection

When I use the same curl command on on a older subdomain that is using the same cloudflare ssl certs on NPM, it shows this.

* ALPN: curl offers h2,http/1.1
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
*  CAfile: none
*  CApath: /etc/ssl/certs
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (OUT), TLS alert, unknown CA (560):
* SSL certificate problem: unable to get local issuer certificate
* Closing connection

I've tried using multiple services to see if that was maybe the issue but they all resulted in the 525 error.

I have cloudflare set to Full currently but for the past months it's been on Full (Strict)

Any help would be appreciated cause idk what is going on.


LetsEncrypt Azure DNS challenges failing suddenly, but only for wildcard certs. • LetsEncrypt Azure DNS challenges failing suddenly, but only for wildcard certs.

Been using nginx proxy manager with letsencrypt dns-01 challenges for a while now. All worked smoothly for a year or more. Yesterday my wildcard certificate expired and wasn't automatically renewed. When I renew manually I see the _acme-challenge txt record created in my zone but the error that comes back is "some challenges have failed". strangely, if i create a new record for {host}.domain.com, it is successful using the same zone, same service principal, same secret, etc. I tried increasing the timeout to 6 minutes without success. I also use Key Vault Acmebot to issue the same wildcard certificates, again using the same service principal, secret, etc, and it operates without error. Any ideas what the issue might be or where to look next?

edit: letsdebug.net shows all ok for my domain