Articles in this section

Notification about failed system update is received from Plesk: There was an issue with updating system packages and third-party components

Leo Mastropierro
Updated
Plesk for Linux kb: technical

Applicable to:

  • Plesk for Linux

Symptoms

  • A notification about a failed system update is received:

    There was an issue with updating system packages and third-party components

  • Error in /var/log/plesk/systemupdatestool.log:

    INFO: pum is called with arguments: ['--check']
    ERROR: Apt cache fetch failed. Try to run the `apt-get update` command. 
    ERROR: Err:12 https://download.imunify360.com/ubuntu/20.04/slot-1 focal InRelease 
    ERROR: Could not connect to download.imunify360.com:443 (157.180.22.9), connection timed out Could not connect to download.imunify360.com:443 (37.27.120.227), connection timed out 
    ERROR: Err:13 https://download.imunify360.com/ubuntu/20.04/slot-2 focal InRelease 
    ERROR: Unable to connect to download.imunify360.com:https:

  • No downtime on the side of Imunify servers

  • Commands below show no errors:

    # plesk sbin pum --check

    # apt-get update

Cause

Issue with DNS resolution on the server.

Resolution

Warning: Since /etc/resolv.conf and /etc/systemd/resolved.conf contents are not part of the Plesk configuration and are to be selected by the server or network administrator, it is highly recommended to contact the administrator of your network service before performing any of the operations listed below.

Use these steps to disable systemd-resolved service, and configure reliables open DNS resolver such 8.8.8.8, 8.8.4.4 (Google); 1.1.1.1, 1.0.0.1 (Cloudflare):

  1. Connect to the server via SSH

  2. Execute the following command to disable systemd-resolved:

    # systemctl disable systemd-resolved && systemctl stop systemd-resolved

  3. Use vi to configure the DNS resolvers you would like to use directly in the /etc/resolv.conf file:

    # vi /etc/resolv.conf

    An example of this file would be:

    nameserver 8.8.8.8
    nameserver 8.8.4.4
    nameserver 1.1.1.1

Was this article helpful?

Comments

3 comments
Date Votes
  • Avatar
    Patrick B
    (Edited )

    Does not help.

    systemd-resolved was never activated on my server, also changed resolv.conf to Cloudflare/Google last week.

    Is it really a dns issue? The given IP addresses in the logs seem to be correct.

    Sometimes it is the same for “tuxcare” domain:

    Reason: 2026-02-06 06:27:03 INFO: pum is called with arguments: ['--update', '--json']
    /usr/lib/python3/dist-packages/apt/cache.py:562: Warning: W:Failed to fetch https://repo.alt.tuxcare.com/alt-common/deb/ubuntu/24.04/stable/dists/noble/InReleaseCould not connect to repo.alt.tuxcare.com:443(157.180.22.9), connection timed out, W:Failed to fetch

    btw: when dns lookup fails it looks like this:

    Reason: 2026-02-04 07:07:52 INFO: pum is called with arguments: ['--list', '--repo-info', '--json']
    /usr/lib/python3/dist-packages/apt/cache.py:562: Warning: W:Failed to fetch https://repo.alt.tuxcare.com/alt-common/deb/ubuntu/24.04/stable/dists/noble/InRelease Temporary failure resolving 'repo.alt.tuxcare.com', W:Failed to fetch https://download.imunify360.com/ubuntu/24.04/slot-1/dists/noble/InReleaseTemporary failure resolving 'download.imunify360.com', W:Failed to fetch

    2
  • Avatar
    Michael Perron

    Ich hab dieses Problem alle paar Tage mit imunify360, eher selten mal mit tuxcare. Alles andere macht keine Probleme.

    Grund: 2026-04-03 06:27:24 INFO: pum is called with arguments: ['--list', '--repo-info', '--json']
    /usr/lib/python3/dist-packages/apt/cache.py:562: Warning: W:Failed to fetch https://download.imunify360.com/ubuntu/24.04/slot-1/dists/noble/InRelease Could not connect to download.imunify360.com:443 (157.180.22.9), connection timed out

     

    0
  • Avatar
    Michael Perron

    Das löst das Problem nicht.

    0

Please sign in to leave a comment.