Nginx Proxy Manager 2.16 Adds Built-In Log Viewer

Home › News › Linux › Nginx Proxy Manager 2.16
LINUXNGINX PROXYNETWORKING

Nginx Proxy Manager 2.16 Adds Built-In Log Viewer and Security Improvements

Nginx Proxy Manager 2.16 introduces an integrated log viewer, per-path access lists, networking improvements, security fixes, and updated certificate-management components.

KS
By Khurram ShahzadHybrid Cloud & Virtualization Engineer
📅 Sep 24, 2026
◷ 6 min read
Nginx Proxy Manager 2.16 adds a web-based logs viewer and expands access-control and infrastructure management capabilities. Image concept: VMoreCloud.

✓ Key Takeaways

  • Nginx Proxy Manager 2.16 adds a built-in Logs viewer to the web interface.
  • Per-path access lists provide more granular protection inside Proxy Host configurations.
  • The release adds reuseport support and updates the s6 overlay for Podman socket activation.
  • Several security and authentication improvements address token invalidation, 2FA QR-code generation, DNS credential handling, and an RCE-related change.
  • Certbot and DNS-plugin updates require special attention for environments using DNS-based certificate issuance.

What Is New in Nginx Proxy Manager 2.16?

Nginx Proxy Manager 2.16 is a new stable release of the open-source reverse-proxy management platform. The project provides a web interface for managing proxy hosts, redirects, streams, SSL certificates, access lists and related Nginx configuration without requiring administrators to edit every configuration file manually. citeturn0search5turn0search0

The 2.16 release focuses on easier troubleshooting, more granular access control, networking behavior, security hardening and certificate-management updates. The project currently lists the 2.16.x series as the supported stable branch for security updates. citeturn0search3

Built-In Log Viewer Arrives

The most visible change in Nginx Proxy Manager 2.16 is a new Logs viewer inside the administration interface. The project exposes log-related API functionality for system logs, Let’s Encrypt activity and per-host logs, allowing administrators to inspect operational information directly through the management interface. citeturn0search0turn0search6

This can simplify day-to-day troubleshooting. Instead of immediately opening a shell and searching files or container output, an administrator can start the investigation from the Nginx Proxy Manager UI.

Why it matters: Logs are often the first place to look when a reverse proxy returns an unexpected status code, a certificate request fails, or an upstream application stops responding. Putting log access closer to the configuration interface reduces context switching during troubleshooting.

Per-Path Access Lists

Version 2.16 also adds per-path access lists to the Proxy Host modal. Previously, access restrictions were commonly applied at the host level. Per-path rules provide a more granular option when different paths on the same hostname need different access controls. citeturn0search0

For example, an administrator could expose a public application while applying a separate access policy to a sensitive administrative path. The exact policy should still be tested against the application’s routing behavior and authentication requirements.

Security Improvements in Nginx Proxy Manager 2.16

Security is a significant part of this release. The official release notes list several security-related changes, including a change to escape ordering intended to prevent RCE, token invalidation after a password change, local generation of 2FA QR codes, improved private-key permission handling, and removal of DNS provider credentials from disk after Certbot completes. citeturn0search0

2FA improvement: The release notes state that Nginx Proxy Manager now generates QR codes for two-factor authentication locally, reducing the need to expose 2FA secrets to third-party QR-code services. citeturn0search0

The release also fixes permission and authorization-related behavior, including returning HTTP 403 for denied requests in the relevant PermissionError path instead of 404. Administrators should still treat the reverse proxy as an exposed security boundary and apply strong authentication, least-privilege access and secure TLS configuration.

Networking and Performance Changes

Nginx Proxy Manager 2.16 adds reuseport support. The project describes this as a change intended to improve performance and reduce packet drops. The practical effect depends on workload, traffic patterns, host networking and the underlying Nginx worker configuration. citeturn0search0

The release also updates the s6 overlay to support Podman socket activation and fixes IPv6 forwarding for Streams so valid Nginx upstream configurations are generated.

Certificate Management and Certbot Changes

Nginx Proxy Manager relies on Certbot for certificate automation, and version 2.16 updates that component. The release adds DNS plugins for LWS and Tencent Cloud EdgeOne and updates plugins for Timeweb Cloud, Websupport and Azure DNS. It also includes a fix for Tencent Cloud apex and wildcard certificate issuance. citeturn0search0

