• Plesk Uservoice will be deprecated by October. Moving forward, all product feature requests and improvement suggestions will be managed through our new platform Plesk Productboard.
    To continue sharing your ideas and feedback, please visit features.plesk.com

Resolved DNF makecache failed after 18.0.71 u1

OverWolf

Regular Pleskian
Server operating system version
AlmaLinux 9.6
Plesk version and microupdate number
18.0.71 #1
Hi,
I'm on AlmaLinux 9.6 and after update from 18.0.69 to 18.0.70u1 I have this error :

MariaDB 11 kB/s | 3.4 kB 00:00
PLESK_18_0_71 extras 1.6 kB/s | 3.0 kB 00:01
PHP 7.4 0.0 B/s | 0 B 00:30
Errors during downloading metadata for repository 'PLESK_17_PHP74':
- Curl error (28): Timeout was reached for https://ch.origin.autoinstall.plesk.com/PHP74_17/dist-rpm-RedHat-el9-x86_64/repodata/repomd.xml [Connection timed out after 30000 milliseconds]
Error: Failed to download metadata for repo 'PLESK_17_PHP74': Cannot download repomd.xml: Curl error (28): Timeout was reached for https://ch.origin.autoinstall.plesk.com/PHP74_17/dist-rpm-RedHat-el9-x86_64/repodata/repomd.xml [Connection timed out after 30000 milliseconds]
dnf-makecache.service: Main process exited, code=exited, status=1/FAILURE
dnf-makecache.service: Failed with result 'exit-code'.
Failed to start dnf makecache.
dnf-makecache.service: Consumed 8.515s CPU time.

Is this a possibile bug ?
 
Other strange thing is that after the update (yesterday) I cannot open Plesk UI via port 8447. This is very strange because I have opened it for upgrade to 18.0.71u1
 
Hello, @OverWolf . Kindly run the following command to perform a test with curl and let us know what's the outcome:

Bash:
curl -v https://ch.origin.autoinstall.plesk.com/PHP74_17/dist-rpm-RedHat-el9-x86_64/repodata/repomd.xml
 
