• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Issue Plesk broken, resolving error?

xgenesis

Basic Pleskian
I get this error when I run plesk repair, I think Plesk broke the DNS when automatically updating

Code:
k-ac' '/etc/psa-webmail/horde'] with exit code [1]

  fsmng failed: W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease  Temporary failure resolving 'security.ubuntu.com'
W: Failed to fetch http://updates.atomicorp.com/channels/tortix-common/debian/dists/xenial/InRelease  Temporary failure resolving 'updates.atomicorp.com'
W: Failed to fetch https://autoinstall.plesk.com/debian/NODE_0.0.1/dists/all/InRelease  Temporary failure resolving 'autoinstall.plesk.com'
W: Some index files failed to download. They have been ignored, or old ones used instead.
E: Failed to fetch https://autoinstall.plesk.com/ubuntu/PSA_17.5.3/../../PSA_17.5.3/extras-deb-Ubuntu-16.04-x86_64/opt/horde/psa-turba_4.2.18-ubuntu16.04.build1705170314.14_all.deb  Temporary failure resolving 'autoinstall.plesk.com'

E: Some files failed to download
ERROR:Command '['/usr/bin/apt-get', 'install', '--reinstall', '--download-only', 'psa-turba=4.2.18-ubuntu16.04.build1705170314.14']' returned non-zero exit status 100

When I do nslookup www.google.com

Code:
nslookup www.google.com
Server:         213.186.33.99
Address:        213.186.33.99#53

** server can't find www.google.com: SERVFAIL
 
It is not Plesk that is failing, but the domain name resolution on the host.

You can try to edit /etc/resolv.conf and make sure that it contains at least one valid, accessible nameserver. You can always add these two to the beginning of the file:
nameserver 8.8.8.8
nameserver 4.4.4.4
 
Back
Top