On 3.7.2018 at 01:28, dlandon said:

Der beste Weg zum Update ist über den integrierten ownCloud-Updater. Es wird jedoch nicht mit einem selbst signierten Zertifikat aktualisiert. Ich verwende ein richtiges Zertifikat und es lohnt sich, nur den eingebauten ownCloud-Updater verwenden zu können

Gruß in die Runde

Ich habe das heute versucht, hab aktuell die 10.15.2 auf unraid, der updater zeigt mir an das ich auf 10.15.3 ubdaten kann, Checking System wird wunderbar durchlaufen "mit grünem Haken" aber bei Creating a checkpoint, bleibt er stehen und der "spinner" läuft dauerhaft und es erscheint dann irgendwann Server error 504: error Message: See your webserver logs for details.?

Gruß Andreas

23 hours ago, Hitchcock said:

Gruß in die Runde

Ich habe das heute versucht, hab aktuell die 10.15.2 auf unraid, der updater zeigt mir an das ich auf 10.15.3 ubdaten kann, Checking System wird wunderbar durchlaufen "mit grünem Haken" aber bei Creating a checkpoint, bleibt er stehen und der "spinner" läuft dauerhaft und es erscheint dann irgendwann Server error 504: error Message: See your webserver logs for details.?

Gruß Andreas

Use the manual method here https://forums.unraid.net/topic/57801-support-dlandon-owncloud/#findComment-566488. The built in update hasn't worked for me for a long time.

Hello,
I am currently trying to remove index.php from tha share link, but any of my attempts are not working.

Can I please get advice how to remove this from the link?

thx

I have problem with owncloud ... i want to use tailscale ..

I made this adjustments..

And a change the default data in folder nginx..

An the container is not running -.-

hi i setup the own cloud and created users and ive played with the windows client.. so i can copy files to file broswer and then it syncs on unraid server.. so that part works

but it doesnt work in reverse... if i wanna put files in user folders files from unraid server.. like using Krusader and copy a bunch of documents or pictures.. to several user folders... it does not sync doesnt show up when you log in.. it doesnt even recongize files are in the files folder... how you supposed to get the software to see files you copy in folders from the server side... not the client side

13 hours ago, comet424 said:

hi i setup the own cloud and created users and ive played with the windows client.. so i can copy files to file broswer and then it syncs on unraid server.. so that part works

but it doesnt work in reverse... if i wanna put files in user folders files from unraid server.. like using Krusader and copy a bunch of documents or pictures.. to several user folders... it does not sync doesnt show up when you log in.. it doesnt even recongize files are in the files folder... how you supposed to get the software to see files you copy in folders from the server side... not the client side

ownCloud doesn't normally track files added, deleted, or moved on the server side. Files are only tracked when added, deleted, and moved from the ownCloud interface - either by sync'ing or the through the UI. You'll cause database issues by managing files on the server side.

Use the ownCloud app 'Files Clipboard' to manage files and folders in the ownCloud UI.

ah ok as i trying this own cloud i was hoping a way to have like ZimaOS client does and when you log into the app.. it maps a drive letter to the files.. but also be able to specific user folders like /mnt/user/family files/user name but one they dont do multi user.. and own cloud so far cant do outside of the /owncloud directory..

trying to find best app that can do that

p fil

so basiclly if i want to copy say a document off the unraid server to 10 users i log into everyones account and drop files in.. as i figured admin account would have access to all the users files too so i can just copy to users folders... but looks like it doesnt do 100% what i wanna do..

ill play with this program and try other programs too as i wanted also if i the admin i wanted root share of the entire share folders.... but i appreciate it .. cant do what i orginally thought i could do...

3 minutes ago, comet424 said:

ah ok as i trying this own cloud i was hoping a way to have like ZimaOS client does and when you log into the app.. it maps a drive letter to the files.. but also be able to specific user folders like /mnt/user/family files/user name but one they dont do multi user.. and own cloud so far cant do outside of the /owncloud directory..

trying to find best app that can do that

p fil

so basiclly if i want to copy say a document off the unraid server to 10 users i log into everyones account and drop files in.. as i figured admin account would have access to all the users files too so i can just copy to users folders... but looks like it doesnt do 100% what i wanna do..

ill play with this program and try other programs too as i wanted also if i the admin i wanted root share of the entire share folders.... but i appreciate it .. cant do what i orginally thought i could do...

ownCloud is not a front end to your array files.

ah ok ya i was hoping for like a backup for each user to