Hi,
in this moment I have this result :
* Trying 195.214.233.207:443...
* Connected to ch.origin.autoinstall.plesk.com (195.214.233.207) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* CAfile: /etc/pki/tls/certs/ca-bundle.crt
* TLSv1.0 (OUT), TLS header, Certificate Status (22):
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS header, Certificate Status (22):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS header, Finished (20):
* TLSv1.2 (IN), TLS header, Unknown (23):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.2 (IN), TLS header, Unknown (23):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS header, Unknown (23):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.2 (IN), TLS header, Unknown (23):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.2 (OUT), TLS header, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS header, Unknown (23):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use http/1.1
* Server certificate:
* subject: CN=ch.origin.autoinstall.plesk.com
* start date: Jul 25 10:30:56 2025 GMT
* expire date: Oct 23 10:30:55 2025 GMT
* subjectAltName: host "ch.origin.autoinstall.plesk.com" matched cert's "ch.ori gin.autoinstall.plesk.com"
* issuer: C=US; O=Let's Encrypt; CN=E5
* SSL certificate verify ok.
* TLSv1.2 (OUT), TLS header, Unknown (23):
> GET /PHP74_17/dist-rpm-RedHat-el9-x86_64/repodata/repomd.xml HTTP/1.1
> Host: ch.origin.autoinstall.plesk.com
> User-Agent: curl/7.76.1
> Accept: */*
>
* TLSv1.2 (IN), TLS header, Unknown (23):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.2 (IN), TLS header, Unknown (23):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
* TLSv1.2 (IN), TLS header, Unknown (23):
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Date: Mon, 28 Jul 2025 17:58:05 GMT
< Server: Apache/2.4.58 (Ubuntu)
< Last-Modified: Tue, 07 May 2024 23:00:44 GMT
< ETag: "c09-617e527ebfa9d"
< Accept-Ranges: bytes
< Content-Length: 3081
< Cache-Control: max-age=86400
< Expires: Tue, 29 Jul 2025 17:58:05 GMT
< Vary: Accept-Encoding
< Content-Type: application/xml
<
<?xml version="1.0" encoding="UTF-8"?>
<repomd xmlns="http://linux.duke.edu/metadata/repo" xmlns:rpm="http://linux.duke .edu/metadata/rpm">
<revision>1715122844</revision>
<data type="primary">
<checksum type="sha256">cf8b775d765dde3892c925246d0bc6f722caa73659816d147c91 8f14f9904b61</checksum>
<open-checksum type="sha256">f0163a402aad9ba2d8a3e9c0de80777a64ad511a08f6fad 2dff03e279766d219</open-checksum>
<location href="repodata/cf8b775d765dde3892c925246d0bc6f722caa73659816d147c9 18f14f9904b61-primary.xml.gz"/>
<timestamp>1715122844</timestamp>
<size>9945</size>
<open-size>79481</open-size>
</data>
<data type="filelists">
<checksum type="sha256">7965edafde086065adf13ea8e8d8937f8ec3aa507b3719c56842 a907886444ec</checksum>
<open-checksum type="sha256">0eebef7246984100bb1026a0a4f41552dfc60eb075c860f 3d25e94e4bb1edb80</open-checksum>
<location href="repodata/7965edafde086065adf13ea8e8d8937f8ec3aa507b3719c5684 2a907886444ec-filelists.xml.gz"/>
<timestamp>1715122844</timestamp>
<size>10277</size>
<open-size>90677</open-size>
</data>
<data type="other">
<checksum type="sha256">b46253492506277ee541c74fe39da93fbfcec1d17fc8728a187d 8ab1f596b2a5</checksum>
<open-checksum type="sha256">5c5e7846489c891e2cab805dfb0dea027d43b545c3723d0 7fb8ca88e704e5bd0</open-checksum>
<location href="repodata/b46253492506277ee541c74fe39da93fbfcec1d17fc8728a187 d8ab1f596b2a5-other.xml.gz"/>
<timestamp>1715122844</timestamp>
<size>1945</size>
<open-size>7263</open-size>
</data>
<data type="primary_db">
<checksum type="sha256">7ef7433384db6b78c5788888b2e70f509a4b1f889d114bb241fd 18dfc03688ed</checksum>
<open-checksum type="sha256">505e7348061c1c9eb57b9bc00b0f536ab73049c21e0c261 8ef70071f837c23b5</open-checksum>
<location href="repodata/7ef7433384db6b78c5788888b2e70f509a4b1f889d114bb241f d18dfc03688ed-primary.sqlite.bz2"/>
<timestamp>1715122844</timestamp>
<size>20307</size>
<open-size>180224</open-size>
<database_version>10</database_version>
</data>
<data type="filelists_db">
<checksum type="sha256">ccb019e2b0594227ac65e30ba6d6657acae8e8352b45bee9ac28 8fa3c1843b85</checksum>
<open-checksum type="sha256">dd35cfe63059d0e80ab88f68eee086446fcb194f91d9d30 73153e9da5f064fc6</open-checksum>
<location href="repodata/ccb019e2b0594227ac65e30ba6d6657acae8e8352b45bee9ac2 88fa3c1843b85-filelists.sqlite.bz2"/>
<timestamp>1715122844</timestamp>
<size>20756</size>
<open-size>98304</open-size>
<database_version>10</database_version>
</data>
<data type="other_db">
<checksum type="sha256">7168f97ced42c5d74f15b96795b323476171dc90aa5413da335b b5a4efe1815b</checksum>
<open-checksum type="sha256">9be33fb62dbd967bab0b03a0691064941004d8bd6ed2a59 a8812dbad218eb048</open-checksum>
<location href="repodata/7168f97ced42c5d74f15b96795b323476171dc90aa5413da335 bb5a4efe1815b-other.sqlite.bz2"/>
<timestamp>1715122844</timestamp>
<size>2862</size>
<open-size>24576</open-size>
<database_version>10</database_version>
</data>
</repomd>
* Connection #0 to host ch.origin.autoinstall.plesk.com left intact
 
Thank you for the confirmation. It looks like curl successfully retrieves the file. Could you please re-attempt the update? It might have been a temporary connectivity issue. Please let us know in case the issue persists.
 
Back
Top