Files with umlauts are no longer displayed in Nextcloud 28

Support
1

NethServer Version: 8
Module: Nextcloud

I have integrated SMB shares from Nethserver8 as external storage in Nextcloud, unfortunately files containing umlauts are no longer displayed. In Nethserver7 and so far also in Nethserver8 I was able to solve the problem by adding the following entries in the config.php file.

‘force_language’ => ‘de’,
‘default_language’ => ‘de’,
‘default_locale’ => ‘de_DE’,
‘default_phone_region’ => ‘DE’,

After one of the last updates the problem has suddenly reappeared, although the entries in config.php are still there. Does anyone have any idea what else could be causing this? I would be very grateful for any tips.

Regards
Erwin

2

I can’t reproduce, files with umlauts are shown in Nextcloud external storage using Samba.

Did you migrate Nextcloud from NS7 or is it a fresh NC installation?

Are there errors in Samba or Nextcloud logs?

EDIT:

Do the umlauts work in normal Nextcloud folders? (not in the external storage samba folders)

3

HI

I have not seen this behaviour so far, neither at home or for clients.

And at home (and special cases at clients) I do have 1-2 folders directly on Nextcloud…
Most shares are samba shares.

My 2 cents
Andy

4

Hi @mrmarkuz, @Andy_Wismer,

Thank you very much for your reply.

I haven’t actually seen the problem for a long time and was wondering why it has suddenly reappeared.

Nextcloud was migrated from Nethserver7 to Nethserver8 and umlauts in Nextcloud folders are no Problem.

I also only use Samba shares and only one direct folder in Nextcloud. I have since done some testing and noticed the following.

If I create a file with umlauts on an SMB share in Nextcloud or on a Windows PC, then this file is visible.

I currently work a lot on my iPad Pro and have created and edited many files with umlauts and then copied them to the Samba shares. Exactly these files are not visible in Nextcloud and I don’t get any errors in the log files.

However, this is not always the case: if I transfer the file directly from the iPad to the Nextcloud app via File Sharing, it is also visible.

However, if I copy the files to the SMB shares via the FileBrowser app, these files are no longer visible. For another test, I copied the file via the FE File Explorer app, and the files are not visible here either.

Curiously, the affected files are still visible on a Windows PC, but not on my MacBook, which confuses me even more.

Through the many tests I have now at least found a workaround as to why this is the case, but it is completely unclear to me.

It would have been better off working on a Windows PC or a Mac, then I wouldn’t have encountered these problems at all.

Maybe this information will help someone who has the same problem, although it is very specific.

Regards

Erwin

1 Like
5

I don’t use Mac a lot but maybe it helps to check file permissions/attributes in the samba-dc container to find differences between shown and not shown files.

Enter samba-dc container:

runagent -m samba1 podman exec -ti samba-dc bash

In this example the files of share1 are listed:

ls -la /srv/shares/share1

Samba provides some enhancements for Mac, check out Configure Samba to Work Better with Mac OS X - SambaWiki

How to edit smb.conf in NS8:

6

@mrmarkuz The file permissions/attributes are the same, if I rename the file without umlauts, it is immediately visible.

I have tried the Mac enhancements, but unfortunately this means that the complete include.conf is no longer read correctly.

The error message appears in the log file

2024-10-23T11:15:35+02:00 [1:samba1:samba-dc] TLS …/…/source4/lib/tls/tls_tstream.c:1378 - Decryption has failed.

I added these entries.

vfs objects = fruit streams_xattr
fruit:metadata = stream
fruit:model = MacSamba
fruit:veto_appledouble = no
fruit:nfs_aces = no
fruit:wipe_intentionally_left_blank_rfork = yes
fruit:delete_empty_adfiles = yes
fruit:posix_rename = yes

Regards
Erwin

7

I have just seen that I get this error message more often, so it probably has nothing to do with the new entries in include.conf.

Nevertheless, the include.conf does not seem to work properly after the new entries, as the recycle bin no longer works. If I remove the new entries again, the recycle bin works perfectly again.

Am I doing something wrong with the entries in include.conf?

8

I have adjusted the include.conf, now the recycle bin still works, but I don’t know if the entries are correct?

vfs objects = fruit streams_xattr recycle
recycle: exclude_dir = /tmp,/temp,/Temp,/cache
recycle: repository = Recycle Bin
recycle: versions = True
recycle: keeptree = True
recycle: touch = True
recycle: directory_mode = 0770
recycle: exclude = .tmp,.temp,.o,.obj,~
fruit:metadata = stream
fruit:model = MacSamba
fruit:veto_appledouble = no
fruit:nfs_aces = no
fruit:wipe_intentionally_left_blank_rfork = yes
fruit:delete_empty_adfiles = yes
fruit:posix_rename = yes

9

It looks correct. I hope it helps with the umlauts…

10

@mrmarkuz Unfortunately it didn’t fix the problem, it’s somehow a very strange error. I don’t have the problem at all on a Windows PC and it also works on the Mac via the Finder. I have the biggest problem on the iPad and here I have a workaround to get around the problem, even if it is a bit more complicated.

At this point I should probably just accept it, unless you have any other ideas as to what the problem might be? Maybe it’s also a bug in iPadOS and MacOS.

Is there actually a way to include the following entries in the include.conf, which apparently only works for the Global section at the moment?

[share]
spotlight backend = elasticsearch

[TimeMachineBackup]
vfs objects = fruit streams_xattr
fruit:time machine = yes

Regards

Erwin

11

Another method is to use the samba registry:

12

Thank you, but this is now beyond my understanding, can you help me with exactly how to implement this?

13

Yes but please wait with adding the share config until this one is fixed else you may not be able to manage the shared folders from the UI anymore.

Here are example commands for adding your configuration.

net conf share "spotlight backend" elasticsearch

net conf setparm TimeMachineBackup "vfs objects" "fruit streams_xattr"
net conf setparm TimeMachineBackup "fruit:time machine" yes
1 Like
14

@mrmarkuz Many thanks for the sample configuration.

Unfortunately, I’ve just noticed that I can no longer access the shared folders in the UI, which I hadn’t noticed before. :exploding_head:

This probably already happened when creating the recycle bin in include.conf.

How can I fix this?

Regards
Erwin

15

You can remove the entries using following command:

net conf delparm ...

16

@mrmarkuz Many thanks for your support, I think I’ve got it working again.

Waiting for a fix now.

Regards
Erwin

1 Like