A reverse proxy can terminate TLS and forward traffic for many services. High sustained encrypted throughput and connection churn can move CPU and network from background resources to the primary bottleneck.
Users publishing multiple busy services or large file-transfer endpoints.متطلبات أجهزة Nginx Proxy Manager: المعالج وذاكرة الوصول العشوائي وحِمل الوكيل
تعرّف على متطلبات Nginx Proxy Manager من حيث المعالج والذاكرة العشوائية وقاعدة البيانات وTLS والشبكة، ثم اختر أجهزة ZimaOS المناسبة لأحمال الوكيل العكسي.
Nginx Proxy Manager requirements at a glance
Nginx Proxy Manager does not publish a numerical CPU or RAM minimum. Its current official setup can run as a single container with SQLite, exposing HTTP 80, HTTPS 443 and the admin UI on 81, or it can use an external MariaDB/MySQL/PostgreSQL database. For a home server, reverse-proxy traffic, TLS termination, logging, certificate operations and co-hosted services matter more than a fixed RAM number.
- CPU
- No official numerical minimum. CPU demand rises with TLS handshakes, encrypted throughput, compression/custom Nginx rules and concurrent proxy traffic.
- RAM
- No official numerical minimum. Community and third-party guides often suggest roughly 512 MB to 1 GB for small deployments, but those figures are not Nginx Proxy Manager requirements.
- Database
- SQLite is supported in the current single-container setup. MariaDB/MySQL and PostgreSQL are also supported when you prefer a separate database service.
- Storage
- Persist `/data` and `/etc/letsencrypt`. Storage needs are usually modest, but logs, certificates and database backups should not live on disposable container layers.
- Network
- Ports 80 and 443 carry public HTTP/HTTPS proxy traffic; port 81 is the admin UI. Real network demand follows the combined traffic of all proxied services.
- Best Zima starting point
- ZimaBoard 2 832 is already more than sufficient for a typical home reverse proxy. Move up for a larger self-hosted stack, very high local traffic or broader storage/network needs—not because the NPM UI itself is heavy.
From official requirements to the right setup
Size Nginx Proxy Manager from traffic and architecture, not from the number of proxy-host rows in the UI.
-
Official requirements
Start with the current official deployment model: one NPM container with SQLite is valid and keeps `/data` plus `/etc/letsencrypt` persistent. A separate database is optional, not mandatory.
-
Confirm your needs
Estimate combined HTTP/HTTPS throughput, TLS termination and concurrent connections for the services behind the proxy. Nginx itself is designed for reverse proxy and load-balancing work, so network/TLS load is more meaningful than idle UI memory.
-
Leave room to grow
Choose the database topology. SQLite simplifies a small single-host deployment; MariaDB/MySQL/PostgreSQL add another service and therefore another RAM/CPU/backup dependency.
-
Run it on ZimaOS
Install Nginx Proxy Manager from ZimaOS, configure representative proxy hosts and certificates, then observe CPU, memory, network and log growth during the busiest real traffic period before deciding whether to upgrade hardware.
Check every playback client
- Number of public proxy hosts
- Peak HTTP/HTTPS throughput
- Concurrent TLS connections and handshakes
- WebSocket/stream proxy usage
- SQLite versus external database
- Certificate count and renewal operations
- Access/error log retention
- Other ZimaOS services sharing CPU and network
Official minimum requirements
The current Nginx Proxy Manager documentation publishes ports, persistent volumes, database options and supported deployment patterns, but no numerical host CPU or RAM minimum.
Treat 512 MB or 1 GB figures from community/VPS tutorials only as small-deployment anecdotes. For ZimaOS, the practical baseline is a reliable always-on host with enough CPU for TLS, enough RAM for NPM plus its database choice, and enough network capacity for the proxied services.
| Requirement | Official minimum | What this supports |
|---|---|---|
| CPU | No numerical official minimum | The current official setup guide does not specify a core count or clock speed. |
| RAM | No numerical official minimum | The current official setup guide does not specify a memory floor. |
| Default/simple database | SQLite supported | The current single-container example stores the SQLite DB under `/data`. |
| External database options | MariaDB/MySQL or PostgreSQL | Using an external database adds its own container/service resource requirements. |
| Ports | 80 HTTP, 443 HTTPS, 81 admin UI | Additional stream ports can be exposed when needed. |
| Persistent storage | /data and /etc/letsencrypt | These paths hold application state and certificate data and should be backed up. |
When to upgrade your hardware
Upgrade when proxy traffic or the surrounding network stack creates measurable pressure.
TLS and proxy throughput become sustained
The proxy stack adds a separate database and more network services
Logs, certificates and backups outgrow tiny app storage
MariaDB/PostgreSQL, DNS, authentication, monitoring and security tools all add memory and CPU even if NPM itself remains light.
Larger homelabs and small-office self-hosting stacks.NPM persists application state and Let's Encrypt data. Larger log retention and backup history can make application storage reliability more important than raw CPU.
Long-running deployments with many hosts and certificates.Plan hardware growth with confidence
Scale NPM by keeping state persistent and separating network throughput from application overhead.
Use SQLite for a simple single-host deployment
The current official setup supports SQLite directly in the NPM container, reducing the number of services that must be maintained.
This is a good fit for a small ZimaOS reverse-proxy host.Use an external database only when the architecture needs it
MariaDB/MySQL/PostgreSQL can suit larger operational preferences, but they add their own memory, storage and backup needs.
Leave extra RAM and reliable persistent storage for the database container.Keep upstream containers on a private Docker network
NPM's advanced configuration recommends a shared Docker network so upstream service ports do not need to be exposed on every host interface.
This improves network architecture without requiring more CPU.Upgrade networking for the traffic you actually proxy
NPM cannot make a slow WAN, disk or upstream application faster. Faster 2.5GbE/10GbE matters when large local or internet-facing transfers genuinely pass through the proxy.
Choose network capacity from aggregate proxied traffic rather than app RAM usage.Can it run on ZimaOS?
Nginx Proxy Manager is currently available in the ZimaOS App Store and fits a central reverse-proxy role.
Install Nginx Proxy Manager from the ZimaOS App Store
The current ZimaOS listing provides NPM as a networking app for managing multiple proxied services.
Open Nginx Proxy Manager in the ZimaOS App StorePersist data and certificates
Keep `/data` and `/etc/letsencrypt` persistent so proxy definitions, users and certificate state survive container updates.
Read the official NPM setup guideUse private Docker networking for local upstreams
NPM's official advanced guide shows how a shared Docker network can avoid exposing upstream application ports to the whole host network.
Read NPM advanced configurationChoose Zima hardware for Nginx Proxy Manager
NPM itself is light. Choose the host from aggregate proxy traffic and the other services it protects and publishes.
Is NPM mainly a home reverse proxy, or part of a larger high-traffic self-hosting stack?
Home/small-office reverse proxy
Current ZimaBoard 2 resources provide substantial headroom for NPM, SQLite and several lightweight network services.
- Personal reverse proxyZimaBoard 2 832
- More network/security apps and service headroomZimaBoard 2 1664
Large self-hosted stack or storage-heavy proxy workflows
Move up for overall application capacity, integrated storage and faster networking.
- Multi-drive all-in-one serverZimaCube 2 Standard
- High local throughput and 10GbE workflowsZimaCube 2 Pro
There is no official NPM CPU/RAM minimum and no universal request-per-second guarantee. TLS versions, ciphers, upstream response size, logging, database topology and network speed can materially change results.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | A home Nginx Proxy Manager host with SQLite and several proxied services. | TLS termination, certificate management and ordinary home-server traffic. |
|
Very high sustained encrypted traffic or a much larger co-hosted stack can justify additional compute/network headroom. | Get Now |
| ZimaBoard 2 1664 | NPM plus DNS, VPN, monitoring and more containers. | A larger always-on networking and self-hosting stack. |
|
Extra RAM benefits the whole stack; NPM does not require 16 GB. | Get Now |
| ZimaCube 2 Standard | An all-in-one NAS/self-hosting server where NPM fronts many local services. | Proxying a larger multi-drive service stack. |
|
Choose it for storage/application consolidation, not because NPM needs a Core i3. | Get Now |
| ZimaCube 2 Pro | A high-throughput self-hosted platform with 10GbE local workflows. | Large file services, many containers and faster internal traffic behind NPM. |
|
10GbE is useful only when upstreams, clients and traffic volumes can use it. | Get Now |
What the Press Says
Highlights from trusted reviewers worldwide.
“ZimaCube 2: Not just another NAS, tested with 25TB storage, local AI agents, 4K transcoding, and real homelab workflows.”Read full review
“The ZimaBoard 2 is a compact x86 server board that can be turned into a mini NAS, home server, media box, or self-hosting hub.”Read full review
“ZimaCube 2: A modern, high-performance NAS with plenty of room to grow—built for users who want more than basic storage.”Read full review
“Coverage focused on ZimaCube 2's open hardware foundation, no monthly fee, and self-hosting flexibility.”Read full review
Loved by the Community
Stories and reviews from people who build with Zima every day.
★★★★★
Zima Blade Little yet Powerful
Maybe I am not digital natives but I live with PCs since 12 years old in 1984 when IBM PC clone come to my home. Many years have passed and many operating system I've tried. For me Zima blade and CasaOS was a quantum leap for home PC enthusiast and server lab machine to make me stay curious and relevant for this era.
★★★★★
Very good!!
I use ZimaCube Pro as 5th Proxmox cluster node. It runs several VMs and containers, including a VM with GPU passthrough to run a self-hosted LLM. A specific LXC container runs a Samba server for NAS capabilities using four of six RAID 6 SATA HDDs with ZFS.
★★★★★
Great innovation for mini server!
It is very useful and makes a powerful mini server for many purposes, including university and college students in engineering and electronics. Thank you so much for making this server.
★★★★★
Avaliação ZimaBoard 2
Construí um servidor de uso pessoal. O desempenho está muito bom e funciona perfeitamente onde quer que eu esteja. A surpresa é não dependermos de grandes estruturas para termos nosso próprio servidor de dados. Como iniciante, estou gostando bastante do ZimaOS, pois ele é simples e eficiente.
Frequently asked questions
These answers separate official NPM deployment requirements from community sizing estimates.
How much RAM does Nginx Proxy Manager need?
Nginx Proxy Manager does not publish an official RAM minimum. Community and third-party guides commonly mention roughly 512 MB to 1 GB for small installations, but treat those as deployment examples rather than a guaranteed requirement.
How many CPU cores does Nginx Proxy Manager need?
There is no official core-count minimum. A small home proxy is light, while high TLS/connection throughput can make CPU more important.
Does Nginx Proxy Manager require MariaDB?
No. The current official setup supports SQLite directly. MariaDB/MySQL and PostgreSQL are optional external database choices.
Can ZimaBoard 2 832 run Nginx Proxy Manager?
Yes. Its Intel N150, 8 GB RAM and dual 2.5GbE provide substantial headroom for a normal home reverse-proxy workload.
Does Nginx Proxy Manager need a GPU?
No. Reverse proxying, TLS, certificates and database work do not require a dedicated GPU.
What ports does Nginx Proxy Manager use?
The current official example exposes 80 for HTTP, 443 for HTTPS and 81 for the admin interface, with additional stream ports exposed only when needed.
When should I choose ZimaCube 2 for NPM?
Choose ZimaCube 2 when NPM fronts a larger multi-drive application stack, or when the overall server needs more compute/storage/network headroom. NPM alone rarely justifies it.
Should upstream Docker apps expose their ports publicly?
Not necessarily. NPM's advanced guide recommends a shared Docker network for local upstream services so their ports do not need to be published on all host interfaces.
What sources and further reading informed this Nginx Proxy Manager hardware guide?
The official NPM setup and advanced-configuration pages establish current ports, persistence, SQLite/external database options and Docker networking. The ZimaOS App Store confirms the current packaged app. Community and third-party SERP results provide 512 MB–1 GB examples, but they are explicitly treated as anecdotal or provider guidance rather than official hardware requirements.
