Support intro
Sorry to hear you’re facing problems. 
The community help forum (help.nextcloud.com) is for home and non-enterprise users. Support is provided by other community members on a best effort / “as available” basis. All of those responding are volunteering their time to help you.
If you’re using Nextcloud in a business/critical setting, paid and SLA-based support services can be accessed via portal.nextcloud.com where Nextcloud engineers can help ensure your business keeps running smoothly.
Getting help
In order to help you as efficiently (and quickly!) as possible, please fill in as much of the below requested information as you can.
Before clicking submit: Please check if your query is already addressed via the following resources:
- Official documentation (searchable and regularly updated)
- How to topics and FAQs
- Forum search
(Utilizing these existing resources is typically faster. It also helps reduce the load on our generous volunteers while elevating the signal to noise ratio of the forums otherwise arising from the same queries being posted repeatedly).
Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can. 
The Basics
- Nextcloud Server version (e.g., 29.x.x):
- nextcloud:31.0.8-apache
- Operating system and version (e.g., Ubuntu 24.04):
- Debian GNU/Linux 12 (bookworm) x86_64
- Reverse proxy and version _(e.g. nginx 1.27.2)
- caddy:latest and dnsmasq for local DNS
- Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
Docker
- Are you using CloudfIare, mod_security, or similar? (Yes / No)
Not Yet
Hello,
Because my university has reduced my OneDrive from 1 TB to 100 GB and I’ve been asked to delete the “excess” to free up space (I’ve started downloading everything to a 1 TB 3.5" HDD I have at home),
I’ve taken on the task of implementing my own cloud storage. In this case, I’ve chosen Nextcloud. So, I decided to give it a try. I opted to use the community Docker version (https://github.com/nextcloud/docker) since I only need file management.
My laptop specs:
specs
OS: Debian GNU/Linux 12 (bookworm) x86_64
Kernel: Linux 6.1.0-37-amd64
Shell: bash 5.2.15
DE: Xfce4 4.18
WM: Xfwm4 (X11)
WM Theme: Default
Theme: Adwaita-dark \[GTK2/3/4\]
Icons: Adwaita \[GTK2/3/4\]
Font: Sans (10pt) \[GTK2/3/4\]
Cursor: Adwaita
Terminal: xfce4-terminal 1.0.4
CPU: Intel(R) Core™ i3-3227U (4) @ 1.90 GHz
GPU: Intel 3rd Gen Core processor Graphics Controller @ 1.10 GHz \[Integrated\]
Memory: 4.38 GiB / 7.46 GiB (59%)
Swap: 5.24 GiB / 14.90 GiB (35%)
Disk (/): 32.65 GiB / 63.62 GiB (51%) - ext4
Disk (/home): 108.04 GiB / 139.67 GiB (77%) - ext4
Disk (/media/familia/HBCD_PE_x64): 902.29 GiB / 920.39 GiB (98%) - fuseblk
Disk (/media/familia/HDD): 453.42 GiB / 465.76 GiB (97%) - fuseblk
Disk (/media/familia/HHD1TA): 92.25 GiB / 915.82 GiB (10%) - ext4
Local IP (enp2s0): 192.168.1.19/24
Locale: es_MX.UTF-8
For the test, I decided to create a folder at /mnt/Nextcloud (27 GB free). Here’s my docker-compose.yml:
services:
nextcloud:
image: nextcloud:31.0.8-apache
container_name: nextcloud
restart: unless-stopped
ports:
- "8087:80"
environment:
- NEXTCLOUD_ADMIN_USER=admin
- NEXTCLOUD_ADMIN_PASSWORD=adminpass
- SQLITE_DATABASE=nextcloud.db
- NEXTCLOUD_TRUSTED_DOMAINS=files.nehemiasfeliz.com
- OVERWRITEHOST=files.nehemiasfeliz.com
- OVERWRITEPROTOCOL=https
- PHP_MEMORY_LIMIT=1G
- PHP_UPLOAD_LIMIT=0
- APACHE_BODY_LIMIT=0
volumes:
- nextcloud:/var/www/html
- /mnt/Nextcloud:/var/www/html/data
deploy:
resources:
limits:
cpus: '0.5'
memory: 512M
volumes:
nextcloud:
To access the service, I use dnsmasq as the local DNS and Caddy (in Docker) as the reverse proxy. Here’s the configuration:
# dnsmasq.conf
interface=lo,eth0
listen-address=127.0.0.1,192.168.1.19
address=/files.nehemiasfeliz.com/192.168.1.19
server=/nehemiasfeliz.com/8.8.8.8
server=/nehemiasfeliz.com/148.103.0.73
server=148.103.0.73
server=8.8.8.8
services:
caddy-local:
image: caddy:latest
container_name: caddy-local
ports:
- "80:80"
- "443:443"
volumes:
- ./Caddyfile.local:/etc/caddy/Caddyfile:ro
- caddy_local_data:/data
- caddy_local_config:/config
environment:
- CLOUDFLARE_API_TOKEN=<TOKEN>
restart: unless-stopped
volumes:
caddy_local_data:
caddy_local_config:
# Caddyfile.local
{
email juniornff@gmail.com
acme_dns cloudflare {env.CLOUDFLARE_API_TOKEN}
http_port 80
https_port 443
ocsp_stapling off
}
# Redirección HTTP → HTTPS
:80 {
redir https://{host}:8444{uri} permanent
}
files.nehemiasfeliz.com {
reverse_proxy 192.168.1.19:8087
}
After starting the container, the configuration shows errors related to the setup.
Errors
There are several configuration-related errors.
[Red] - The reverse proxy header configuration is incorrect. This is a security issue and could allow an attacker to spoof an IP address visible to Nextcloud. For more details, check the documentation (Reverse proxy — Nextcloud latest Administration Manual latest documentation).
[Yellow] - The server does not have a maintenance window start time configured. This means that resource-intensive daily background jobs will run during regular usage hours. We recommend setting it to a time of low usage to reduce the impact on users caused by these intensive tasks. For more details, check the documentation (Background jobs — Nextcloud latest Administration Manual latest documentation).
[Yellow] - One or more MIME type migrations are available. New MIME types are typically added to handle certain file types more appropriately. Migrating MIME types can take considerable time on large instances, so this is not done automatically during updates. Use the command occ maintenance:repair --include-expensive to perform the migrations.
[Yellow] - Some headers are not properly configured in your instance - The HTTP header Strict-Transport-Security is not configured (it should be at least 15552000 seconds). For enhanced security, it is recommended to enable HSTS. For more details, check the documentation (Hardening and security guidance — Nextcloud latest Administration Manual latest documentation).
[Yellow] - SQLite is currently being used as the primary database. For larger installations, we recommend switching to a different primary database. This is particularly recommended when using the desktop client for file synchronization. To migrate to another database, use the command-line tool: “occ db:convert-type”. For more details, check the documentation (Converting database type — Nextcloud latest Administration Manual latest documentation).
[White] - The database is being used for transactional file locking. To improve performance, please use memcache if available. For more details, check the documentation (Transactional file locking — Nextcloud latest Administration Manual latest documentation).
[White] - Your installation does not have a default phone region selected. This is necessary to validate phone numbers in user settings that do not include an international code. To allow numbers without an international code, add the “default_phone_region” setting with the corresponding ISO 3166-1 code in your configuration file. For more details, check the documentation (ISO 3166-1 alpha-2 - Wikipedia).
[White] - You have not entered or verified your email server settings yet. Please go to “Basic Settings” to configure it. Then, use the “Send email” button below the form to verify your settings. For more details, check the documentation (Email — Nextcloud latest Administration Manual latest documentation).
But I can check that later. Also, I have some questions:
-
When I start the container and access Nextcloud, I see that it creates some “example” files and folders. If I use my HDD for Nextcloud instead of the created folder, will all the files on that HDD be deleted? Or will those example files simply be added to the HDD?
-
I’m using SQLite as the database. The use I intend for Nextcloud is mostly personal, and maybe for a few family members/friends. Should I switch to another database? Would that change significantly affect resource consumption?
Later, I plan to use my Cloudflare domain to make it accessible outside my local network, using cloudflare-ddns in Docker (https://github.com/timothymiller/cloudflare-ddns) as my DDNS and another Caddy in Docker for the reverse proxy:
services:
cloudflare-ddns:
image: timothyjmiller/cloudflare-ddns:latest
container_name: cloudflare-ddns
network_mode: "host"
security_opt:
- no-new-privileges:true
volumes:
- ./config.json:/config.json:ro
restart: unless-stopped
# config.json
{
"cloudflare": [
{
"authentication": {
"api_token": "TOKEN"
},
"zone_id": "ID",
"subdomains": [
{ "name": "files", "proxied": true } # i will paste that
]
}
],
"a": true,
"aaaa": true,
"purgeUnknownRecords": false,
"ttl": 300
}
services:
caddy:
image: caddy:latest
container_name: caddy-reverse
ports:
- "8081:80"
- "8443:443"
volumes:
- ./Caddyfile:/etc/caddy/Caddyfile:ro
- ./cloudflare-origin/cert.pem:/etc/caddy/cloudflare-origin/cert.pem:ro
- ./cloudflare-origin/key.pem:/etc/caddy/cloudflare-origin/key.pem:ro
- caddy_data:/data
- caddy_config:/config
restart: unless-stopped
volumes:
caddy_data:
caddy_config:
# Caddyfile
:80 {
redir https://{host}{uri} permanent
}
files.nehemiasfeliz.com {
tls /etc/caddy/cloudflare-origin/cert.pem /etc/caddy/cloudflare-origin/key.pem
reverse_proxy 192.168.1.19:8087
}
Should I do anything else besides that?
.
