Register problem

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • doanhtien
    Junior Member
    • Aug 2023
    • 4

    #1

    Register problem

    Hello
    We are experiencing issues while installing KernelCare on the new server node. The error message indicates a timeout while trying to access the RPM package: "1.el8.x86_64.rpm [Connection timed out after 30000 milliseconds] [MIRROR] kernelcare-2.80-1.el8.x86_64.rpm: Curl error (28): Timeout was reached for https://repo.cloudlinux.com/kernelca...el8.x86_64.rpm [Connection timed out after 30000 milliseconds]". The installation and registration process is taking quite a bit of time: https://prnt.sc/7RYkQB5Oi0Ua. Do you have any instructions on how to resolve this issue?

    Thanks​
  • bogdan.sh
    Administrator
    • Nov 2016
    • 1221

    #2
    Hi,

    Do you use any kind of proxy on that server? Can you ping the cln.cloudlinux.com or xmlrpc.cln.cloudlinux.com from it? Do you use IPv6?

    Comment

    • doanhtien
      Junior Member
      • Aug 2023
      • 4

      #3
      Our server is located in Japan. I've tried pinging cln.cloudlinux.com and xmlrpc.cln.cloudlinux.com via IPv4, but there's a 100% loss. Do you have any other servers that I can use to proceed with the installation?

      Comment

      • doanhtien
        Junior Member
        • Aug 2023
        • 4

        #4
        Furthermore, I received a notification stating 'The kernel is not updated to the latest version. Please, run kcarectl --update on the server to update the kernel.' However, when I use the command 'kcarectl --update', the response is 'Updates already downloaded. No updates are needed for this kernel. Kernel is safe.' Does this have any implications?​

        Comment

        • bogdan.sh
          Administrator
          • Nov 2016
          • 1221

          #5
          Please try to identify where the packet loss is actually happening with 'traceroute cln.cloudlinux.com', as far as I know we do not block Japan. I guess it's some external firewall.

          About kcarectl --update, most likely it was already updated by regular cronjob.

          Comment

          • doanhtien
            Junior Member
            • Aug 2023
            • 4

            #6
            Originally posted by bogdan.sh
            Please try to identify where the packet loss is actually happening with 'traceroute cln.cloudlinux.com', as far as I know we do not block Japan. I guess it's some external firewall.

            About kcarectl --update, most likely it was already updated by regular cronjob.
            Could you please verify the error image I encountered when the server prompted 'Please, run kcarectl --update' at https://prnt.sc/Eo-C_23O-_tx? However, when I run the command, the server reports that the kernel is safe. Is there any way for me to dismiss this alert?​

            Comment

            Working...