• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Issue Problems resolving autoinstall.plesk.com + mirror.eu.oneandone.net + more

Servus

Basic Pleskian
Hi,
since around last update Plesk Obsidian 18.0.26 I have extreme problems accessing update mirrors over CLI and also update/upgrade site in Plesk Panel. I tried several solutions like desactivating firewall in plesk panel but nothing fixed the problems. Interesting: It's not always the same! Sometimes I can access or hit update domains, and next time I try it, the same domains are unreachable. So, today it was possible to update PHP 7.4.4 to 7.4.5.
I also tried this plesk support tipps. See at the end.
Perhaps someone has an idea solving this problem.

Code:
root@server:~# aptitude clean
root@server:~# aptitude update
Hit https://artifacts.elastic.co/packages/6.x/apt stable InRelease
Err http://autoinstall.plesk.com/ubuntu/PMM_0.1.10 bionic InRelease
  Temporary failure resolving 'autoinstall.plesk.com'
Err http://mirror.eu.oneandone.net/ubuntu/ubuntu bionic InRelease
  Temporary failure resolving 'mirror.eu.oneandone.net'
Err http://mirror.truenetwork.ru/mariadb/repo/10.3/ubuntu bionic InRelease
  Temporary failure resolving 'mirror.truenetwork.ru'
Err https://packages.grafana.com/oss/deb stable InRelease
  Temporary failure resolving 'packages.grafana.com'
Err https://updates.atomicorp.com/channels/tortix-common/debian bionic InRelease
  Temporary failure resolving 'updates.atomicorp.com'
Hit http://autoinstall.plesk.com/pool/PSA_18.0.26_2994 bionic InRelease
Hit http://autoinstall.plesk.com/PHP72_17 bionic InRelease
Hit http://autoinstall.plesk.com/PHP73_17 bionic InRelease
Hit http://autoinstall.plesk.com/PHP74_17 bionic InRelease
Err http://mirror.eu.oneandone.net/ubuntu/ubuntu bionic-updates InRelease
  Temporary failure resolving 'mirror.eu.oneandone.net'
Err http://mirror.eu.oneandone.net/ubuntu/ubuntu bionic-backports InRelease
  Temporary failure resolving 'mirror.eu.oneandone.net'
Hit http://mirror.eu.oneandone.net/ubuntu/ubuntu bionic-security InRelease
W: Failed to fetch http://mirror.eu.oneandone.net/ubuntu/ubuntu/dists/bionic/InRelease: Temporary failure resolving 'mirror.eu.oneandone.net'
W: Failed to fetch http://mirror.eu.oneandone.net/ubuntu/ubuntu/dists/bionic-updates/InRelease: Temporary failure resolving 'mirror.eu.oneandone.net'
W: Failed to fetch http://mirror.eu.oneandone.net/ubuntu/ubuntu/dists/bionic-backports/InRelease: Temporary failure resolving 'mirror.eu.oneandone.net'
W: Failed to fetch http://mirror.truenetwork.ru/mariadb/repo/10.3/ubuntu/dists/bionic/InRelease: Temporary failure resolving 'mirror.truenetwork.ru'
W: Failed to fetch https://updates.atomicorp.com/channels/tortix-common/debian/dists/bionic/InRelease: Temporary failure resolving 'updates.atomicorp.com'
W: Failed to fetch https://packages.grafana.com/oss/deb/dists/stable/InRelease: Temporary failure resolving 'packages.grafana.com'
W: Failed to fetch http://autoinstall.plesk.com/ubuntu/PMM_0.1.10/dists/bionic/InRelease: Temporary failure resolving 'autoinstall.plesk.com'
W: Some index files failed to download. They have been ignored, or old ones used instead.

root@server:~#

By accessing server over CLI there already is a warning/notice
Code:
  * Canonical Livepatch is available for installation.
   - Reduce system reboots and improve kernel security. Activate at:
     https://ubuntu.com/livepatch

0 packages can be updated.
0 updates are security updates.

Failed to connect to https://changelogs.ubuntu.com/meta-release-lts. Check your Internet connection or proxy settings


Last login: Mon Apr 20 12:54:11 2020 from...



Here the solutions by plesk support.

Code:
root@server:~# nslookup autoinstall.plesk.com
Server:         127.0.0.53
Address:        127.0.0.53#53

Non-authoritative answer:
autoinstall.plesk.com   canonical name = 1727842103.rsc.cdn77.org.
Name:   1727842103.rsc.cdn77.org
Address: 195.181.175.51

root@server:~# nslookup mirror.eu.oneandone.net
Server:         127.0.0.53
Address:        127.0.0.53#53

Non-authoritative answer:
Name:   mirror.eu.oneandone.net
Address: 217.72.206.21
Name:   mirror.eu.oneandone.net
Address: 2001:8d8:5c0:404::3

cat /etc/resolv.conf
# This file is managed by man:systemd-resolved(8). Do not edit.
#
# This is a dynamic resolv.conf file for connecting local clients to the
# internal DNS stub resolver of systemd-resolved. This file lists all
# configured search domains.
#
# Run "systemd-resolve --status" to see details about the uplink DNS servers
# currently in use.
#
# Third party programs must not access this file directly, but only through the
# symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a different way,
# replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.

nameserver 127.0.0.53
options edns0
search onlinehome-server.info

The appearance of "search" seems to be a problem. But I don't know how the content was before. The file was updated (timestamp) today at 12.24 pm.
I'm a little afarid to change it to

Code:
cat /etc/resolv.conf
; generated by /sbin/dhclient-script
search example.com autoinstall.plesk.com
nameserver 192.168.0.1

. My provider is Ionos (former 1and1). Sometimes they have their own configurations together with PLESK.
 
sometimes caused by incorrect DNS settings therefore check your dns settings and have you tried to use for testing different / public nameserver not only the one from provider
 
Last edited:
Thanks a lot for your help @Brujo . No. For sure, I would have done it.
But one day later it worked again like all days/the last two years before.
I wanted to wait a few days to be sure that it isn't a temporary fix and it works again before I write it here.
Lots of greets
 
Last edited:
good that it was obviously only a temporary problem with the nameservers, but that doesn't hurt if you add another nameserver and don't have such a temporary appearance from your provider
 
Back
Top