NGINX-proxy manager support

jacksonm36

does this panel work behind npm?
also can we please have upload certficates or dns challenge method?

stefan

jacksonm36 We use standard nginx on the server, it handles the ssl, modsecurity rules and ssl for all domains that users add.

Using this one instead will beat the purpose, as OpenPanel does not know it exist and you would need to remove existing nginx on port 80 / 443, so you will actually remove a bunch of existing functionality: modsecurity waf, IP blocking per domain, /openpanel and /webmail links, custom nginx error pages, domain redirects, force https option, etc.

Also, since we let Docker manage ports for containers, you will need to edit proxy after each reboot 🙄

stefan

I will include an option to add custom certificate, expect it in the next update.

The DNS verification method also makes a lot of sence, I will make sure to add that one as well!

Would you prefer:
A: to have an option to set file upload/DNS method per domain.
B: or for it just to work automatically: example do DNS method if file upload fails.

Thank you for the suggestions. 👍

stefan

added an option to upload custom ssl, it will not be replaced by free certificate even after it expires. It needs to be manually renewed or deleted to generate a free Let'sEncrypt certificate.

Once again, thanks for the Idea to use DNS verification, Ive implemented that as well and managed to also fit remote DNS verification.

So there is an option for user to select provider per domain and set API Keys, and the panel will automatically add the record there.

For instance, for a domain using Cloudflare DNS, you can set the Cloudflare API key, allowing the TXT record to be automatically published there. Similarly, for another domain on the same account, you can set Google Domains and your Google API key, ensuring the record for that domain is posted there.

Will add more providers later.

I will push this to testing for the next version and if all is ok, will be available soon.

stefan

Not all tests are passing, a lot of new issues with nginx and existing installations that use certbot.

It will take a lot of time to make it backwards compatible, so for now we will have to delay the release of this feature. Maybe in some other versions when we have more time, or just add it to the premium version without any compatibility for existing installs..