![]() In this way your sudo apt update and sudo apt install commands will be able to work in both cases. Now, when on the VPN, you can optionally re-enable the proxy, and when not on the VPN, you can disable the proxy. Sudo mv /etc/apt//01proxy.bak /etc/apt//01proxy # Re-enable the apt proxy by removing the foreign ".bak" extension: Sudo mv /etc/apt//01proxy /etc/apt//01proxy.bak If this alternate server is on a VPN, for instance, it won't be available if you're not VPNed in to that network, and you'll see the errors above.Īs a work-around, you can temporarily disable or enable this proxy by simply renaming this file as follows: # Disable the apt proxy by changing its name to have a ".bak" extension: For Kazam, when I try to disable I get this sudo: unable to execute /usr/bin/add-apt-repository: No such file or directory. This means that my system has an apt proxy configured to re-route apt update and apt install commands through an alternate server. ![]() Grep for this in /etc/apt to see where this phrase might be found: grep -rn 'apt-cacher\.something1\.something2' "/etc/apt"įor me, I found a result in the file /etc/apt//01proxy. They have been ignored, or old ones used instead. ![]() When running sudo apt update (preferred), or sudo apt-get update, look for the following types of errors: Err:1 bionic InReleaseĬould not resolve '2'Ĩ packages can be upgraded. This will only apply to some people, in particular to people working on managed systems who are configured by others. Error while 'sudo apt-get update' Ask Question Asked 3 years, 6 months ago Modified 2 years, 7 months ago Viewed 5k times -3 I was trying to run the command sudo apt-get update It showed me the following error. flags: qr rd ra QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 >HEADER>HEADER>HEADER<<- opcode: QUERY, status: NOERROR, id: 54875 If not, next step is to try host -v: jinx:776 Z$ host -v us. W: You may want to run apt-get update to correct these problemsĬan you resolve any of those hosts from the command line? jinx:775 Z$ ping us. W: Some index files failed to download, they have been ignored, or old ones used instead. W: Failed to fetch Could not resolve 'us.' Linux nematode 2.6.28-19-server #66-Ubuntu SMP Sat Oct 16 18:41: i686 GNU/LinuxĬould not resolve 'us.'Įrr jaunty-updates/main Translation-en_USĮrr jaunty-updates/restricted Translation-en_USĮrr jaunty-updates/universe Translation-en_USĮrr jaunty-updates/multiverse Translation-en_USĮrr jaunty-security/main Translation-en_USĮrr jaunty-security/restricted Translation-en_USĮrr jaunty-security/universe Translation-en_USĮrr jaunty-security/multiverse Translation-en_US Are the servers temporarily broken, or is my APT misconfigured and using old servers? In short, how do I fix this? Running sudo apt-get update fails on my server (that has an internet connection).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |