-
-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Expired certificate on federated share causes file list to be shown as empty #42755
Open
5 of 8 tasks
Labels
0. Needs triage
Pending check for reproducibility or if it fits our roadmap
28-feedback
bug
feature: federation
feature: files
Comments
joeysundotcom
added
0. Needs triage
Pending check for reproducibility or if it fits our roadmap
bug
labels
Jan 13, 2024
Can you provide the entire log entry/stack trace? Otherwise we're kind of flying blind here :) |
Sure. Here goes:
|
should be fixed by #48625 ? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
0. Needs triage
Pending check for reproducibility or if it fits our roadmap
28-feedback
bug
feature: federation
feature: files
Bug description
Hello,
I've stumbled upon some weird behaviour on my instance. The file list of the root folder would be shown as empty on the web interface. The +New button was also missing. I followed the log while reloading the page and it seems to crash with this error message:
Warning no app in context GuzzleHttp\Exception\RequestException: cURL error 60: SSL certificate problem: certificate has expired (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for
2024-01-13T19:01:24+00:00 https://FEDERATED-HOSTNAME-HERE/ocm-provider/ at .../guzzlehttp/guzzle/src/Handler/CurlFactory.php line 211
I do have a shared folder from federation. So contacted the admin of the other server and asked him to renew the certificate. As soon as that was done, everything went back to normal.
Steps to reproduce
Expected behavior
Dunno, but I guess an expired cert should not break the loading process. Instead, the icon or name of the folder could indicate disconnection.
Installation method
Community Manual installation with Archive
Nextcloud Server version
28
Operating system
Other
PHP engine version
PHP 8.1
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?
None
What user-backends are you using?
Configuration report
No response
List of activated Apps
No response
Nextcloud Signing status
No response
Nextcloud Logs
No response
Additional info
No response
The text was updated successfully, but these errors were encountered: