6 hours ago, Kilrah said:

I've done it back in the day so it's possible, but LSIO have their own standard paths so you have to move stuff around. I.e. recreating the lsio paths in this won't work, I'd recommend you make a clean, separate install of this one in another folder so you can look at where stuff is and move the old LSIO appdata accordingly.

Got it.  Do you think this would work?

 

1. dump existing database to .bak file via mysqldump

2. rename current /data folder with all my files to /data2

3. install your container clean, with it's different /appdata path, /data folder, and a new mariadb database container

4. /move files from /data2 to /data

5. import database dump

There should be no need to recreate either the database or the appdata folder. Of course back everything up before the migration though.

 

It's the appdata that's mapped differently and needs adjusting.

Also permissions are different, this container runs as user:group 33:33 by default, so you'd have to either change the owner user:group to that on data and appdata or specify the same user:group as LSIO in extra parameters.

On 1/24/2025 at 3:16 PM, Kilrah said:

There should be no need to recreate either the database or the appdata folder. Of course back everything up before the migration though.

 

It's the appdata that's mapped differently and needs adjusting.

Also permissions are different, this container runs as user:group 33:33 by default, so you'd have to either change the owner user:group to that on data and appdata or specify the same user:group as LSIO in extra parameters.

I was able to get it running and on first appearances it seems mostly okay.  I forgot to start with v29 and after launching the latest version successfully going back to v29 I was getting no gui (though no errors showing in the console).  So I went back to latest and did a cli upgrade.  I think I can resolve the security and setup issues reported in the Overview screen.  One odd thing though, is that when I do go to the console, I get something like:

 

I have no name!@5cbf7e44702e:/var/www/html$

I have no name!@5cbf7e44702e:/var/www/html$ whoami
whoami: cannot find name for user ID 99

 

Any ideas on what would be causing that and how to resolve it?

 

Edited January 27, 20251 yr by BurntOC

Also, speaking of tags, do you recommend the fpm or regular image? I'm running a reverse proxy and thinking fpm might be better in that case?

Edited January 27, 20251 yr by BurntOC

4 hours ago, BurntOC said:

whoami: cannot find name for user ID 99

 

Any ideas on what would be causing that and how to resolve it?

The user in the standard NC container is 33. You probably added the user=99:100 to get the correct permissions, that'll work, if you don't want that error remove it and chown the data/appdata to 33:33.

 

4 hours ago, BurntOC said:

Also, speaking of tags, do you recommend the fpm or regular image?

I don't know anything about fpm, sorry. 

When I had this problem two things I did fixed this issue

 

1-Turn off the container, then Run the "Docker Safe New Perms" on the TOOLS section of Unraid

2-Add the line 'check_data_directory_permissions' => false, in the config.php file in the config directory

/mnt/user/appdata/nextcloud-ffmpeg/config

Greetings,

the upgrade from 30.0.6.2 to 31 doesnt work as the version seems incorrect in your build.

Can't start Nextcloud because the version of the data (
Warning: PHP Startup: Unable to load dynamic library 'pdlib.so' (tried: /usr/local/lib/php/extensions/no-debug-non-zts-20230831/pdlib.so (/usr/local/lib/php/extensions/no-debug-non-zts-20230831/pdlib.so: cannot open shared object file: No such file or directory), /usr/local/lib/php/extensions/no-debug-non-zts-20230831/pdlib.so.so (/usr/local/lib/php/extensions/no-debug-non-zts-20230831/pdlib.so.so: cannot open shared object file: No such file or directory)) in Unknown on line 0
30.0.6.2) is higher than the docker image version (
Warning: PHP Startup: Unable to load dynamic library 'pdlib.so' (tried: /usr/local/lib/php/extensions/no-debug-non-zts-20230831/pdlib.so (/usr/local/lib/php/extensions/no-debug-non-zts-20230831/pdlib.so: cannot open shared object file: No such file or directory), /usr/local/lib/php/extensions/no-debug-non-zts-20230831/pdlib.so.so (/usr/local/lib/php/extensions/no-debug-non-zts-20230831/pdlib.so.so: cannot open shared object file: No such file or directory)) in Unknown on line 0
31.0.0.18) and downgrading is not supported. Are you sure you have pulled the newest image version?

 

It does update from the official container, but then doesnt start when i switch back to nextcloud-ffmpeg:31. I removed the Warning in this one.

Can't start Nextcloud because the version of the data (31.0.0.18) is higher than the docker image version (31.0.0.18) and downgrading is not supported. Are you sure you have pulled the newest image version?

 

and also a thank you for this container too.

Should be fixed