/mnt/user/family files/user 1

/mnt/user/family files/user 2

/mnt/user/family files/user 3

and when i rysnc files to those locations or just copy to it.. then each file sees that file.. when they login to backup there files..

is there backup docker app that you know of that does that? i asked in the General Forum a couple weeks ago but no one ever replied.. so i just been trial erroring what google says and then i try to see if unraid apps has the community app for it

Tailscale support added

The ownCloud container now supports Tailscale for secure remote access without requiring public DNS, router port forwarding, a static public IP address, or a publicly managed SSL certificate.

I have tested the following through Tailscale:

• ownCloud browser access

• ownCloud Android application access

• File uploads and synchronization

• Tailscale-managed HTTPS certificates

Because ownCloud uses an internally generated self-signed certificate, set the Tailscale Serve Target to:

https+insecure://localhost

The Tailscale WebUI and client URLs must not include the container’s :8443 port. Including the port connects directly to ownCloud and presents its self-signed certificate instead of the trusted Tailscale certificate.

The container’s Tailscale hostname must also be added manually to the trusted_domains array in ownCloud’s config.php.

Complete setup, client configuration, certificate, and rollback instructions have been added to the first post in this thread.

PHP2Shell (CVE-2026-109618/-109619) and PHP 7.4

Hi @dlandon , thank you for keeping this container going all these years. I have one security issue to raise and a couple of questions.

PHP2Shell is an unauthenticated remote-code-execution bug in PHP itself, disclosed on 2026-10-21 (php.net). ownCloud has confirmed it affects ownCloud Classic (ownCloud).

The current image (built 2026-09-11) ships php7.4-fpm 1:7.4.33-30 from the ondrej/php PPA, which predates the fix. The PPA's fixed build, 1:7.4.33-31, has been out since 2026-10-21 (Launchpad).

For anyone running this container:

1. Restart it. With AUTO_OS_UPDATES=1, which is the default, the restart installs the fixed build.

2. Check with: docker exec ownCloud dpkg-query -W php7.4-fpm
   It should show 1:7.4.33-31 or newer.

3. If you have auto-updates off, or run the :legacy tag ("no more updates"), you won't get the fix. Please keep the container off the open Internet until you have it.

Three suggestions, if you have a moment:

1. Rebuild now so the image ships the fixed PHP. A build started after 2026-10-21 gets -31 from the same PPA (Launchpad). This can also be guarded so that a cached layer can never ship the old build again. ownCloud's own first "patched" image shipped -30 by mistake (discussion):
   RUN apt-get update && apt-get install -y --only-upgrade 'php7.4*' && dpkg --compare-versions "$(dpkg-query -W -f='${Version}' php7.4-fpm)" ge 1:7.4.33-31

2. Point fresh installs at the current 10.16.x. owncloud-complete-latest still downloads 10.16.0 from 2025-11 (download.owncloud.com), while 10.16.6 is current (ownCloud).

3. Consider ownCloud 11 on PHP 8.3 as the way off PHP 7.4. ownCloud 11.0.0 was released on 2026-07-30 and requires PHP 8.3 (release). Ubuntu 24.04 ships PHP 8.3 with security support, so the PPA wouldn't be needed. ownCloud's own 11.0.1 image gets this fix that way (discussion). It upgrades from 10.x, though it is a major release with breaking changes (notes). It also removes the built-in updater app, which settles the updater problem from earlier in this thread.

About the built-in updater (the 504 at "Creating a checkpoint", page 19): I reproduced it and found the cause. The .php location in the shipped nginx site config has no fastcgi_read_timeout, so nginx gives up after its default of 60 seconds (nginx docs). The web updater runs each step as one request, and the checkpoint step copies the whole ownCloud tree, which easily takes longer than that on appdata. In my test, adding fastcgi_read_timeout 3600; let the full web update from 10.15.2 to 10.15.3 complete. Details for users and for the image:

• Workaround for existing installs (the site config in appdata is persistent):
  docker exec ownCloud bash -c 'f=/config/nginx/site-confs/default; grep -q fastcgi_read_timeout $f || sed -i "/fastcgi_pass php-handler;/a\ fastcgi_read_timeout 3600;" $f; nginx -t && nginx -s reload'

• The updater also needs to write to the whole webroot. 60_get_owncloud.sh resets it to root:abc on every start, so "Checking System" can fail until docker exec ownCloud chown -R abc:abc /config/www/owncloud is run. That has to be repeated after each restart.

