Troubleshooting guide

Nextcloud Slow Uploads: Server, Storage and Proxy Checks

Troubleshoot slow Nextcloud uploads caused by PHP-FPM, NGINX, Redis locking, object storage, S3, disk I/O, reverse proxies and client behaviour.

Remote support availableCommercial systemsService: Nextcloud Performance Tuning
Nextcloudslow uploadsS3PHP-FPMRedis

What this problem usually means

Slow Nextcloud uploads can come from PHP limits, reverse proxy buffering, file locking, slow storage, S3/object storage latency, database load, or client-side chunked upload behaviour.

Production caution: Do not only raise upload limits. If storage or file locking is the issue, larger uploads may fail later and consume more resources.

Common symptoms

  • Uploads start fast then stall
  • Large files fail or timeout
  • Sync client repeatedly retries files
  • Web uploads are slower than expected
  • Server load or disk I/O rises during uploads

Common causes

  • PHP upload/time limits too low
  • NGINX client body or proxy timeouts
  • Redis/file locking problems
  • Object storage latency or API throttling
  • Database and preview jobs competing for resources
  • Slow local disk or network storage

Safe first checks

These checks are intended to help identify the direction of the issue. Always adjust paths, service names and commands for your environment.

Check Nextcloud logs

tail -100 /path/to/nextcloud/data/nextcloud.log

Check PHP upload limits

php -i | grep -E "upload_max_filesize|post_max_size|max_execution_time"

Check NGINX errors

tail -100 /var/log/nginx/error.log

Check disk and I/O

df -h; iostat -xz 1 3

Typical fixes

  • Align PHP, NGINX and proxy upload limits
  • Confirm Redis file locking is healthy
  • Tune timeouts for large uploads
  • Review object storage/S3 latency and request patterns
  • Separate heavy preview/background jobs from upload windows
  • Check disk, network and database bottlenecks

When to get help

Get help if the system is production-facing, customer data is involved, backups are uncertain, or the issue affects revenue, security or uptime. We can review the logs, confirm the cause and quote a fixed-scope fix where appropriate.

Need this fixed?

Get remote support for this issue.

Fixed technical support starts from $499. Emergency incident support is $199/hr with a minimum window.

Contact Us

Related guides