Another one... cURL error 60

Expected behaviour

Should be able to display content

Actual behaviour

“No marketplace connection: cURL error 60: SSL certificate problem: certificate has expired” displayed and no content on marketplace.

Server configuration

Operating system:
root@xyz:/var/www/htmll# uname -a
Linux b2ef29b1dec6 5.10.0-25-amd64 #1 SMP Debian 5.10.191-1 (2023-08-16) x86_64 GNU/Linux

ownCloud version: (see ownCloud admin page)

Updated from an older ownCloud or fresh install:
No, fresh installation

Where did you install ownCloud from:
Used this “quick” guide: htt ps://

Signing status (ownCloud 9.0 and above):

The content of config/config.php:

<?php $CONFIG = array ( 'instanceid' => 'ocex2mx03fw5', 'passwordsalt' => '4GWKSrVAQ/PtTq8YD5JqjkrBGa3s6x', 'secret' => 'oXadqHbv//R0x40eO5/dRWISVwxUhMzQsEOlK00RIllZocB+', 'trusted_domains' => array ( 0 => 'DOMAIN.NAME', ), 'datadirectory' => '/var/www/html/data', 'overwrite.cli.url' => 'http://DOMAIN.NAME', 'dbtype' => 'sqlite3', 'version' => '', 'logtimezone' => 'UTC', 'installed' => true, 'proxy'=>'DOMAIN.NAME:8080' ); ### Problem Description Generally, OwnCloud seems to work just fine. If I try to access the Marketplace integration it displays the "curl error 60" error as shown above. I am using the (I suppose) official "stable" files in my Docker container. The whole installation is behind a ReverseProxy that has access to the internal and external networks. My Docker PC can access the > `htt ps://` website, but the docker container doesn't seem to be able to and instead throws this error. I know this error gets reported often and the closest issue to mine was this one: > `htt ps://` - And yes, I tried the DST Root CA X3 thing too, but to no avail. If somebody knows why I can't access the marketplace, please let me know so I can take action...

Here is the output of curl -LI from inside the docker container:

root@xyz:/var/www/html# curl -LI
curl: (60) SSL certificate problem: certificate has expired
More details here:

curl performs SSL certificate verification by default, using a "bundle"
 of Certificate Authority (CA) public keys (CA certs). If the default
 bundle file isn't adequate, you can specify an alternate file
 using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
 the bundle, the certificate verification probably failed due to a
 problem with the certificate (it might be expired, or the name might
 not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
 the -k (or --insecure) option.

vs Outside the docker container:

DockerUser@OutsideOfContainer:~$ curl -LI
HTTP/2 200
accept-ranges: bytes
cache-control: max-age=0, no-store
content-security-policy: default-src 'self'; img-src minio:9000 * * data: 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' data:; style-src 'unsafe-inline' 'self'; font-src 'self'; frame-src *
content-type: text/html; charset=UTF-8
date: Mon, 25 Sep 2023 21:57:52 GMT
etag: "4ac-5f02ac6f83040"
last-modified: Mon, 19 Dec 2022 09:16:41 GMT
referrer-policy: strict-origin-when-cross-origin
server: Apache
strict-transport-security: max-age=315360000; preload
vary: Accept-Encoding
x-content-type-options: nosniff
x-frame-options: SAMEORIGIN
x-xss-protection: 0
content-length: 1196

I see there are some newer versions available… how can I update this container? with the official docs I wasnt able to set it up that easily as in the one I posted above.

My Version seems to be and newer versions seem to be named like 10.11.x… how can I update manually? Will it fix my issue from above?

I will RTFM tomorrow :smiley: