32 packages can be upgraded. Run 'apt list --upgradable' to see them.*
W: Failed to fetch http://ftp.debian.org/debian/dists/buster/InRelease Temporary failure resolving 'ftp.debian.org'*
W: Failed to fetch http://ftp.debian.org/debian/dists/buster-updates/InRelease Temporary failure resolving 'ftp.debian.org'*
W: Failed to fetch http://repo.r1soft.com/apt/dists/stable/InRelease Temporary failure resolving 'repo.r1soft.com'*
W: Failed to fetch http://download.mono-project.com/repo/debian/dists/buster/InRelease Temporary failure resolving 'download.mono-project.com'*
W: Some index files failed to download. They have been ignored, or old ones used instead.*
The contents of /etc/apt/sources.list.d is shown because a solution was to remove a file in there which does not exist on my server!!
Thanks for any help somebody can give me here.
ping: google.com: Temporary failure in name resolution*
you are right. I do not know how to solve this.
The server has been OK until upgrade to 4.2.4. All changed and I started getting lots of failure emails from Diagnosis automatic run. Most errors were DNS zone errors which I fixed and then it started again.
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)*
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 127.0.0.1
cat /etc/resolv*
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)*
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN*
Sorry if I upset you by my ignorance of the use of this forum! The problem is still there and now has added all the DNS Zone errors as if there was nothing set.
I think I will close my yunohost server and stop using it
New info:
after restarting dnsmasq the three dig commands gave the same IP 192.198.174.192
Maybe it was that?
I am trying the apt update command to see if it works now.
NEWS: itr failed again with the attached errors from webadmin.
Basically I created this file nano /etc/NetworkManager/conf.d/no-systemd-resolved.conf
with contents [main] systemd-resolved=false
and then checked,enabled,started and checked again the systemd-resolved service: systemctl status systemd-resolved.service systemctl enable systemd-resolved.service systemctl start systemd-resolved.service systemctl status systemd-resolved.service
Then i run apt update
and it worked except for the forge.yunohost.org
error as before.
Then it started showing errors resolving server during download of packages.
I assume that is a yunohost bug or error.
Thanks for your help with this. I shall leave it open for you to check and close…
i now got this error yunohost dyndns update --force Error: Failed to resolve dyndns.yunohost.org
@Aleks
This is becoming tedious!
errors in apt update
are plenty and not related to this DNS resolve issue anymore.A full upgrade worked but replied with DNS resolution for dyndns.yunohost.org failed
Hit:1 https://deb.troglobit.com/debian stable InRelease Hit:2 http://security.debian.org/debian-security buster/updates InRelease Hit:3 http://download.mono-project.com/repo/debian buster InRelease Hit:4 http://ftp.debian.org/debian buster InRelease Hit:5 http://ftp.debian.org/debian buster-updates InRelease Ign:6 https://repo.r1soft.com/apt stable InRelease Err:7 https://repo.r1soft.com/apt stable Release Certificate verification failed: The certificate is NOT trusted. The name in the certificate does not match the expected. Could not handshake: Error in the certificate verification. [IP: 87.96.243.92 443] Err:8 http://forge.yunohost.org/debian buster InRelease Temporary failure resolving 'forge.yunohost.org' Err:9 http://download.bareos.org/bareos/release/19.2/Debian_10 InRelease Temporary failure resolving 'download.bareos.org' Reading package lists... Done E: The repository 'http://repo.r1soft.com/apt stable Release' no longer has a Release file.
Well I don’t know why you ended up doing this … this just sounds like not the right thing to do, systemd-resolved will likely conflict with dnsmasq, which Yunohost relies on … Also networkmanager is supposed to not be installed on Yunohost. If it is, then it’s a bug, which could explain why /etc/resolv.conf doesn’t always point to 127.0.0.1 …
Can you elaborate on how / why you ended up on that stackoverflow/superuser post
Hi @Aleks
yes of course: I googled the error message “…resolve1.service not found”
and found that it addressed my issue.
When I edited the /etc/NetworkManager/conf.d/no-systemd-resolved.conf file it did not exist and I created it. I think that network manager is installed.
When I did apt install network-manager
it told me that it was installed!!
I think we found a bug then
I installed yunohost from the original ISO and then upgraded but without adding anything to Debian, so it is a bug from the original install of yunohost! Shall I uninstall network-manager then??
/
