Skip to main content

Upgrade Centos 7.9 to Almalinux , Tuxcare Error

flashex

Hi, my Centos 7.9 version is EOL and therefore while trying to update my server from Centos 7.9 to Almalinux, using the procedure indicated by cpanel, I receive this error during the checks.

2024-10-12 00:17:41 [ERROR] https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 403 - Forbidden

It looks like my Cpanel is not licensed with tuxcare Extended Lifecycle Support.

The license is provided by Hetzner.

How can I fix this to upgrade to Almalinux?

Comments

4 comments

Date Votes
  • cPRex Jurassic Moderator

    Hey there!  It sounds like you're running into the issue described here:

    https://support.cpanel.net/hc/en-us/articles/26988081123607-ELS-repo-returns-403-if-connections-use-IPv6

    Can you try adjusting that IPv6 setting and see if that takes care of things?

    0
  • LeGastronome
    • Edited

    Hello,

    I have the same error on my side, upgrade checker block on a 403 error at Tuxcare,

    seems that it's a auth access error? not ip V6 ?

    [ERROR] https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 403 - Forbidden
      Trying other mirror.

    curl -iLv https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/repomd.xml
    * About to connect() to repo.tuxcare.com port 443 (#0)
    *   Trying 2a01:4ff:f0:c5f1::1...
    * Connected to repo.tuxcare.com (2a01:4ff:f0:c5f1::1) port 443 (#0)
    * Initializing NSS with certpath: sql:/etc/pki/nssdb
    *   CAfile: /etc/pki/tls/certs/ca-bundle.crt
      CApath: none
    * SSL connection using TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
    * Server certificate:
    *       subject: CN=repo.tuxcare.com
    *       start date: Sep 02 08:12:57 2024 GMT
    *       expire date: Dec 01 08:12:56 2024 GMT
    *       common name: repo.tuxcare.com
    *       issuer: CN=R10,O=Let's Encrypt,C=US
    > GET /centos7-els/updates/x86_64/repodata/repomd.xml HTTP/1.1
    > User-Agent: curl/7.29.0
    > Host: repo.tuxcare.com
    > Accept: */*
    >
    < HTTP/1.1 403 Forbidden
    HTTP/1.1 403 Forbidden
    < Server: nginx/1.20.1
    Server: nginx/1.20.1
    < Date: Thu, 31 Oct 2024 10:28:59 GMT
    Date: Thu, 31 Oct 2024 10:28:59 GMT
    < Content-Type: text/html
    Content-Type: text/html
    < Content-Length: 153
    Content-Length: 153
    < Connection: keep-alive
    Connection: keep-alive

    <
    <html>
    <head><title>403 Forbidden</title></head>
    <body>
    <center><h1>403 Forbidden</h1></center>
    <hr><center>nginx/1.20.1</center>
    </body>
    </html>
    * Connection #0 to host repo.tuxcare.com left intact

    0
  • cPRex Jurassic Moderator

    LeGastronome - that seems like the same error to me as the verbose output shows an IPv6 connection attempt.

    0
  • LeGastronome

    Correct, my mistake thank you !

    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post