FYI, updating to Hub 10 (V31) seems to have gone smoother than from V29 to V30 for me.

 

=================================

Initializing nextcloud 31.0.0.18 ...
Upgrading nextcloud from 30.0.6.2 ...

 

..
[Fri Mar 14 13:16:43.945450 2025] [mpm_prefork:notice] [pid 1:tid 1] AH00163: Apache/2.4.62 (Debian) PHP/8.3.17 configured -- resuming normal operations
[Fri Mar 14 13:16:43.945487 2025] [core:notice] [pid 1:tid 1] AH00094: Command line: 'apache2 -D FOREGROUND'

==================================
 

After updating to Nextcloud 10 from the latest Nextcloud 9 build, my protocols are full with this error:

[PHP] Fehler: Declaration of Psr\Log\AbstractLogger::emergency($message, array $context = []) must be compatible with Psr\Log\LoggerInterface::emergency(Stringable|string $message, array $context = []): void at /var/www/html/custom_apps/workflow_kitinerary/vendor/psr/log/Psr/Log/AbstractLogger.php#22
	GET /remote.php/dav/
	von 127.0.0.1 von ? um 17.03.2025, 21:28:14

 

In the backend overview, there are multiple errors referring to WebDAV as the problem source, although i never had any issue with this at any time:

- Dein Webserver ist noch nicht hinreichend für Datei-Synchronisierung konfiguriert, da die WebDAV-Schnittstelle vermutlich nicht funktioniert. Damit diese Prüfung ausgeführt werden kann, muß sichergestellt sein, dass der Webserver eine Verbindung zu sich selbst herstellen kann. Daher muss er in der Lage sein, mindestens eine seiner `trusted_domains` oder `overwrite.cli.url` aufzulösen und eine Verbindung zu ihnen herzustellen. Dieser Fehler kann das Ergebnis einer serverseitigen DNS-Nichtübereinstimmung oder einer ausgehenden Firewall-Regel sein.
- Der Webserver ist nicht ordnungsgemäß für die Auflösung von `.well-known`-URLs eingerichtet. Fehler bei: `/.well-known/caldav` Weitere Informationen findest du in der Dokumentation ↗.
- 143 Fehler in den Protokollen seit 10. März 2025, 21:50:53

 

in my htaccess inside the nextcloud folder, there is the following block regarding .well-known calls:

