Note: In the past certs deleted in the UI (custom and certbot certs) were NOT deleted on the disk, which means that they may still be renewed by certbot, see how to delete them below the changelog
What's Changed
- change: X_FRAME_OPTIONS now uses sameorigin as default instead of deny
- improve: deleting custom certs will also remove them from the disk
- fix: fancyindex was broken
- fix: #1629
- dep updates
How to remove certificates from the disk which were previously deleted in the ui (path relative to the path where you mounted the /data folder)
- Make sure that you don't accidentally delete a cert which is still in use, compare the IDs and make a backup!
- custom certs:
- cert saved in
tls/custom/npm-[id] - stapling file (if enabled) at
tls/custom/npm-[id].der - deleting the folder and the stapling file will remove the cert.
- cert saved in
- certbot certs:
- cert is saved in
tls/certbot/live/npm-[id]andtls/certbot/archive/npm-[id] - stapling file (if enabled) at
tls/certbot/live/npm-[id].der - renewal config at:
tls/certbot/renewal/npm-[id].conf - deleting the folders, the stapling file and the renewal config will remove the cert.
- NOTE: It is important that you also delete the renewal config, otherwise certbot may still renew/recreates the cert after deleting the folders!
- cert is saved in
- Why doesn't NPMplus do this itself?
- in the past it was possible to delete certs from the UI which were still in use (still possible for certs only used in streams) and may still are, deleting them automatically may break some instances
How to update
- read the changes above
- repull the docker image
- apply possible changes that maybe effect you from above to your compose.yaml
- redeploy the compose stack
- report any issues you may find
Full Changelog: 2025-03-20-r1...2025-03-21-r1