The practical route is to run Pydio Cells on a Linux host with persistent storage and a MySQL-compatible database. For a first deployment, Docker gives you the quickest, most isolated setup; a native binary is a better fit when you want systemd and host-level control. Pydio Cells supplies its own web gateway, so a separate Apache or Nginx server is optional rather than mandatory.
Need a server to try this on? Antihost offers Linux VPS plans with NVMe storage, full root access and a 14-day free trial.
This guide covers hardware, databases, Docker and bare-metal installation, Raspberry Pi sizing, HTTPS and networking, backups, upgrades, and the failure modes that most often prevent a working login.
As an Amazon Associate I earn from qualifying purchases.
What Pydio Cells does
Pydio Cells is Pydio’s current self-hosted platform for document sharing and collaboration. It is written in Go, uses a microservice architecture, and is distributed as compiled binaries, a Docker image, and source code. Its feature set is aimed at organizations that need large-file transfer, granular security controls, and workflow automation while keeping the data and service under their own administration.
Self-hosting means you supply the compute, database, storage, network access, TLS configuration, monitoring, and backups. In return, you control where files live and how users authenticate. That trade-off is important: Cells is not a single executable that removes all operational work. It is an application service that must be sized, secured, and maintained like any other server software.
#1 Best Overall
- 【Advanced Home Data & Media Hub】For advanced home users who need phone backup, file storage, and centralized data management. Centralize family photos, 4K videos, movies, computer backups, and personal files in one place while running multiple apps for home entertainment and everyday data management. Suitable for households with growing digital libraries and multiple NAS use cases.
- 【Built for Creators, Media Servers & Advanced Apps】Powered by the Intel N100 Quad-Core CPU, 8GB DDR5 RAM, 2.5GbE networking, and dual M.2 NVMe slots, DXP2800 handles large files and heavier workloads with ease. Run Docker, virtual machines, and media server applications compatible with Plex—ideal for content creators, tech enthusiasts, and advanced home users managing 4K videos, RAW photos, personal media libraries, and multiple NAS apps.
- 【Up to 80TB for Growing Digital Libraries】 Supports up to 80TB of storage using two HDD bays and two M.2 NVMe SSD slots for family photos, movies, RAW photos, 4K videos, work files, and device backups. AI photo management supports recognition of people, objects, scenes, and locations, album organization, and duplicate photo detection. HDDs and SSDs are not included.
- 【AI-powered Home Surveillance】Turn DXP2800 into a centralized home surveillance hub by connecting compatible network cameras and storing recordings locally on your NAS. AI-powered features include Face Recognition, People Detection, and Pet Detection, helping advanced home users review important events more efficiently while managing home surveillance and personal data in one place.
- 【One data Center Across Your Devices】Keep files from desktops, laptops, phones, tablets, and other devices together instead of scattered across cloud accounts and external drives. Access, back up, organize, and share data across Windows, macOS, Android, iOS, web browsers, and compatible smart TVs—ideal for creators and advanced home users working across multiple devices.
Choose a host before installing
Baseline requirements
Pydio’s requirements guidance recommends an AMD 64-bit system or ARM in 32- or 64-bit form, with at least two CPU cores, 4 GB of RAM, and SSD storage. MySQL 5.7 or newer, or MariaDB 10.3 or newer, is required. MongoDB versions 5 through 7 are supported for selected services, but a MySQL-compatible database remains the core dependency for a normal installation.
| Component | Minimum or supported value | Practical implication |
|---|---|---|
| CPU | Two cores or more; AMD 64-bit or ARM 32/64-bit | Two cores can serve a small household or lab. More headroom is advisable for simultaneous uploads, previews, and indexing. |
| Memory | 4 GB RAM baseline | Leave memory for the operating system, database, Docker, and any reverse proxy or monitoring services. |
| Primary storage | SSD recommended | Use storage with enough capacity for files, versions, logs, and growth; keep backups on a separate device or system. |
| Database | MySQL 5.7+ or MariaDB 10.3+; MongoDB 5–7 for selected services | Create the database and account before running the setup wizard. |
| Open files | More than 2,048; 8,192 recommended for production | Raise the service user’s limit so many concurrent files and connections do not exhaust descriptors. |
Edition-specific sizing
The published minimums differ by edition. Cells Home lists two cores and 4 GB of RAM, while Enterprise lists four cores and 8 GB. These are minimum hardware figures, not performance guarantees. User count, file size, previews, synchronization clients, and workflow activity can all increase demand. Check the current licensing and edition terms on Pydio’s pricing page before committing to a production design.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Raspberry Pi, small server, or VPS?
| Platform | Best use | Advantages | Constraints |
|---|---|---|---|
| Raspberry Pi 4B (4 GB or more) | Home, learning, and small-scale deployments | Low power draw, ARM support, inexpensive local hosting | Limited CPU and memory headroom; storage and remote connectivity need careful planning |
| Small x86 Linux server | Households, clubs, and small teams | More CPU/RAM options, easier database and storage expansion | You manage hardware, updates, power, and network availability |
| Linux VPS | Users who need reliable internet reachability without maintaining hardware | Datacenter connectivity, snapshots or attached volumes, predictable remote access | Recurring hosting cost, provider dependence, and the need to secure an internet-facing server |
Pydio’s advanced deployment guidance documents Raspberry Pi use and suggests a Raspberry Pi 4B with at least 4 GB of RAM. Treat that as a small-scale target. Put the data directory on reliable SSD storage rather than relying on a heavily used removable card, and keep an independent backup because a Pi does not remove the risk of drive, power, or network failure.
Prepare Linux and the database
Supported operating-system families
Supported deployments include Debian and Ubuntu, as well as distributions in the Red Hat Enterprise Linux family. Apply security updates, set a stable hostname, and make sure the server has a fixed local address or a predictable VPS address. Create a dedicated operating-system account for Cells; do not run the service as root.
Create the database first
Install MySQL or MariaDB and create a database plus an account that the setup wizard can use. The Docker guide calls for a privileged database account during initialization, so prepare credentials with the permissions required by the version of Cells you are deploying. Store the password in a password manager and restrict database access to the Cells host or private network wherever possible.
Rank #2
- Value NAS with RAID for centralized storage and backup for all your devices. Check out the LS 700 for enhanced features, cloud capabilities, macOS 26, and up to 7x faster performance than the LS 200.
- Connect the LinkStation to your router and enjoy shared network storage for your devices. The NAS is compatible with Windows and macOS*, and Buffalo's US-based support is on-hand 24/7 for installation walkthroughs. *Only for macOS 15 (Sequoia) and earlier. For macOS 26, check out our LS 700 series.
- Subscription-Free Personal Cloud – Store, back up, and manage all your videos, music, and photos and access them anytime without paying any monthly fees.
- Storage Purpose-Built for Data Security – A NAS designed to keep your data safe, the LS200 features a closed system to reduce vulnerabilities from 3rd party apps and SSL encryption for secure file transfers.
- Back Up Multiple Computers & Devices – NAS Navigator management utility and PC backup software included. NAS Navigator 2 for macOS 15 and earlier. You can set up automated backups of data on your computers.
MongoDB is not a replacement for the required MySQL-compatible dependency in a standard installation. It is supported for selected services, so add it only when your chosen architecture specifically needs one of those services.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Set operating limits
Verify the open-file limit for the account that will run Cells. The documented floor is above 2,048 descriptors, with 8,192 recommended for production. If you use systemd, configure the service’s LimitNOFILE accordingly and verify the effective value after starting the service. Also synchronize the server clock with a reliable time source; authentication tokens and OAuth flows are time-sensitive.
Route A: install with Docker
1. Install Docker and confirm the host
Install a supported Docker Engine on the Linux host, enable it to start at boot, and confirm that the Docker daemon can create containers. Ensure the host can reach the database and that the firewall policy allows only the ports you intend to expose.
2. Run a temporary test container
For an initial test, start the image with host networking:
docker run -d --network=host pydio/cellsOpen https://localhost:8080 in a browser on the host, or use an SSH tunnel if the server has no graphical session. Complete the browser-based configuration wizard, enter the database connection details, create the first administrator, and confirm that you can sign in. This test proves that the image, database, and basic gateway work; it is not a durable production layout because no host directory has been mounted for persistence.
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #3
- Entry-level NAS Personal Storage：UGREEN NAS DH2300 is your first and best NAS made easy. It is designed for beginners who want a simple, private way to store videos, photos and personal files, which is intuitive for users moving from cloud storage or external drives and move away from scattered date across devices. This entry-level NAS 2-bay perfect for personal entertainment, photo storage, and easy data backup (doesn't support Docker or virtual machines).
- Set Your Devices Free, Expand Your Digital World: This unified storage hub supports massive capacity up to 64TB.*Storage drives not included. Stop Deleting, Start Storing. You can store 22 million 3MB images, or 2 million 30MB songs, or 43K 1.5GB movies or 67 million 1MB documents! UGREEN NAS is a better way to free up storage across all your devices such as phones, computers, tablets and also does automatic backups across devices regardless of the operating system—Window, iOS, Android or macOS.
- The Smarter Long-term Way to Store: Unlike cloud storage with recurring monthly fees, a UGREEN NAS enclosure requires only a one-time purchase for long-term use. For example, you only need to pay $459.98 for a NAS, while for cloud storage, you need to pay $719.88 per year, $2,159.64 for 3 years, $3,599.40 for 5 years. You will save $6,738.82 over 10 years with UGREEN NAS! *NAS cost based on DH2300 + 12TB HDD; cloud cost based on 12TB plan (e.g. $59.99/month).
- Blazing Speed, Minimal Power: Equipped with a high-performance processor, 1GbE port, and 4GB RAM on Board, this NAS handles multiple tasks with ease. File transfers reach up to 125MB/s—a 1GB file takes only 8 seconds. Don't let slow clouds hold you back; they often need over 100 seconds for the same task. The difference is clear.
- Let AI Better Organize Your Memories: UGREEN NAS uses AI to tag faces, locations, texts, and objects—so you can effortlessly find any photo by searching for who or what's in it in seconds. It also automatically finds and deletes similar or duplicate photo, backs up live photos and allows you to share them with your friends or family with just one tap. Everything stays effortlessly organized, powered by intelligent tagging and recognition.
3. Create a persistent production container
For a live service, bind a host directory to /var/cells. The directory holds pydio.json, user data, logs, certificates, and service information. Choose a filesystem with sufficient capacity, set ownership and permissions for the container process, and include the directory in your backup plan.
A typical layout uses host networking and environment settings for the HTTPS bind address and public URL. Adapt the values to your actual interface, port, and DNS name:
sudo mkdir -p /srv/pydio-cells
sudo chown -R 1000:1000 /srv/pydio-cells
docker run -d
--name pydio-cells
--restart unless-stopped
--network=host
-v /srv/pydio-cells:/var/cells
-e CELLS_SITE_BIND=0.0.0.0:8080
-e CELLS_SITE_EXTERNAL=https://files.example.com
pydio/cellsThe numeric ownership shown is an example; use the UID and GID expected by the image version you deploy. If the container is recreated, keep the same host directory and database. Never treat a disposable container layer as the location of your only copy of the files.
4. Configure the public URL
Set CELLS_SITE_EXTERNAL to the HTTPS URL that users and desktop or mobile clients will actually use. OAuth redirects depend on this external address. A localhost address may work for the first wizard but will cause client authentication or callback failures when users connect remotely.
5. Add TLS and DNS
Cells includes its own gateway and can serve HTTPS directly, so Apache or Nginx is not required for the basic deployment. Point a DNS name at the host, obtain a certificate using the method appropriate for your environment, and bind the service to the address and port you intend to expose. If you place a TLS-terminating proxy in front of Cells, preserve the external HTTPS URL and follow the Docker guide’s instructions for exposing the additional gRPC port required by Cells Sync.
Rank #4
- Your Personal Streaming Server - Build your own Netflix-style media library and stream 4K movies, shows and photos to any device without monthly fees
- Create Your Own Cloud - Store your entire photo, video and music collection; access from anywhere with fast 282 MB/s transfer speeds
- Creator-Grade Backup Solution - Protect your irreplaceable content with automated backups to cloud services, external drives and remote NAS
- Multi-Layered Data Protection - Combine RAID redundancy, automated backups and snapshot technology to prevent data loss from any cause
- Smart Home Surveillance - Support up to 30 IP cameras with AI detection, instant alerts and secure remote monitoring
6. Open only required ports
The default gateway is TCP port 8080, although both bind address and port are configurable. Permit that port only from the networks that need it, or expose the proxy’s HTTPS port while keeping the internal gateway private. Do not publish database ports to the public internet. If synchronization is enabled behind a proxy, open the documented gRPC port only where the proxy and clients require it.
Route B: install the binary on Linux
1. Download the correct build
Obtain the Cells binary matching the target operating system and CPU architecture. On a Raspberry Pi, that means selecting the appropriate ARM build; on most VPSs and desktop-class servers, it will be an AMD 64-bit build. Verify that the downloaded file is executable and store it in a controlled location such as /usr/local/bin.
2. Create the service account and directories
Create a dedicated pydio account and a working directory owned by that account. Keep application data, certificates, and logs on persistent storage. Restrict the directory so ordinary users cannot read database credentials or private keys.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
3. Run the configuration wizard
As the dedicated account, run:
cells configureThe wizard can finish in a browser or entirely in the terminal. Enter the database host, database name, account, and password; choose the HTTPS bind address; set the public external URL; and create the first administrator. Use the public URL that clients will use, not an internal hostname that remote devices cannot resolve.
4. Start and verify the service
Start Cells with:
cells startVisit the configured HTTPS endpoint, sign in, upload a test file, download it from a second client, and confirm that the file remains after a service restart. For long-running operation, create a systemd unit that runs as pydio, sets the open-file limit, starts after the network and database, and restarts on failure. Keep the unit’s environment and working directory explicit so upgrades do not silently change where data is written.
Best Value
- Personal & Home Private Storage: Yxk Zero1 2-Bay NAS is your gateway to stress-free private storage. Built for beginners who crave simplicity, it brings your scattered photos, videos, and files together into one secure home hub — no tech skills needed. Say goodbye to the chaos of multiple drives and cloud subscriptions, and hello to effortless access wherever you are. This entry-level 2-bay NAS is perfect for personal entertainment, photo backup, and worry-free data protection — now with Docker support for those ready to explore more.
- One-Time Investment, Lifelong Storage Freedom: Unlike Cloud storage with its recurring subscription fees and ever-shrinking free tiers, Yxk Zero1 NAS is a one-time purchase that puts you in complete control of your data. **The Hard Drive Must Be Purchased Separately — add or replace drives as your collection grows, no monthly bills, no storage limits imposed by others, and no risk of sudden price hikes. Your NAS, your rules, forever.
- Remote Access From Any Device: Once your NAS is set up, that's all you need to remember. Browse, upload, and share files from your phone app, desktop client, or any web browser — Windows, macOS, iOS, or Android. One central hub, everywhere you go.
- Blazing 2.5GbE Speed: With 2.5GbE connectivity — 2.5x faster than standard 1GbE — your files transfer in a flash and 4K streams without buffering. Flexible RAID modes, automated backups, and snapshot recovery work quietly in the background, so your data stays safe from drive failures or accidental loss. Speed without compromise, protection without complexity.
- Your Private Cloud Shared Your Way: You own your data — all of it, 100%. Advanced encryption and granular permission controls keep your files protected whether they're stored locally or shared with family and friends. Set up dedicated spaces for each user, so everyone gets seamless access across devices while keeping personal files truly personal. Privacy isn't a feature; it's the foundation.
Secure the deployment before inviting users
Use a non-root service
Run the binary or container with a dedicated non-root identity. Root execution increases the impact of a web vulnerability or a mistakenly mounted host path. Review directory ownership after upgrades and backups so the service can write data without granting it unnecessary access elsewhere.
Make HTTPS and timekeeping non-negotiable
Use HTTPS for the browser, API, desktop clients, and mobile clients. Keep the server’s date and time accurate. Pydio warns that an incorrect clock can invalidate authentication and produce errors such as HTTP 403, even when the password is correct.
Protect the database and secrets
- Keep MySQL or MariaDB on a private interface and firewall it from the public internet.
- Use a unique, high-entropy database password and administrator password.
- Restrict read access to the Cells data directory, especially certificates and configuration files.
- Record which host directories, database schemas, and external volumes belong to the deployment.
Back up independently
Back up both the database and the persistent Cells directory. The directory contains configuration, data, logs, certificates, and service information, while the database contains application state that a file-only copy may not capture consistently. Store at least one backup on a different device or location, test restoration on a separate host, and take a backup before upgrades or schema changes.
Raspberry Pi deployment details
A Raspberry Pi 4B with at least 4 GB of RAM is the documented small-deployment path. Install a 64-bit Linux distribution when the selected Cells build and your other software support it, connect the Pi by wired Ethernet where possible, and use an SSD for the Cells directory and database. Keep expectations modest: a Pi is suitable for a few users, learning, and home access, but large simultaneous transfers, previews, synchronization, and many workflows can exhaust its CPU, memory, or storage I/O.
Remote access requires more than installing the binary. You need a stable public DNS name, HTTPS, firewall rules, and either a reachable public address or a secure tunnel. If your internet connection uses carrier-grade NAT or changes addresses, a VPS or managed tunnel may be simpler than exposing the Pi directly. Whichever route you choose, keep the database and file backups independent of the Pi.
Docker versus binary installation
| Decision | Docker | Binary or bare metal |
|---|---|---|
| Isolation | Application and dependencies are isolated in a container; host networking can simplify the gateway. | Cells runs directly under a dedicated host account and shares the host’s libraries and service manager. |
| Initial setup | Fastest test path: one image and docker run, followed by the browser wizard. |
Requires downloading the correct binary, creating accounts and directories, then running cells configure. |
| Persistence | Explicitly mount a host directory to /var/cells. |
Choose and protect the working directory yourself. |
| Upgrades | Pull and recreate the container while retaining the host directory and database; follow the release notes. | Replace the binary under a controlled systemd or service workflow, retaining configuration and data. |
| Host control | Less host configuration, but you must understand image permissions, networking, and volumes. | More direct control over limits, logs, systemd, and filesystem layout. |
| Best fit | Labs, repeatable deployments, and administrators already operating Docker. | Minimal servers, traditional Linux operations, or environments where containers are not desired. |
Operating, upgrading, and monitoring
Keep a change record
Record the Cells version, image digest or binary checksum, database version, external URL, bind address, exposed ports, and backup location. This turns a recovery from guesswork into a repeatable procedure.
Watch the right signals
Check disk space, inode usage, memory, CPU, database health, certificate expiry, and failed login rates. Cells logs are under /var/cells/logs in the documented layout. For a systemd deployment, inspect the journal with commands such as:
sudo journalctl -u pydio-cells --since "1 hour ago"
sudo systemctl status pydio-cellsFor Docker, inspect container output and status:
docker ps --filter name=pydio-cells
docker logs --tail=200 pydio-cellsUpgrade conservatively
- Read the release notes for the target Cells version and confirm database compatibility.
- Take a verified database dump and a filesystem backup of the persistent Cells directory.
- Record the current image or binary version and configuration.
- Stop or quiesce the service according to the upgrade instructions.
- Deploy the new image or binary without deleting the persistent directory.
- Start the service, watch logs for migrations, and test administrator login, upload, download, sharing, and synchronization.
Troubleshooting common failures
| Symptom | Likely cause | Checks and fix |
|---|---|---|
| Browser cannot open the setup page | Service is stopped, wrong bind address, or firewall blocks the gateway | Check docker ps or systemctl status, inspect logs, verify the configured port, and allow only the required port through the firewall. |
| Setup cannot connect to the database | Database is down, credentials lack privileges, or the hostname is unreachable from the container | Test the database account from the Cells host, confirm MySQL/MariaDB version, and verify container-to-host or container-to-database networking. |
| Files disappear after a container recreation | No persistent volume was mounted | Stop using the disposable container layer; mount the host directory to /var/cells and restore from backup if necessary. |
| Remote clients fail OAuth or redirects | External URL is localhost, an internal hostname, or uses HTTP while clients expect HTTPS | Set CELLS_SITE_EXTERNAL or the binary configuration to the public HTTPS FQDN and ensure DNS and certificates match it. |
| HTTP 403 during authentication | Server clock is inaccurate or a proxy changes request details | Synchronize time, verify the HTTPS endpoint and proxy headers, then retry authentication. |
| Cells Sync fails behind a reverse proxy | Required gRPC port is not exposed or proxied | Expose and route the additional gRPC port specified by the Docker guide; keep it limited to the networks that need synchronization. |
| “Too many open files” or intermittent upload errors | File-descriptor limit is too low | Raise the limit above 2,048; use 8,192 for production as recommended, then restart the service and verify the effective limit. |
| Uploads are slow or the host becomes unresponsive | Insufficient CPU, RAM, storage I/O, or network bandwidth | Check resource graphs, move data to SSD, reduce concurrent workload, or migrate to a host with more headroom. |
A production-readiness checklist
- Linux host is patched and has a stable hostname, address, and synchronized clock.
- Cells runs as a dedicated non-root user.
- MySQL or MariaDB is installed, reachable privately, and backed up.
- Persistent storage is mounted and has tested restore procedures.
- Open-file limit is above 2,048; 8,192 is configured where production load warrants it.
- HTTPS certificate, DNS record, bind address, and public external URL agree.
- Only the gateway and any required synchronization port are exposed.
- Database and filesystem backups are independent and periodically restored in a test environment.
- Administrator login, upload, download, sharing, mobile or desktop OAuth, and synchronization have all been tested.
- Logs, disk space, certificate expiry, and service availability are monitored.
Bottom line
For most first deployments, start with Docker, a MySQL-compatible database, an SSD-backed host, and a mounted /var/cells directory. Set the public HTTPS URL before connecting clients, run the service without root privileges, and verify backups before storing irreplaceable files. A Raspberry Pi 4B with 4 GB or more can handle a small home or lab Cells installation, while heavier collaboration workloads justify a larger server or VPS. Choose the binary route when direct systemd and filesystem control matter more than container isolation.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errors