<IfModule mod_rewrite.c>
  RewriteEngine on
  RewriteCond %{HTTP_USER_AGENT} DavClnt
  RewriteRule ^$ /remote.php/webdav/ [L,R=302]
  RewriteRule .* - [env=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
  RewriteRule ^\.well-known/webfinger /index.php/.well-known/webfinger [R=301,L]
  RewriteRule ^\.well-known/nodeinfo /index.php/.well-known/nodeinfo [R=301,L]
  RewriteRule ^\.well-known/carddav /remote.php/dav/ [R=301,L]
  RewriteRule ^\.well-known/caldav /remote.php/dav/ [R=301,L]
  RewriteRule ^remote/(.*) remote.php [QSA,L]
  RewriteRule ^(?:build|tests|config|lib|3rdparty|templates)/.* - [R=404,L]
  RewriteRule ^\.well-known/(?!acme-challenge|pki-validation) /index.php [QSA,L]
  RewriteRule ^ocm-provider/?$ index.php [QSA,L]
  RewriteRule ^(?:\.(?!well-known)|autotest|occ|issue|indie|db_|console).* - [R=404,L]
</IfModule>

 

As far as i know, the server is not restricted by a firewall or by the router, pinging my nextcloud-domain from the unraid prompt gets answers all the time.

I really don't understand what happens here. Does anyone have any idea?

1 hour ago, Gekko said:

After updating to Nextcloud 10 from the latest Nextcloud 9 build, my protocols are full with this error:

[PHP] Fehler: Declaration of Psr\Log\AbstractLogger::emergency($message, array $context = []) must be compatible with Psr\Log\LoggerInterface::emergency(Stringable|string $message, array $context = []): void at /var/www/html/custom_apps/workflow_kitinerary/vendor/psr/log/Psr/Log/AbstractLogger.php#22
	GET /remote.php/dav/
	von 127.0.0.1 von ? um 17.03.2025, 21:28:14

 

 

Looks like that app is not compatible with 31 yet, might be why. 

 

 

It's never a good idea to use latest/default with nextcloud, often when a new version comes out apps take a few weeks/months to get updated for it, if they do. Should always pin to a major version e.g. :30 and watch for the incompatible app list in admin settings before switching, resp. make a test install to see if forcing those to install actually works or causes issues. My instance is still on 30 because while most of those below seem to actually work on 31 draw.io doesn't and I need it. 

 

 

1 hour ago, Gekko said:

in my htaccess inside the nextcloud folder, there is the following block regarding .well-known calls:

If you're reverse-proxying that needs to be configured to pass it, e.g.

 

 

 

 

Edited March 17, 20251 yr by Kilrah

Thank you Kilrah for answering so swiftly...i really love your Nextcloud version!

 

When deactivating the workflow app, all related issues disappear - for me, it's not a serious issue pausing the app until an update is provided. Regarding the error messages i thought there might be some deeper layer of problems ocurring through a basic misconfiguration of WebDAV services. Thank you for your help!

 

This might be some very basic question, but i really don't know the answer: is there a way to determine what version will be installed when the Action Center in unraid alerts a new version of Nextcloud being available?

10 minutes ago, Gekko said:

This might be some very basic question, but i really don't know the answer: is there a way to determine what version will be installed when the Action Center in unraid alerts a new version of Nextcloud being available?

You could look at https://hub.docker.com/repository/docker/kilrah/nextcloud-ffmpeg/tags?page=1

 

If you specify no tag it'll be "latest", which if you look at the hashes currently matches 31.0.1

 

if you specify the repository line as e.g. kilrah/nextcloud-ffmpeg:30 then it'll only get updates for the 30 branch and not move to 31 until you change it (recommended). If you want a very specific version you'd specify e.g :30.0.0

running the linuxserver version right now, i added the rules below to the config.php but previews are still not working for videos.(yes i tried a restart of the container) I want to switch over to this docker. Can i just replace the repository or should i go the long way around and move everything config based?

 

  'enable_previews' => true,

  'preview_max_x' => 800,

  'preview_max_y' => 600,

  'enabledPreviewProviders' =>

  array (

    0 => 'OC\\Preview\\IMAGE',

    1 => 'OC\\Preview\\MOVIE',

    2 => 'OC\\Preview\\GIF',

    3 => 'OC\\Preview\\BMP',

    4 => 'OC\\Preview\\XBitmap',

    5 => 'OC\\Preview\\MP3',

    6 => 'OC\\Preview\\TXT',

    7 => 'OC\\Preview\\MarkDown',

    8 => 'OC\\Preview\\OpenDocument',

    9 => 'OC\\Preview\\PDF',

    10 => 'OC\\Preview\\MP4',

    'preview_max_memory' => 1024,

    'preview_max_x' => NULL,

    'preview_max_y' => NULL,

    'preview_max_filesize_image' => 400,

    11 => 'OC\\Preview\\MOV',

    12 => 'OC\\Preview\\MKV',

    13 => 'OC\\Preview\\HEIC',

    14 => 'OC\\Preview\\JPEG',

    15 => 'OC\\Preview\\PNG',

    16 => 'OC\\Preview\\AVI',

  ),

Been a while since I looked at the LSIO container but AFAIK folders are arranged differently. If you do a test fresh install of this one to see where the folders are and copy the ones from your container to the right places it should work. You'll probably have to adjust file/folder ownership too. 

Good evening!

 

I have Nextcloud version 31.0.4 installed and am having trouble displaying images taken with an iPhone and iOS 18. Is there a solution?

I read that libheif needs to be updated to version 1.18.0.
But I also read something about Alpine being updated to 3.21 as the underlying framework, which should automatically have the latest version of libheif.

 

Can anyone help me see my pictures in Nextcloud again?

 

Thanks!

On 5/13/2025 at 11:39 PM, SidM said:

Can anyone help me see my pictures in Nextcloud again?

Update, should work again on v30 and 31.

Edited May 15, 20251 yr by Kilrah

6 hours ago, Kilrah said:

Update, should work again on v30 and 31.

Great! Thank you so much! It's working again!

Hi, how did you update / manage to get heic preview working again?

Simply update the container.

Thank you, already did after reading the posts above.

 

It says up-to-date but still having errors with it:

 

Log:

 

Error:

core ImagickExceptionFailed to read the file

File: /Goddy/files/Photos/2025/05/16/25-05-16 00-18-32 0727.heic Imagick says:

 

Any ideas?

That's barely readable but it looks like you're not using my image this thread is about.

Edited May 16, 20251 yr by Kilrah

@Kilrah I want to say thank you for keeping up with maintenance on this image. I have been using for the past couple of years and it is going strong.

Can you point me in the right direction how to enable HTTPS with self signed certificates?

No idea, I always use a reverse proxy.

hello,what a nice image!

btw.ever considering add cuda support for dlib and tensorflow?