Im using a External Storage folder to hold my markdown notes. I only use them sporadically via Nextcloud and view/change them mostly via external applications. But i have to rely on the Nextcloud WebDAV sync to sync the to some devices. When i now change such a note externally, this change doesnt sync to the devices. Nextcloud means, that the files have not changed. Only when I open one of the edited notes the change will be detected, and then the WebDAV sync works.

In the adminpanel i have set the option for this external storage in "Check for changes" to "Once every direct access". I can also set it to "Never". Both settings are documented. But there is also a setting "Ever". This is not documented in https://docs.nextcloud.com/server/stable/admin_manual/configuration_files/external_storage_configuration_gui.html

Unfortunately, "Always" doesn't necessarily mean "Immediately." When I select "Always," the WebDAV sync still hasn't completed even after 10 minutes.

So where does this “Always” come from if it’s not documented anywhere, and what does it mean? And even more importantly, how do I get a WebDAV sync to work after making a change? Do I really have to run occ files_external:scan <id> every few seconds?

Is there some way to use Nextcloud as DMS? It should be possible to scan bills with a phone and add this as PDF and OCR to Nextcloud, or PDF manuals and such things. All should be categorized and tagged semi automatic.

geteilt von: https://discuss.tchncs.de/post/56066354

Hey, I need help :(

I was tinkering a bit with Collabora and Nextcloud Office. First it worked fine, then I noticed that only SOME office documents were opening in browser, some were just downloading.

After tinkering more, the situation is completely broken now: All files, images, videos, office documents are listed as "unscanned" in the web interface. And they don't render in browser, but get downloaded right away when you click. (Also no "view" option in the three-dots-menu). occ does NOT see unscanned files (tried occ files:scan --unscanned). A full rescan of files also didn't help.

Does anyone have any idea?

Everytime I try setting trusted domains variables before booting, and rebuild my container, there is only localhost being set in config.php. Is there a way I can have the file automatically set on a freshly built container?

The environment variable NEXTCLOUD_TRUSTED_DOMAINS does get loaded onto the server, but the Nextcloud install is not using it.

Honestly, I would even be happy with NEXTCLOUD_TRUSTED_DOMAINS=* at this point to trust all domains.

The latest Nextcloud Files Linux AppImage does not run on my system. Can anyone confirm? When I try to run it in a terminal, it fails with this error:

./Nextcloud-4.0.5-x86_64.AppImage: symbol lookup error: /tmp/.mount_NextclHbCPhi/usr/bin/../lib/libgobject-2.0.so.0: undefined symbol: g_string_copy

I use Debian 13 and have been using Nextcloud AppImage versions for many years without problems. What is going wrong here? Did they forget to include some library in the image? Don't they test what they compile?

Luckily, I still have the older 4.0.1 version. But using out of date software is not ideal.

The smaller than usual size of the AppImage seems a bit suspicious to me (167 MB vs. 193 MB for the older version). While I welcome de-bloating, this seems like they left out some essential stuff.

Ya. I did it on my nextcloud collabora. Love this shit.
I wish nextcloud managed playing music in a more normal fashion, but as a document editor and repository, it's doing great for me.
And even the music player ... well it works. I'm listening to it.
My cheap-ass hetzner for $5/month and nextcloud. Takin care of my biz.

I'm trying to set up Nextcloud using the AIO Docker install onto my Synology.

I got through the first stage of setup, and navigated to the /containers page. It shows all containers as "Starting", with a yellow dot. Except for the Fulltextsearch, which is Stopped red (due to me stopping it, after I realised I had installed it despite my platform not supporting Seccomp, but the "Optional containers" checkbox being greyed out even when it’s stopped).

Many of these containers show as green/healthy in the DSM Container Manager even though the /containers page doesn't show them as such.

Logs for the different containers:

::: spoiler Mastercontainer logs:

Trying to fix docker.sock permissions internally...
Adding internal www-data to group root
DOCKER_API_VERSION was found to be set to '1.43'.
Please note that only v1.44 is officially supported and tested by the maintainers of Nextcloud AIO.
So you run on your own risk and things might break without warning.
WARNING: No kernel memory TCP limit support
WARNING: No cpu cfs quota support
WARNING: No cpu cfs period support
WARNING: No blkio throttle.read_bps_device support
WARNING: No blkio throttle.write_bps_device support
WARNING: No blkio throttle.read_iops_device support
WARNING: No blkio throttle.write_iops_device support
WARNING: No kernel memory TCP limit support
WARNING: No cpu cfs quota support
WARNING: No cpu cfs period support
WARNING: No blkio throttle.read_bps_device support
WARNING: No blkio throttle.write_bps_device support
WARNING: No blkio throttle.read_iops_device support
WARNING: No blkio throttle.write_iops_device support
Initial startup of Nextcloud All-in-One complete!
You should be able to open the Nextcloud AIO Interface now on port 8080 of this server!
E.g. https://internal.ip.of.this.server:8080/
⚠️ Important: do always use an ip-address if you access this port and not a domain as HSTS might block access to it later!

If your server has port 80 and 8443 open and you point a domain to your server, you can get a valid certificate automatically by opening the Nextcloud AIO Interface via:
https://your-domain-that-points-to-this-server.tld:8443/
/usr/lib/python3.12/site-packages/supervisor/options.py:13: UserWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html. The pkg_resources package is slated for removal as early as 2025-11-30. Refrain from using this package or pin to Setuptools<81.
  import pkg_resources
{"level":"warn","ts":1766322552.6626272,"msg":"failed to set GOMAXPROCS","error":"open /sys/fs/cgroup/cpu/cpu.cfs_quota_us: no such file or directory"}
{"level":"info","ts":1766322552.6628811,"msg":"GOMEMLIMIT is updated","package":"github.com/KimMachineGun/automemlimit/memlimit","GOMEMLIMIT":3671407411,"previous":9223372036854775807}
{"level":"info","ts":1766322552.6629462,"msg":"using config from file","file":"/Caddyfile"}
{"level":"info","ts":1766322552.6645825,"msg":"adapted config to JSON","adapter":"caddyfile"}
{"level":"info","ts":1766322552.6664238,"msg":"serving initial configuration"}
[mpm_event:notice] [pid 152:tid 152] AH00489: Apache/2.4.66 (Unix) OpenSSL/3.5.4 configured -- resuming normal operations
[core:notice] [pid 152:tid 152] AH00094: Command line: 'httpd -D FOREGROUND'
NOTICE: fpm is running, pid 157
NOTICE: ready to handle connections
NOTICE: PHP message: 404 Not Found
Type: Slim\Exception\HttpNotFoundException
Code: 404
Message: Not found.
File: /var/www/docker-aio/php/vendor/slim/slim/Slim/Middleware/RoutingMiddleware.php
Line: 76
Trace: #0 /var/www/docker-aio/php/vendor/slim/slim/Slim/Routing/RouteRunner.php(62): Slim\Middleware\RoutingMiddleware->performRouting(Object(GuzzleHttp\Psr7\ServerRequest))
#1 /var/www/docker-aio/php/vendor/slim/csrf/src/Guard.php(482): Slim\Routing\RouteRunner->handle(Object(GuzzleHttp\Psr7\ServerRequest))
#2 /var/www/docker-aio/php/vendor/slim/slim/Slim/MiddlewareDispatcher.php(178): Slim\Csrf\Guard->process(Object(GuzzleHttp\Psr7\ServerRequest), Object(Slim\Routing\RouteRunner))
#3 /var/www/docker-aio/php/vendor/slim/twig-view/src/TwigMiddleware.php(117): Psr\Http\Server\RequestHandlerInterface@anonymous->handle(Object(GuzzleHttp\Psr7\ServerRequest))
#4 /var/www/docker-aio/php/vendor/slim/slim/Slim/MiddlewareDispatcher.php(129): Slim\Views\TwigMiddleware->process(Object(GuzzleHttp\Psr7\ServerRequest), Object(Psr\Http\Server\RequestHandlerInterface@anonymous))
#5 /var/www/docker-aio/php/src/Middleware/AuthMiddleware.php(53): Psr\Http\Server\RequestHandlerInterface@anonymous->handle(Object(GuzzleHttp\Psr7\ServerRequest))
#6 /var/www/docker-aio/php/vendor/slim/slim/Slim/MiddlewareDispatcher.php(283): AIO\Middleware\AuthMiddleware->__invoke(Object(GuzzleHttp\Psr7\ServerRequest), Object(Psr\Http\Server\RequestHandlerInterface@anonymous))
#7 /var/www/docker-aio/php/vendor/slim/slim/Slim/Middleware/ErrorMiddleware.php(77): Psr\Http\Server\RequestHandlerInterface@anonymous->handle(Object(GuzzleHttp\Psr7\ServerRequest))
#8 /var/www/docker-aio/php/vendor/slim/slim/Slim/MiddlewareDispatcher.php(129): Slim\Middleware\ErrorMiddleware->process(Object(GuzzleHttp\Psr7\ServerRequest), Object(Psr\Http\Server\RequestHandlerInterface@anonymous))
#9 /var/www/docker-aio/php/vendor/slim/slim/Slim/MiddlewareDispatcher.php(73): Psr\Http\Server\RequestHandlerInterface@anonymous->handle(Object(GuzzleHttp\Psr7\ServerRequest))
#10 /var/www/docker-aio/php/vendor/slim/slim/Slim/App.php(209): Slim\MiddlewareDispatcher->handle(Object(GuzzleHttp\Psr7\ServerRequest))
#11 /var/www/docker-aio/php/vendor/slim/slim/Slim/App.php(193): Slim\App->handle(Object(GuzzleHttp\Psr7\ServerRequest))
#12 /var/www/docker-aio/php/public/index.php(200): Slim\App->run()
#13 {main}
Tips: To display error details in HTTP response set "displayErrorDetails" to true in the ErrorHandler constructor.
NOTICE: Terminating ...
NOTICE: exiting, bye-bye!
[mpm_event:notice] [pid 152:tid 152] AH00491: caught SIGTERM, shutting down

:::

::: spoiler Database logs:

+ rm -rf '/var/lib/postgresql/data/*'
+ touch /mnt/data/initial-cleanup-done
+ set +ex
chmod: /var/run/postgresql: Operation not permitted
The files belonging to this database system will be owned by user "postgres".
This user must also own the server process.

The database cluster will be initialized with locale "en_US.utf8".
The default database encoding has accordingly been set to "UTF8".
The default text search configuration will be set to "english".

Data page checksums are disabled.

fixing permissions on existing directory /var/lib/postgresql/data ... ok
creating subdirectories ... ok
selecting dynamic shared memory implementation ... posix
selecting default "max_connections" ... 100
selecting default "shared_buffers" ... 128MB
selecting default time zone ... Australia/Brisbane
creating configuration files ... ok
running bootstrap script ... ok
sh: locale: not found
[30] WARNING:  no usable system locales were found
performing post-bootstrap initialization ... ok
initdb: warning: enabling "trust" authentication for local connections
initdb: hint: You can change this by editing pg_hba.conf or using the option -A, or --auth-local and --auth-host, the next time you run initdb.
syncing data to disk ... ok


Success. You can now start the database server using:

    pg_ctl -D /var/lib/postgresql/data -l logfile start

waiting for server to start....
[36] LOG:  starting PostgreSQL 17.7 on x86_64-pc-linux-musl, compiled by gcc (Alpine 15.2.0) 15.2.0, 64-bit
[36] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
[39] LOG:  database system was shut down at 2025-12-21 23:21:07 AEST
[36] LOG:  database system is ready to accept connections
 done
server started
CREATE DATABASE


/usr/local/bin/docker-entrypoint.sh: running /docker-entrypoint-initdb.d/init-user-db.sh
CREATE ROLE
ALTER DATABASE
+ touch /mnt/data/initialization.failed
+ psql -v ON_ERROR_STOP=1 --username nextcloud --dbname nextcloud_database
GRANT
GRANT
+ rm /mnt/data/initialization.failed

waiting for server to shut down....2025-12-21 23:21:12.597 AEST [36] LOG:  received fast shutdown request
+ set +ex
[36] LOG:  aborting any active transactions
[36] LOG:  background worker "logical replication launcher" (PID 42) exited with exit code 1
[37] LOG:  shutting down
[37] LOG:  checkpoint starting: shutdown immediate
[37] LOG:  checkpoint complete: wrote 934 buffers (5.7%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.805 s, sync=0.674 s, total=2.456 s; sync files=308, longest=0.322 s, average=0.003 s; distance=4260 kB, estimate=4260 kB; lsn=0/19163B0, redo lsn=0/19163B0
[36] LOG:  database system is shut down
 done
server stopped

PostgreSQL init process complete; ready for start up.

[14] LOG:  starting PostgreSQL 17.7 on x86_64-pc-linux-musl, compiled by gcc (Alpine 15.2.0) 15.2.0, 64-bit
[14] LOG:  listening on IPv4 address "0.0.0.0", port 5432
[14] LOG:  listening on IPv6 address "::", port 5432
[14] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
[57] LOG:  database system was shut down at 2025-12-21 23:21:15 AEST
[14] LOG:  database system is ready to accept connections
[55] LOG:  checkpoint starting: time
[55] LOG:  checkpoint complete: wrote 48 buffers (0.3%); 0 WAL file(s) added, 0 removed, 0 recycled; write=4.592 s, sync=0.911 s, total=6.666 s; sync files=13, longest=0.172 s, average=0.071 s; distance=270 kB, estimate=270 kB; lsn=0/1959CE8, redo lsn=0/1959C58
++ rm -f /mnt/data/database-dump.sql.temp
++ touch /mnt/data/export.failed
++ pg_dump --username nextcloud nextcloud_database
++ rm -f /mnt/data/database-dump.sql
++ mv /mnt/data/database-dump.sql.temp /mnt/data/database-dump.sql
++ pg_ctl stop -m fast
[14] LOG:  received fast shutdown request
[14] LOG:  aborting any active transactions
[14] LOG:  background worker "logical replication launcher" (PID 60) exited with exit code 1
[55] LOG:  shutting down
[55] LOG:  checkpoint starting: shutdown immediate
[55] LOG:  checkpoint complete: wrote 0 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.001 s, sync=0.001 s, total=0.502 s; sync files=0, longest=0.000 s, average=0.000 s; distance=0 kB, estimate=243 kB; lsn=0/1959D98, redo lsn=0/1959D98
[14] LOG:  database system is shut down
waiting for server to shut down.... done
server stopped
++ rm /mnt/data/export.failed
++ echo 'Database dump successful!'
++ set +x
Database dump successful!
Setting postgres values...
chmod: /var/run/postgresql: Operation not permitted

PostgreSQL Database directory appears to contain a database; Skipping initialization

[14] LOG:  starting PostgreSQL 17.7 on x86_64-pc-linux-musl, compiled by gcc (Alpine 15.2.0) 15.2.0, 64-bit
[14] LOG:  listening on IPv4 address "0.0.0.0", port 5432
[14] LOG:  listening on IPv6 address "::", port 5432
[14] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
[24] LOG:  database system was shut down at 2025-12-21 23:49:29 AEST
[14] LOG:  database system is ready to accept connections

:::

::: spoiler Nextcloud logs:

Waiting for database to start...
Waiting for database to start...
Waiting for database to start...

:::

::: spoiler Redis logs:

Memory overcommit is disabled but necessary for safe operation
See https://github.com/nextcloud/all-in-one/discussions/1731 how to enable overcommit
Redis has started
# WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
# WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.

:::

I don’t think Redis is related to my current problem, but I suspect they may be an issue later...

Configuration

::: spoiler AIO compass.yaml file:

name: nextcloud-aio
services:
  nextcloud-aio-mastercontainer:
    image: ghcr.io/nextcloud-releases/all-in-one:latest
    init: true
    restart: always
    container_name: nextcloud-aio-mastercontainer
    volumes:
      - nextcloud_aio_mastercontainer:/mnt/docker-aio-config
      - /run/docker.sock:/var/run/docker.sock:ro
    network_mode: bridge
    ports:
      - 8080:8080
    environment:
      APACHE_PORT: 11000
      APACHE_IP_BINDING: 127.0.0.1
      DOCKER_API_VERSION: 1.43 # As far as I can tell, this is the version supported on Synology when running "docker version | grep API"
      NEXTCLOUD_DATADIR: /volume1/nextcloud
      WATCHTOWER_DOCKER_SOCKET_PATH: /run/docker.sock
      COLLABORA_SECCOMP_DISABLED: true

volumes:
  nextcloud_aio_mastercontainer:
    name: nextcloud_aio_mastercontainer

:::

Does anyone have any idea of how to get this working? Or of good troubleshooting steps to try?

Why is the official Nextcloud help community so combative? I've been working with Nextcloud for about 3 months in various configurations and every time I've had to seek assistance there it has been an unwelcome experience.

Even when I say something to the effect of "I'm having this problem with "X", I think I've done something wrong in configuration, where should I look first?" I almost always get a sharp response at best, and most often a response akin to: "You're wrong, that problem doesn't exist. I've tested it on my server." This latest time, I've found a problem in 3 different installations, 2 other users confirmed they also experience the problem and my thread is just hijacked with "Well we don't see it, so it doesn't exist." and "You should have told us "X" if you wanted any real help." or "Why are you asking here instead of somewhere else?" Every time I post there, I find myself backing away cautiously while vitreol just erupts.

I'm not one of the users who just willy nilly starts posting questions everywhere - I go through lot of self-help effort, investigating, researching and looking at official documentation and searching online to try and figure it out myself before I post, but I'm always faced with a "You're so stupid for posting here." vibe over there. I've experienced this same or similar behavior over at least a half a dozen attempts to get help with something. In my 20+ years of hosting experience, participating in countless communities, I have never experienced such an unwelcoming, hostile "help community". What's the deal?

cross-posted from: https://aussie.zone/post/27569122

Most of the threads I've found on other sites (both Reddit and the Synology forums) have basically said "go with Docker". But what do you actually gain from this?

People suggest it's more up-to-date, and maybe for some packages that's true? But for Nextcloud specifically it looks pretty good. 32.0.3 came out 1 day ago and isn't yet supported, but the version immediately preceding that, from 3 weeks ago, is.

I've never done Nextcloud before, but I would assume installing it via the Package Center would be way easier to install and to keep up-to-date than Docker. So what's the reason everyone recommends Docker? Is it easier to extend?

I volunteer with a small local org. They use Google Workspace. I want to ask them to switch to NextCloud. But despite looking pretty throughly, I can't find anyone that offers managed hosting/support. I don't want to be the sysadmin. The org already pays a hefty fee for Google so they should't have a problem paying for NextCloud.

NC recommends a bunch of providers on their site, but they all look like VPS's, and don't seem to mention NC at all, much less anything about support. They also all look like they're non-US, which I understand many would consider a good thing but I really don't want to be dealing with slow connections. Not sure if that's a realistic concern.

Bonus points if they offer discounts for non-profits.

cross-posted from: https://lemmy.world/post/38329467

• Includes a talk about Nextcloud development from an employee

Main site at https://seagl.org/ and they are on fediverse @[email protected]

A number of talks and expo hall. All are welcome; please help re-share so people can know about it and attend. Lots of the talks will be on streaming as well for remote participation. They also have Matrix chats https://seagl.org/meet

Please enjoy this very technical discussion on Nextcloud Atomic, the immutable system-level wrapper for Nextcloud AIO, which is being designed as the successor to NextcloudPi. Atomic delivers Nextcloud as a simple deployment for single machines, allowing easy selfhosting for home enthusiasts and anyone else wanting to run Nextcloud.

Interview includes Tobias (Atomic, NextcloudPi, Nextcloud Secrets) and Marcel (Floccus, Bookmarks, Recognize). Begins with quick overview and review of running Nextcloud, along with popular outlying Nextcloud implementations and apps then discussed at-length. For comprehensive show notes and timestamps click here.

If you enjoy the interview, please do share it with others! Thanks so much.