Skip to main content
We are currently experiencing a higher than average ticket volume and as such our responses may be delayed. Searching on our Help Center articles or going to our Community is also a great resource for answers.

Update failed

Comments

10 comments

  • exemaco

    I tried with different servers and they all have the same error.

    0
  • cPRex Jurassic Moderator

    Hey there!  Are you able to get an IP in response when you run the following command from your server?

    dig repo.imunify360.cloudlinux.com

     

    0
  • exemaco

    cPRex

    Yes,

     

    dig repo.imunify360.cloudlinux.com

    ; <<>> DiG 9.11.36-RedHat-9.11.36-11.el8_9 <<>> repo.imunify360.cloudlinux.com
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 48632
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

    ;; OPT PSEUDOSECTION:
    ; EDNS: version: 0, flags:; udp: 512
    ;; QUESTION SECTION:
    ;repo.imunify360.cloudlinux.com.        IN      A

    ;; ANSWER SECTION:
    repo.imunify360.cloudlinux.com. 120 IN  A       107.155.119.71

    ;; Query time: 24 msec
    ;; SERVER: 8.8.8.8#53(8.8.8.8)
    ;; WHEN: Thu Apr 11 13:22:51 -03 2024
    ;; MSG SIZE  rcvd: 75

    0
  • exemaco

    cPRex

    wget https://repo.imunify360.cloudlinux.com/defense360/el/6/updates/x86_64/repodata/repomd.xml
    --2024-04-11 13:25:11--  https://repo.imunify360.cloudlinux.com/defense360/el/6/updates/x86_64/repodata/repomd.xml
    Resolving repo.imunify360.cloudlinux.com (repo.imunify360.cloudlinux.com)... 107.155.119.71
    Connecting to repo.imunify360.cloudlinux.com (repo.imunify360.cloudlinux.com)|107.155.119.71|:443... failed: Connection timed out.
    Retrying.

     

     

    0
  • cPRex Jurassic Moderator

    Okay, now we're getting somewhere.

    What about this - last test:

    wget https://google.com
    0
  • exemaco

    cPRex

     

    wget https://google.com
    --2024-04-11 13:30:25--  https://google.com/
    Resolving google.com (google.com)... 142.251.133.238, 2800:3f0:4002:801::200e
    Connecting to google.com (google.com)|142.251.133.238|:443... connected.
    HTTP request sent, awaiting response... 301 Moved Permanently
    Location: https://www.google.com/ [following]
    --2024-04-11 13:30:26--  https://www.google.com/
    Resolving www.google.com (www.google.com)... 142.250.79.132, 2800:3f0:4002:813::2004
    Connecting to www.google.com (www.google.com)|142.250.79.132|:443... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: unspecified [text/html]
    Saving to: ‘index.html’

    index.html                                                    [ <=>                                                                                                                                 ]  18.51K  --.-KB/s    in 0.001s

    2024-04-11 13:30:26 (12.8 MB/s) - ‘index.html’ saved [18958]

    0
  • exemaco

    Let me clarify that we have 10 different servers, and they all have the same symptom.

    0
  • cPRex Jurassic Moderator

    Originally I was thinking there were outbound https issues, but it doesn't seem like that is the case.  Could you submit a ticket from one of the affected systems so we can check that out? 

    0
  • exemaco

    ok I'll tell my client to submit a ticket to cpanel support.

    1

Please sign in to leave a comment.