Open Majestic7979 opened 11 months ago
Please provide the full stack trace and/or immediately prior transaction that seems to trigger this message. Otherwise we're flying blind here...
Obviously redact filenames/users/domains as deemed appropriate.
Also, when did these start popping up in your logs precisely?
This happens on a brand new server....
I am facing the same issue. It came up, once the encryption module has been activated in app store and afterwards within the security settings. I have a fresh installed environment, no further users then the admin account. No files uploaded yet. Created for test purposes.
Same here: official docker container loaded from here, base version - apache
[encryption] Fatal: A public master key is available but the private key could not be found. This should never happen.
GET /ocs/v2.php/apps/notifications/api/v2/notifications
from 172.24.0.1 by admin at 2023-12-09T16:42:50+00:00
{"reqId":"Ap9txnJ9zahwX6FAzxqY","level":4,"time":"2023-12-09T16:42:50+00:00","remoteAddr":"172.24.0.1","user":"admin","app":"encryption","method":"GET","url":"/ocs/v2.php/apps/notifications/api/v2/notifications","message":"A public master key is available but the private key could not be found. This should never happen.","userAgent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:120.0) Gecko/20100101 Firefox/120.0","version":"27.1.4.1","data":{"app":"encryption"},"id":"6574a71ff3f6c"}
Anything else you need to investigate further?
Kind regards //neph
This issue has been automatically marked as stale because it has not had recent activity and seems to be missing some essential information. It will be closed if no further activity occurs. Thank you for your contributions.
Are you still needing a stack trace since it's a new server and others are experiencing the same issue?
⚠️ This issue respects the following points: ⚠️
Bug description
I am seeing this in the logs. Not sure what is causing it!? I have the encryption enabled in my settings. I am running the Docker container. Debian 12 host. 13th gen Intel i5 in case it's relevant due to AES extensions.
Steps to reproduce
Check the logs... Filter by Fatal. It's there.
Expected behavior
No error, since it says it should never happen.
Installation method
Community Docker image
Nextcloud Server version
27
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.2
Web server
Apache (supported)
Database engine version
MariaDB
Is this bug present after an update or on a fresh install?
None
Are you using the Nextcloud Server Encryption module?
Encryption is Enabled
What user-backends are you using?
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
Nothing else to add.