Settings > Privacy > Encryption not saved on fresh NC 19 install

[mjog]

Changing the Settings > Privacy > Encryption setting as admin user is not saved on fresh NC 19 install.

Steps to reproduce

1. Log in as admin user
2. Go to Settings > Privacy > Encryption, click edit button
3. Tick the "This server is using full-disk encryption" checkbox

Expected behaviour

On reload, "This server is protected with full-disk-encryption" is displayed.

Actual behaviour

On reload, "You files are not protected by encryption" is displayed

Server configuration

Operating system: Debian 10

Web server: Apache 2.4.38

Database: Maria 10.3.22

PHP version: 7.3

Nextcloud version: 19.0.0

Updated from an older Nextcloud/ownCloud or fresh install: Fresh

Where did you install Nextcloud from: Downloaded tar.gz

[ph00lt0]

Same issue is present in the snap image.

[georgehrke]

Please fill the entire issue template and provide logs as well ...

[ph00lt0]

It's the LTS snap, running on Ubuntu 20. All other versions are controlled by the snap, so I see no point filling the full template.

[georgehrke]

Unless you fill out the issue template completely including all logs, we can't go ahead and help you. If no one is able to provide logs, this issue will automatically be closed in 21 days.

[ph00lt0]

@georgehrke sounds like a policy closing issues of bugs that are in current LTS lol. There are no error logs on this.

[georgehrke]

@ph00lt0 Did you check the browser log?

[ph00lt0]

If you mean console log, nothing to see there other then deprecated jquery version warning.

[georgehrke]

Can you still fill the issue template please? I need config.php, enabled apps, etc.

[ph00lt0]

No enabled apps other then default, config is just directly as in snap I just installed a clean installation of nextcloud snap.

[jonknud]

Hello Together,
I have the same problem with a fresh install of nextcloud via docker (nextcloud:19-fpm). How can I help to solve this? Where can I find the issue template? I coundn't find it though google.

[aszlig]

The regression is in c0615e3, where on the frontend the values for fullDiskEncryptionEnabled and serverSideEncryptionEnabled were matched against the string '1' and are now matched against the integer 1.

However, the backend was (and is) still returning strings.

So the fix for this is to either change the comparison on the frontend to use strings or the backend to emit integers instead.