-
JB33-RJM
- Posts: 1
- Joined: 2018-01-17 21:27
apt-get update : Temporary Failure resolving ‘ftp.us.debian.
#1
Post
by JB33-RJM » 2018-01-17 21:46
Hello all,
I have a been a linux hobbyist for many years and I am just now actually learning it. A friend introduced me to Debian & Kali. I currently have Debian 9 installed. I am writing this message on a machine other than the one experiencing the error, so I know the description will be a bit light, but I think it is a simple /etc/apt/sources.list issue. I have already been in VI and commented out the CD-Rom, which helped with that portion of the error, but I still have Temporary failure issues, which my instinct says are incorrect links.
Here is the error gist:
Err:1 http://ftp.us.debian.org/debian stretch InRelease
Temporary failure resolving ‘ftp.us.debian.org’
Err:2 http://security.debian.org/debian-security stretch/updates InRelease
Temporary failure resolving ‘ftp.us.debian.org’
Err:3 http://ftp.us.debian.org/debian.org/debian stretch-updates InRelease
Temporary failure resolving ‘ftp.us.debian.org’
Hope this is enough information. Everything network-related works fine, except for apt-get. I can’t update or install any packages.
Thanks for your help,
JB33
-
sunrat
- Administrator
- Posts: 5224
- Joined: 2006-08-29 09:12
- Location: Melbourne, Australia
- Has thanked: 56 times
- Been thanked: 199 times
Re: apt-get update : Temporary Failure resolving ‘ftp.us.deb
#3
Post
by sunrat » 2018-01-18 03:35
Post your sources.list. The first 2 look ok and resolve fine here but the 3rd one looks wrong and won’t resolve. Usually a temporary failure will be fine if you wait a bit.
“ computer users can be divided into 2 categories:
Those who have lost data
…and those who have not lost data YET ” Remember to BACKUP!
-
dotlj
- Posts: 646
- Joined: 2009-12-25 17:21
Re: apt-get update : Temporary Failure resolving ‘ftp.us.deb
#6
Post
by dotlj » 2018-01-28 10:44
Temporary failure resolving … usually simply means either your Internet isn’t connected, isn’t working, or your networking has been changed and not able to connect.
What network interface are you using? Ethernet cable, wireless, both, something else?
Try ifconfig to see what’s working or ip route.
VDS на Debian 8, пытаюсь поставить новый пакет
apt install package
Err ftp.debian.org/debian/jessie/main…
Temporary failure resolving ‘ftp.debian.org’
В /etc/resolv.conf было 8.8.8.8 поставил ещё DNS гугла
nameserver 208.67.220.220
nameserver 8.8.8.8
nameserver 208.67.222.222
nameserver 8.8.4.4
То же самое (или нужно время на обновление?)
На команду host ya.ru
Пишет: connection timed out; no servers could be reached
Техподдержка хостинга говорит смотреть в сторону файрвола. Как понять какой там файрвол стоит и что конкретно в нём нужно подкрутить?
-
Вопрос заданболее трёх лет назад
-
6931 просмотр
своими силами можно определить так:
iptables-save — покажет текущие настройки iptables
route — покажет список маршрутов, defaul правильно установлен?
ping 8.8.8.8 проходит?
host -t A ya.ru 8.8.8.8, должен вернуть ip адрес хоста, если ошибка — значит проблема с интернет соединением
как вариант если ничего не настраивалось, попробуй ребутнуть хост.
с сетью, похоже, все в порядке, пинги до 8.8.8.8 проходят.
но вот отзывается ли 208.67.220.220? попробуйте убрать вообще DNS провайдера из resolv.conf и оставить только гугловские.
Пригласить эксперта
Была та же самая проблема. Все решилось командой:
sudo /etc/init.d/networking restart && sudo dhclient
-
Показать ещё
Загружается…
10 февр. 2023, в 10:35
50000 руб./за проект
10 февр. 2023, в 08:59
1000 руб./за проект
10 февр. 2023, в 08:22
2000 руб./за проект
Минуточку внимания
-
Thread starter
Valrich
-
Start date
Jun 17, 2022
MarkusF
Proxmox Staff Member
Staff member
-
#2
In /etc/resolv.conf you can change the ip of your DNS-resolver
https://en.wikipedia.org/wiki/Resolv.conf
You have a few Options:
- DNS-Server of your Internet-Provider
- host a dns server yourself and add that ip to your resolv.conf
- use public DNS-Server
-
#3
In /etc/resolv.conf you can change the ip of your DNS-resolver
https://en.wikipedia.org/wiki/Resolv.conf
You have a few Options:
- DNS-Server of your Internet-Provider
- host a dns server yourself and add that ip to your resolv.conf
- use public DNS-Server
THANK YOU!
For new Package Requests, see the guidelines
Setup
Package Name:
Package Version:
_NAS Model:_DS715
NAS Architecture:
_DSM version:_DSM 6.0.1-7393
Hello, I just started using Synology DS715 yesterday and downloaded Debian Chroot with Python through Synocommunity. I tried to do simple apt-get upgrade and update, but its not working. Please check the log below. The http://ftp.us.debian.org site seems to be working fine, but why is this not working? Any insight would be appreciated.
root@bitcoinuser:/# apt-get update
Err http://ftp.us.debian.org stable InRelease
Err http://ftp.debian.org wheezy-updates InRelease
Err http://security.debian.org jessie InRelease
Err http://security.debian.org jessie/updates InRelease
Err http://ftp.fr.debian.org jessie InRelease
Err http://ftp.fr.debian.org jessie-updates InRelease
Err http://ftp.us.debian.org stable Release.gpg
Could not resolve ‘ftp.us.debian.org’
Err http://ftp.debian.org wheezy-updates Release.gpg
Could not resolve ‘ftp.debian.org’
Err http://security.debian.org jessie Release.gpg
Could not resolve ‘security.debian.org’
Err http://ftp.fr.debian.org jessie Release.gpg
Could not resolve ‘ftp.fr.debian.org’
Err http://security.debian.org jessie/updates Release.gpg
Could not resolve ‘security.debian.org’
Err http://ftp.fr.debian.org jessie-updates Release.gpg
Could not resolve ‘ftp.fr.debian.org’
Reading package lists… Done
W: Failed to fetch http://ftp.us.debian.org/debian/dists/stable/InRelease
W: Failed to fetch http://ftp.debian.org/debian/dists/wheezy-updates/InRelease
W: Failed to fetch http://security.debian.org/dists/jessie/InRelease
W: Failed to fetch http://ftp.fr.debian.org/debian/dists/jessie/InRelease
W: Failed to fetch http://security.debian.org/dists/jessie/updates/InRelease
W: Failed to fetch http://ftp.fr.debian.org/debian/dists/jessie-updates/InRelease
W: Failed to fetch http://ftp.us.debian.org/debian/dists/stable/Release.gpg Could not resolve ‘ftp.us.debian.org’
W: Failed to fetch http://ftp.debian.org/debian/dists/wheezy-updates/Release.gpg Could not resolve ‘ftp.debian.org’
W: Failed to fetch http://security.debian.org/dists/jessie/Release.gpg Could not resolve ‘security.debian.org’
W: Failed to fetch http://security.debian.org/dists/jessie/updates/Release.gpg Could not resolve ‘security.debian.org’
W: Failed to fetch http://ftp.fr.debian.org/debian/dists/jessie/Release.gpg Could not resolve ‘ftp.fr.debian.org’
W: Failed to fetch http://ftp.fr.debian.org/debian/dists/jessie-updates/Release.gpg Could not resolve ‘ftp.fr.debian.org’
W: Some index files failed to download. They have been ignored, or old ones used instead.
root@bitcoinuser:/# apt-get upgrade
Reading package lists… Done
Building dependency tree
Reading state information… Done
Calculating upgrade… Done
The following packages will be upgraded:
apt apt-utils base-files cron libapt-inst1.5 libapt-pkg4.12 libc-bin libdns-export100 libgnutls-deb0-28
libgnutls-openssl27 libicu52 libirs-export91 libisc-export95 libisccfg-export90 libssl1.0.0 libsystemd0 libudev1
multiarch-support rsyslog systemd systemd-sysv tzdata udev
23 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 16.7 MB of archives.
After this operation, 742 kB disk space will be freed.
Do you want to continue? [Y/n] Y
Err http://ftp.us.debian.org/debian/ stable/main base-files armhf 8+deb8u2
Could not resolve ‘ftp.us.debian.org’
Err http://ftp.fr.debian.org/debian/ jessie/main base-files armhf 8+deb8u2
Could not resolve ‘ftp.fr.debian.org’
Err http://ftp.fr.debian.org/debian/ jessie/main libapt-pkg4.12 armhf 1.0.9.8.1
Could not resolve ‘ftp.fr.debian.org’
Err http://ftp.fr.debian.org/debian/ jessie/main apt armhf 1.0.9.8.1
Could not resolve ‘ftp.fr.debian.org’
Err http://ftp.fr.debian.org/debian/ jessie/main libc-bin armhf 2.19-18+deb8u1
Could not resolve ‘ftp.fr.debian.org’
Err http://ftp.fr.debian.org/debian/ jessie/main libudev1 armhf 215-17+deb8u2
Could not resolve ‘ftp.fr.debian.org’
Err http://ftp.fr.debian.org/debian/ jessie/main udev armhf 215-17+deb8u2
Could not resolve ‘ftp.fr.debian.org’
Err http://ftp.fr.debian.org/debian/ jessie/main libsystemd0 armhf 215-17+deb8u2
Could not resolve ‘ftp.fr.debian.org’
Err http://ftp.fr.debian.org/debian/ jessie/main systemd armhf 215-17+deb8u2
Could not resolve ‘ftp.fr.debian.org’
Err http://ftp.fr.debian.org/debian/ jessie/main systemd-sysv armhf 215-17+deb8u2
Could not resolve ‘ftp.fr.debian.org’
Err http://ftp.fr.debian.org/debian/ jessie/main cron armhf 3.0pl1-127+deb8u1
Could not resolve ‘ftp.fr.debian.org’
Err http://ftp.fr.debian.org/debian/ jessie/main libapt-inst1.5 armhf 1.0.9.8.1
Could not resolve ‘ftp.fr.debian.org’
Err http://ftp.fr.debian.org/debian/ jessie/main libssl1.0.0 armhf 1.0.1k-3+deb8u1
Could not resolve ‘ftp.fr.debian.org’
Err http://ftp.fr.debian.org/debian/ jessie/main libgnutls-openssl27 armhf 3.3.8-6+deb8u3
Could not resolve ‘ftp.fr.debian.org’
Err http://ftp.fr.debian.org/debian/ jessie/main libgnutls-deb0-28 armhf 3.3.8-6+deb8u3
Could not resolve ‘ftp.fr.debian.org’
Err http://ftp.fr.debian.org/debian/ jessie/main libisc-export95 armhf 1:9.9.5.dfsg-9+deb8u2
Could not resolve ‘ftp.fr.debian.org’
Err http://ftp.fr.debian.org/debian/ jessie/main libdns-export100 armhf 1:9.9.5.dfsg-9+deb8u2
Could not resolve ‘ftp.fr.debian.org’
Err http://ftp.fr.debian.org/debian/ jessie/main libicu52 armhf 52.1-8+deb8u2
Could not resolve ‘ftp.fr.debian.org’
Err http://ftp.fr.debian.org/debian/ jessie/main libisccfg-export90 armhf 1:9.9.5.dfsg-9+deb8u2
Could not resolve ‘ftp.fr.debian.org’
Err http://ftp.fr.debian.org/debian/ jessie/main libirs-export91 armhf 1:9.9.5.dfsg-9+deb8u2
Could not resolve ‘ftp.fr.debian.org’
Err http://ftp.fr.debian.org/debian/ jessie/main multiarch-support armhf 2.19-18+deb8u1
Could not resolve ‘ftp.fr.debian.org’
Err http://ftp.fr.debian.org/debian/ jessie/main tzdata all 2015f-0+deb8u1
Could not resolve ‘ftp.fr.debian.org’
Err http://ftp.fr.debian.org/debian/ jessie/main apt-utils armhf 1.0.9.8.1
Could not resolve ‘ftp.fr.debian.org’
Err http://ftp.fr.debian.org/debian/ jessie/main rsyslog armhf 8.4.2-1+deb8u1
Could not resolve ‘ftp.fr.debian.org’
E: Failed to fetch http://ftp.fr.debian.org/debian/pool/main/b/base-files/base-files_8+deb8u2_armhf.deb Could not resolve ‘ftp.fr.debian.org’
E: Failed to fetch http://ftp.fr.debian.org/debian/pool/main/a/apt/libapt-pkg4.12_1.0.9.8.1_armhf.deb Could not resolve ‘ftp.fr.debian.org’
E: Failed to fetch http://ftp.fr.debian.org/debian/pool/main/a/apt/apt_1.0.9.8.1_armhf.deb Could not resolve ‘ftp.fr.debian.org’
E: Failed to fetch http://ftp.fr.debian.org/debian/pool/main/g/glibc/libc-bin_2.19-18+deb8u1_armhf.deb Could not resolve ‘ftp.fr.debian.org’
E: Failed to fetch http://ftp.fr.debian.org/debian/pool/main/s/systemd/libudev1_215-17+deb8u2_armhf.deb Could not resolve ‘ftp.fr.debian.org’
E: Failed to fetch http://ftp.fr.debian.org/debian/pool/main/s/systemd/udev_215-17+deb8u2_armhf.deb Could not resolve ‘ftp.fr.debian.org’
E: Failed to fetch http://ftp.fr.debian.org/debian/pool/main/s/systemd/libsystemd0_215-17+deb8u2_armhf.deb Could not resolve ‘ftp.fr.debian.org’
E: Failed to fetch http://ftp.fr.debian.org/debian/pool/main/s/systemd/systemd_215-17+deb8u2_armhf.deb Could not resolve ‘ftp.fr.debian.org’
E: Failed to fetch http://ftp.fr.debian.org/debian/pool/main/s/systemd/systemd-sysv_215-17+deb8u2_armhf.deb Could not resolve ‘ftp.fr.debian.org’
E: Failed to fetch http://ftp.fr.debian.org/debian/pool/main/c/cron/cron_3.0pl1-127+deb8u1_armhf.deb Could not resolve ‘ftp.fr.debian.org’
E: Failed to fetch http://ftp.fr.debian.org/debian/pool/main/a/apt/libapt-inst1.5_1.0.9.8.1_armhf.deb Could not resolve ‘ftp.fr.debian.org’
E: Failed to fetch http://ftp.fr.debian.org/debian/pool/main/o/openssl/libssl1.0.0_1.0.1k-3+deb8u1_armhf.deb Could not resolve ‘ftp.fr.debian.org’
E: Failed to fetch http://ftp.fr.debian.org/debian/pool/main/g/gnutls28/libgnutls-openssl27_3.3.8-6+deb8u3_armhf.deb Could not resolve ‘ftp.fr.debian.org’
E: Failed to fetch http://ftp.fr.debian.org/debian/pool/main/g/gnutls28/libgnutls-deb0-28_3.3.8-6+deb8u3_armhf.deb Could not resolve ‘ftp.fr.debian.org’
E: Failed to fetch http://ftp.fr.debian.org/debian/pool/main/b/bind9/libisc-export95_9.9.5.dfsg-9+deb8u2_armhf.deb Could not resolve ‘ftp.fr.debian.org’
E: Failed to fetch http://ftp.fr.debian.org/debian/pool/main/b/bind9/libdns-export100_9.9.5.dfsg-9+deb8u2_armhf.deb Could not resolve ‘ftp.fr.debian.org’
E: Failed to fetch http://ftp.fr.debian.org/debian/pool/main/i/icu/libicu52_52.1-8+deb8u2_armhf.deb Could not resolve ‘ftp.fr.debian.org’
E: Failed to fetch http://ftp.fr.debian.org/debian/pool/main/b/bind9/libisccfg-export90_9.9.5.dfsg-9+deb8u2_armhf.deb Could not resolve ‘ftp.fr.debian.org’
E: Failed to fetch http://ftp.fr.debian.org/debian/pool/main/b/bind9/libirs-export91_9.9.5.dfsg-9+deb8u2_armhf.deb Could not resolve ‘ftp.fr.debian.org’
E: Failed to fetch http://ftp.fr.debian.org/debian/pool/main/g/glibc/multiarch-support_2.19-18+deb8u1_armhf.deb Could not resolve ‘ftp.fr.debian.org’
E: Failed to fetch http://ftp.fr.debian.org/debian/pool/main/t/tzdata/tzdata_2015f-0+deb8u1_all.deb Could not resolve ‘ftp.fr.debian.org’
E: Failed to fetch http://ftp.fr.debian.org/debian/pool/main/a/apt/apt-utils_1.0.9.8.1_armhf.deb Could not resolve ‘ftp.fr.debian.org’
E: Failed to fetch http://ftp.fr.debian.org/debian/pool/main/r/rsyslog/rsyslog_8.4.2-1+deb8u1_armhf.deb Could not resolve ‘ftp.fr.debian.org’
E: Unable to fetch some archives, maybe run apt-get update or try with —fix-missing?
I have a Rails application that I want to deploy using Docker on an Ubuntu server. I have the Dockerfile for the application already set up, right now I want to view the nginx conf in its container.
I ran the command below to start an nginx container in an interactive mode:
docker run -i -t nginx:latest /bin/bash
Right now I am trying to install nano editor in order to view the configuration for nginx configuration (nginx.conf) using the commands below:
apt-get update
apt-get install nano
export TERM=xterm
However, when I run the first command apt-get update, I get the error below:
Err:1 http://security.debian.org/debian-security buster/updates InRelease
Temporary failure resolving 'security.debian.org'
Err:2 http://deb.debian.org/debian buster InRelease
Temporary failure resolving 'deb.debian.org'
Err:3 http://deb.debian.org/debian buster-updates InRelease
Temporary failure resolving 'deb.debian.org'
Reading package lists... Done
W: Failed to fetch http://deb.debian.org/debian/dists/buster/InRelease Temporary failure resolving 'deb.debian.org'
W: Failed to fetch http://security.debian.org/debian-security/dists/buster/updates/InRelease Temporary failure resolving 'security.debian.org'
W: Failed to fetch http://deb.debian.org/debian/dists/buster-updates/InRelease Temporary failure resolving 'deb.debian.org'
W: Some index files failed to download. They have been ignored, or old ones used instead.
I have checked very well it has nothing to do with network connectivity. I would need some help. Thank you.
asked May 2, 2020 at 22:58
Promise PrestonPromise Preston
21.1k11 gold badges127 silver badges128 bronze badges
1
Try restarting docker. Worked for me.
sudo service docker restart or sudo /etc/init.d/docker restart
Prior to bumping into this issue, docker was working fine. If you never had docker working in the first place, you probably have a different issue.
answered Sep 24, 2020 at 20:14
4
Perhaps the network on the VM is not communicating with the default network created by docker during the build (bridge), so try «host» network :
docker build --network host -t [image_name]
for docker-compose:
service_name:
container_name: name
build:
context: .
network: host
answered Mar 19, 2021 at 20:00
manumazumanumazu
6134 silver badges2 bronze badges
6
If you have VPN running, stop it and try again. It solved for me!
answered Aug 14, 2020 at 15:26
1
Here’s how I solved it:
Start the docker container for the application in an interactive mode, in my case it an nginx container :
docker run -i -t nginx:latest /bin/bash
Run the command below to grant read permission to the others role for the resolv.conf file:
chmod o+r /etc/resolv.conf
Note: If you are having this issue on your host machine (Ubuntu Linux OS) and not for the Docker containers, then run the same command adding sudo to it in the host machine terminal:
sudo chmod o+r /etc/resolv.conf
Endeavour to exit your bash interactive terminal once you run this:
exit
And then open a new bash interactive terminal and run the commands again:
apt-get update
apt-get install nano
export TERM=xterm
Everything should work fine now.
Reference to this on Digital Ocean: Apt error: Temporary failure resolving ‘deb.debian.org’
That’s all.
Asclepius
54.5k16 gold badges157 silver badges139 bronze badges
answered May 2, 2020 at 22:58
Promise PrestonPromise Preston
21.1k11 gold badges127 silver badges128 bronze badges
1
sudo vi /etc/docker/daemon.json
and check flag of iptables, aslo add DNS if not added
{...., "iptables":true,"dns": ["8.8.8.8", "8.8.4.4"]}
then
sudo service docker restart
solved me
answered Apr 14, 2022 at 10:23
Victor OrletchiVictor Orletchi
4211 gold badge4 silver badges14 bronze badges
I had the same problem and in my case it was file access control.
I uses extended acls on the docker root folder and did not realize it, because they where inherited from the folder above (stupid idea to test docker in a «scratch» directory where permissions are set via extended acls).
This lead to the situation that «/etc/resolv.conf» had setting «640» inside the running docker container with a «+» marking the extended acls. But the image did not have extended acls installed and could not handle it.
The weird thing was that, as far as I can see, all other network tools worked (e.g. ping) but only apt could no access the DNS resolver.
After removing the extended acls from the docker root and setting the usual acls, everything worked inside the running container.
Similar to the answer of «Promise Prestion», but solved permanently for new containers, too.
answered Mar 25, 2021 at 14:50
MarcoMarco
7496 silver badges11 bronze badges
0
Run this command:
echo -e «nameserver 8.8.8.8nnameserver 8.8.4.4» |sudo tee -a /etc/resolv.conf
After that run-
sudo apt-get update
This worked for me.
answered May 20, 2022 at 6:30
1
I easily resolved it via:
- docker exec -it nginx bash (Go inside container)
- ping google.com (if not working)
- exit (Exit from container)
- sudo service docker restart
Please also confirms /etc/sysctl.conf
- net.ipv4.ip_forward = 1
sudo sysctl -p /etc/sysctl.conf
answered May 3, 2020 at 4:57
Under Debian, as root, I’ve ran:
/etc/init.d/docker restart
This solved the issue for me.
Then build and run the container again.
sɐunıɔןɐqɐp
3,14715 gold badges35 silver badges39 bronze badges
answered Jan 27, 2021 at 19:17
I was having the wrong DNS IP address in my /etc/docker/daemon.json. In my case, it was my home router DNS IP address and I was trying from the office network.
I found out my office DNS and updated with that.
{
"dns": ["192.168.1.1"]
}
Eric Aya
69.1k35 gold badges179 silver badges250 bronze badges
answered Jun 29, 2022 at 17:59
1
Similar issue, under debian.
Root cause was a bad DOCKER-USER rule in iptables chain
Those rules have been haded
iptables -I DOCKER-USER -i eno1 -j DROP
iptables -I DOCKER-USER -s 90.62.xxx.xx/32 -i eno1 -j ACCEPT
so removing temporarily following rule fix the point
iptables -D DOCKER-USER -i eno1 -j DROP
answered Jul 15, 2021 at 13:35
Coming here from some docker cross compiling headache:
While forking some repo I manually downloaded its root folder containing confd stuff and added it just like the original maintainer did.
ADD root /
after this I was not able to apt update anymore.
I found that the permission of my root named folder was wrong. stat -f "%OLp" root revealed it is 700, but must be 755 to work.
answered Oct 9, 2021 at 22:02
MaxMax
4822 gold badges4 silver badges14 bronze badges
I had a similar issue, I tried many suggested solutions, but my issue was gone after I rebooted my VM.
Asclepius
54.5k16 gold badges157 silver badges139 bronze badges
answered Sep 2, 2020 at 14:30
babis21babis21
1,2951 gold badge15 silver badges27 bronze badges
I’m using Arch version 6.0.11 and docker version 20.10.21, and having this issues inside docker containers.
Thanks to @Marco, that was the initial hint to solve this. The problem is related to the use of extended ACLs in the host system.
The docker root folder has ACLs, you can see this as it has a plus sign at the end of permissions «+»:
$ sudo ls -lh /var/lib/docker
drw-rw-r--+ 3 root root 4.0K Nov 24 2021 network
And what is the problem? Some docker images does not have ACLs installed, so as it was pointed this causes an issue.
Other network tools like curl resolved DNS properly, but apt or git have problems with DNS resolution.
TLDR; Where is the fix? Modify ACL to set default rx to others.
setfacl -R -d -m o::rx /var/lib/docker
After that, all network tools will be able to perform DNS resolution.
Credits:
Marco comment
Closed git issue in docker
Antoine
1,3714 gold badges20 silver badges26 bronze badges
answered Dec 11, 2022 at 18:55