• The command-line updater avoids nginx entirely. It took 10.15.2 to 10.15.3 in 20 seconds:
  printf '1\n' | docker exec -i ownCloud /sbin/setuser abc php /config/www/owncloud/updater/application.php upgrade:start

• Suggested image change: add the timeout line to /defaults/default, and have 40_set_config.sh add it to existing copies if it's missing. The same grep -q … || sed -i … as above does that.

• The updater calls the instance at its own address. With the self-signed certificate it only skips the certificate check for localhost, so opening ownCloud by LAN IP fails with cURL error 60. This matches the certificate note in the first post.

Thanks again for your work.

Edited October 23Oct 23 by Samsonight
typo

Thanks for the detailed report and for identifying the PHP issue.

I’m rebuilding the existing container so the PHP security fixes are included in the image. I’m also adding a build-time version check to prevent an image from being built with the vulnerable PHP package. Users with automatic OS updates enabled should restart their container and verify the installed php7.4-fpm version.

Moving to a PHP 8.2-based ownCloud image is a separate effort. It will require compatibility testing, so I’m keeping this security rebuild on the existing PHP version while I evaluate that change.

I also saw your report about the web updater timing out while creating a checkpoint. I haven’t addressed that in this rebuild; I’ll review the nginx timeout handling separately.

I recommend using the container’s Tailscale support to access ownCloud privately, rather than exposing it directly to the Internet.

After updating the container, you can verify the installed versions with:

docker exec ownCloud dpkg-query -W -f='${Package} ${Version}\n' php7.4-fpm libapache2-mod-php7.4

Please hold off on upgrading existing ownCloud installations to 11.x

I’m developing a new container that will support both existing installations and new ownCloud 11.x installations. Please don’t manually upgrade an existing installation to ownCloud 11.x until the new image and its migration instructions are ready. The current container is built around ownCloud 10.x, PHP 7.4, and MariaDB 10.6. Changing the ownCloud version before the container can provide the matching PHP and database runtimes could leave the installation unable to start.

The plan is to use one image that selects the PHP runtime based on the installed ownCloud version. A new installation will start with ownCloud 11.x, PHP 8.3, and MariaDB 10.11. Existing installations can continue using their ownCloud 10.x version, PHP 7.4, and MariaDB 10.6 until the user chooses to upgrade. Both PHP versions will be included in the image, avoiding a lengthy PHP installation during container startup.

The ownCloud application upgrade and the MariaDB engine migration will be deliberate user actions. The container will not silently migrate an existing database. I’ll provide instructions for backing up and migrating the database when the image is ready.

Edited October 25Oct 25 by dlandon

14 hours ago, dlandon said:

Please hold off on upgrading existing ownCloud installations to 11.x

I’m developing a new container that will support both existing installations and new ownCloud 11.x installations. Please don’t manually upgrade an existing installation to ownCloud 11.x until the new image and its migration instructions are ready. The current container is built around ownCloud 10.x, PHP 7.4, and MariaDB 10.6. Changing the ownCloud version before the container can provide the matching PHP and database runtimes could leave the installation unable to start.

The plan is to use one image that selects the PHP runtime based on the installed ownCloud version. A new installation will start with ownCloud 11.x, PHP 8.3, and MariaDB 10.11. Existing installations can continue using their ownCloud 10.x version, PHP 7.4, and MariaDB 10.6 until the user chooses to upgrade. Both PHP versions will be included in the image, avoiding a lengthy PHP installation during container startup.

The ownCloud application upgrade and the MariaDB engine migration will be deliberate user actions. The container will not silently migrate an existing database. I’ll provide instructions for backing up and migrating the database when the image is ready.

Thanks a lot ! Kudos to you.

I'm working on a new container that will handle the existing ownCloud installations and install ownCloud 11 and MariaDB 10.11 for new installs. The new container will keep an existing ownCloud version and MariaDB 10.6 as it is. You can then update the MariaDB to 10.11 and ownCloud to 11.x when you are ready. Owncloud recommends you are updated to ownCloud 10.16.x before updating to ownCloud 11.x.

The new container will adjust the php version to what the installed ownCloud version requires. I believe the best migration path for minimal probems would be:

• Make a backup of your appdata/ownCloud/ directory before performing any update.

• Update the docker container when it is avaiable. This step by itself addresses the latest php security issues but leaves you using php 7.4 that is at EOL. Run ownCloud for a while to be sure there are no issues.

