You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My Nextcloud is using an S3 instance with an SSL certificate from an organisation-internal CA imported to the container image.
While certain API calls to S3 work, others don't. The bug here is that Nextcloud seems to use different CA stores depending on how API calls are made: fopen() HTTPgazztle, curl?
Steps to reproduce
configure Nextcloud to use S3 object storage as primary storage with a host using a custom CA
launch nextcloud and notice that login does not work: error 50x
add a custom CA to the docker image (or host OS): /usr/local/share/ca-certificates/my-ca.crt
run update-ca-certificates
configure nextcloud to use S3 primary storage with a host using the custom CA
launch nextcloud and notice that login now works (also some avatar pictures are uploaded to the S3 objetc storage)
upload a file and notice that it does not end up in S3
Errors in the log:
Expected behavior
I expect that all nextcloud components apply consistently the same SSL settings unless explicitly stated otherwise (e.g. using the smtp stream options)
Nextcloud Server version
30
Operating system
Other
PHP engine version
None
Web server
None
Database engine version
None
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?
Default user-backend (database)
LDAP/ Active Directory
SSO - SAML
Other
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
No response
The text was updated successfully, but these errors were encountered:
@icewind1991@come-nc@kesselb I see you touched code related to the certification bundle before. Can you please tell me which cert bundle fopen() in the S3 classes is eventually using?
Bug description
My Nextcloud is using an S3 instance with an SSL certificate from an organisation-internal CA imported to the container image.
While certain API calls to S3 work, others don't. The bug here is that Nextcloud seems to use different CA stores depending on how API calls are made: fopen() HTTPgazztle, curl?
Steps to reproduce
Errors in the log:
Expected behavior
I expect that all nextcloud components apply consistently the same SSL settings unless explicitly stated otherwise (e.g. using the smtp stream options)
Nextcloud Server version
30
Operating system
Other
PHP engine version
None
Web server
None
Database engine version
None
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
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
No response
The text was updated successfully, but these errors were encountered: