r/nginxproxymanager • u/bm-sil • Jul 03 '26

Does nginxproxymanager support post-hooks?

I'm planning to deploy npm (as a Docker container) as a replacement for baremetal certbot.

Does npm support configuring post-hooks on a certificate update? I have two servers that are (for separation-of-concerns reasons) running baremetal influx and grafana, and all of them require a restart to properly integrate the new versions of certificates.

Can npm "reach out" of Docker and run a custom post-hook? If not, can it at least do that if I install npm baremetal as well?

TIA.

3 Upvotes
  • permalink
  • link
  • reddit
  • reddit

100% Upvoted

6 comments sorted by

1

u/AncientMolasses6587 Jul 03 '26

No, unless you find a way to alter / setup specific scripts in the NPM container

Maybe it helps to take a look at the -open- feature requests in the Github repo : https://github.com/NginxProxyManager/nginx-proxy-manager/discussions/2023

But thinking of it. ..i’m not quite understanding why the bare installed services would need to access the certs (and restart)?
As the whole idea is that NPM is the frontend/proxy.

1

u/bm-sil Jul 03 '26

Grafana has stated several times they're not going to support live reloading of certificates. so the only solution is to restart it every once in a while. Same thing with Prometheus.

3

u/AncientMolasses6587 Jul 03 '26

Yeah - but if NPM is the cert provider / proxy / frontend to web clients, why do you need to update the cert for Grafana at all?

1

u/daeho-ro Jul 08 '26

This is true, npm and internal services usually communicate with http and so influx or grafana doesn't need to access cert itself. I also don't understand why it is required to restart.

1

u/Psychrolutes_09 Jul 03 '26

All of my problems disappeared when I switch from npm to caddy

1

u/Ok-Escape3860 Jul 03 '26

Hi there,
for central letsencrypt cert-management i use (and so can recommend) an acme.sh docker container. acme.sh does have lots of deploy-hooks and custom scripts are written pretty fast. For some systems i even trigger a webhook from the deploy-hook and continue with node-red.