• Update the MariaDB database to 10.11. This step updates MariaDB to the latest supported version. Again, run ownCloud for a while to be sure there are no issues.

• Update to ownCloud 11.x. This step updates to php 8.3 and off of php 7.4 that is EOL.

The upgrade for MariaDB and ownCloud are documented in the second post of this forum thread. The steps may change before final release of the updated container. I have done some initial testing and the steps all worked. I'll release a new ownCloud container after some more testing.

Edited October 25Oct 25 by dlandon

I've been testing the new docker container and it is looking good. The one thing I find after upgrading my test server to ownCloud 11 is that there are a lot of apps I use like the 'Next Backup' that are not compatible with ownCloud 11 yet. I will hold off upgrading to ownCloud 11 until more of the apps are updated. You should evaluate what apps you use and see if they are ownCloud 11 ready before making the upgrade to ownCloud 11. You can check them at the ownCloud Marketplace here.

Edited October 26Oct 26 by dlandon

I released a new docker container. My main server ownCloud updated and is running.
*** Running /etc/my_init.d/30_redis_server.sh...

Starting redis-server: redis-server.

*** Running /etc/my_init.d/40_get_owncloud.sh...

*** Running /etc/my_init.d/50_set_config.sh...

*** Running /etc/my_init.d/60_gen_ssl_keys.sh...

[ssl] Generating self-signed keys in /config/keys (missing/empty cert/key), you can replace these with your own keys if required

[ssl] Self-signed certificate generated (valid 825 days, SAN=localhost/127.0.0.1)

*** Running /etc/my_init.d/70_initialize_database.sh...

*** Running /etc/my_init.d/80_first_run.sh...

Oct 30 10:47:33 8d8f31f9381f crontab[644]: (root) REPLACE (root)

ownCloud startup: PHP 7.4.33 <=================

*** Running /etc/my_init.d/999_advanced_script.sh...

*** Booting runit daemon...

*** Runit started as PID 651

Oct 30 10:47:33 8d8f31f9381f cron[658]: (CRON) INFO (pidfile fd = 3)

Oct 30 10:47:33 8d8f31f9381f cron[658]: (CRON) INFO (Skipping @reboot jobs -- not system startup)

ownCloud startup: MariaDB 10.6.23-MariaDB-0ubuntu0.22.04.1-log <=================

261030 10:47:33 mysqld_safe Logging to '/config/database/8d8f31f9381f.err'.

261030 10:47:33 mysqld_safe Starting mariadbd daemon with databases from /config/database

Notice the two highlighted log lines. These give you the php and database versions running on your system. I will wait a while before updating my database. I won't update ownCloud until the apps I use are updated to run on ownCloud 11. Again I caution you that updating to ownCloud 11 with get php 8.3, but the apps not being updated may limit your ability to use ownCloud as you wish.

I updated MariaDB on my main instance of ownCloud and after an update and a restart this is the log:
ownCloud startup: PHP 7.4.33

*** Running /etc/my_init.d/999_advanced_script.sh...

*** Booting runit daemon...

*** Runit started as PID 692

Oct 31 07:28:24 ccc2338ece1c cron[699]: (CRON) INFO (pidfile fd = 3)

Oct 31 07:28:24 ccc2338ece1c cron[699]: (CRON) INFO (Running @reboot jobs)

ownCloud startup: MariaDB 10.11.19-MariaDB-log

261031 07:28:24 mysqld_safe Logging to '/config/database/ccc2338ece1c.err'.

261031 07:28:24 mysqld_safe Starting mariadbd daemon with databases from /config/database

mysqld is alive

Oct 31 07:28:29 ccc2338ece1c mariadb: MariaDB system-table upgrade completed.

Oct 31 07:28:29 ccc2338ece1c mariadb: This installation of MariaDB is already upgraded to 10.11.19-MariaDB.

Oct 31 07:28:29 ccc2338ece1c mariadb: There is no need to run mysql_upgrade again.

Oct 31 07:28:29 ccc2338ece1c mariadb: You can use --force if you still want to run mysql_upgrade

You can see php 7.4.33 and MariaDB 10.11.19. The last step to get to supported php 8.x will come when I update to ownCloud 11. Until the apps are compatible, I will hold off on that. Too many are not yet compatible.

@Samsonight Hopefully this addresses your concerns about ownCloud security and EOL php and MariaDB. Thanks for letting me know about these issues with the ownCloud container.