Upgrade warning for DNS validation: The project specifically warns that Certbot has been updated and some DNS plugins may no longer work as expected without dependency adjustments. If your Nginx Proxy Manager deployment depends on DNS-based Let’s Encrypt validation, test certificate renewal before treating the upgrade as routine. citeturn0search0

Configuration Troubleshooting Gets Easier

Several changes improve visibility when configuration operations fail. Failed Nginx configurations are now retained as .conf.err files, while another fix addresses cases where configuration changes did not take effect. Custom locations were also reorganized into a filterable list, which can help administrators working with larger proxy configurations. citeturn0search0

Other Changes in Version 2.16

  • Improved handling of insufficient private-key permissions.
  • Removal of broken sorting from Audit Logs.
  • Authenticated users visiting the login page are redirected to the dashboard.
  • DNS provider credentials are removed from disk after Certbot execution.
  • Configuration regeneration now uses the row’s own model and host type.
  • Additional DNS-provider integrations and updates are included.
  • New and updated translations include Azerbaijani, Ukrainian, Persian, German, Estonian and Turkish.

These changes are documented in the project’s v2.16.0 release notes. citeturn0search0

What Nginx Proxy Manager 2.16 Means for Administrators

For homelab, small-business and infrastructure administrators, the built-in log viewer is likely to be the most immediately noticeable operational improvement because troubleshooting can begin from the same interface used to configure proxy hosts.

Per-path access lists are more architectural: they give administrators another way to separate access requirements within a single hostname. The security and certificate-management changes are equally important because Nginx Proxy Manager is frequently placed directly in front of Internet-facing applications.

VMoreCloud technical perspective: Nginx Proxy Manager 2.16 is best understood as an operational and security-focused release rather than simply a UI update. The new log viewer improves visibility, while per-path access control and the security fixes provide additional tools for managing reverse-proxy deployments.

Upgrade Checklist

  1. Back up the Nginx Proxy Manager data and Let’s Encrypt data volumes.
  2. Record your current image tag and deployment configuration.
  3. Review any custom DNS plugins used for certificate issuance.
  4. Test certificate renewal if you depend on DNS-based validation.
  5. Review Proxy Host access lists and any custom locations after upgrading.
  6. Check the new Logs viewer for proxy, certificate and upstream errors.
  7. Verify HTTP/HTTPS access, streams, redirects and authentication workflows.
  8. For production systems, stage the upgrade before changing the live deployment.

How to Run Nginx Proxy Manager with Docker

The official documentation provides a Docker Compose deployment using the jc21/nginx-proxy-manager image. The standard setup exposes ports 80, 443 and 81, with persistent volumes for application data and Let’s Encrypt data. citeturn0search4

services: app: image: ‘docker.io/jc21/nginx-proxy-manager:2.16.0′ restart: unless-stopped ports: – ’80:80’ – ‘443:443′ – ’81:81’ volumes: – ./data:/data – ./letsencrypt:/etc/letsencrypt

For an existing deployment, follow the project’s current upgrade documentation and retain your persistent data volumes. Avoid changing multiple infrastructure variables simultaneously when troubleshooting an upgrade.

Availability and Official Documentation

Nginx Proxy Manager 2.16.0 is published as an official release, with Docker images including jc21/nginx-proxy-manager:2.16.0. The project’s security policy currently identifies 2.16.x as the supported stable series. citeturn0search0turn0search3

Nginx ProxyNginx Proxy ManagerNPM 2.16Reverse ProxyDockerLet’s EncryptLinuxNetworkingCybersecurity
KS
About the Author

Khurram Shahzad — Hybrid Cloud & Virtualization Engineer

Hybrid Cloud & Virtualization Engineer specializing in VMware, Azure, AWS, Windows Server, Microsoft 365, Linux, networking, backup & disaster recovery. I share practical guides, technical projects and infrastructure insights through VMoreCloud.

Editorial note: This article summarizes publicly documented Nginx Proxy Manager 2.16 changes and adds practical infrastructure context. VMoreCloud has not independently reproduced every upstream fix or benchmark described in the release notes. Test upgrades in a controlled environment before applying them to production systems.

Ads Blocker Image Powered by Code Help Pro

Ads Blocker Detected!!!

We have detected that you are using extensions to block ads. Please support us by disabling these ads blocker.

Powered By
Best Wordpress Adblock Detecting Plugin | CHP Adblock