{"id":5566,"date":"2024-10-14T01:21:45","date_gmt":"2024-10-13T19:51:45","guid":{"rendered":"https:\/\/www.veeble.org\/kb\/?p=5566"},"modified":"2025-03-17T10:41:27","modified_gmt":"2025-03-17T05:11:27","slug":"fix-the-failed-to-fetch-error-in-ubuntu-apt-package-manager","status":"publish","type":"post","link":"https:\/\/www.veeble.com\/kb\/fix-the-failed-to-fetch-error-in-ubuntu-apt-package-manager\/","title":{"rendered":"Fix the ‘Failed to Fetch’ Error in Ubuntu APT Package Manager"},"content":{"rendered":"\n

Ever tried upgrading your system or installing some new package<\/a> in Ubuntu, but it just keeps popping up with this annoying error?<\/p>\n\n\n\n

\"Failed<\/a><\/figure>\n\n\n\n

You’re not alone! This “Failed to Fetch” error happens to many Ubuntu users. But don\u2019t worry, in this guide, we\u2019ll break down what causes this error and how you can easily fix it.<\/p>\n\n\n\n

Do you know the causes of this error: \"Failed to Fetch\"?<\/strong>
It generally happens while APT, the package manager, can't pull packages from the repositories. Some of the possible reasons are here:
1. Outdated or Incorrect Repositories
2. Network Issues
3. Repository Server is Down
4. Proxy\/DNS Settings
5. Firewall Blocking<\/pre>\n\n\n\n
Now that you know what could be causing the issue, let\u2019s dive into how to fix it. \ud83d\ude03<\/strong><\/p>\n\n\n\n
<\/p>\n\n\n
Check Your Internet Connection<\/h3>\n\n\n
Run a simple command to check your Internet connection. i.e;<\/p>\n\n\n\n
ping google.com<\/code><\/pre>\n\n\n\n
This would output the response if everything is okay with your network, like below:<\/p>\n\n\n\n
\"check<\/a><\/figure>\n\n\n\n
Otherwise, you fix up the network and move on.<\/p>\n\n\n\n
<\/p>\n\n\n
Update Your Repository List<\/h3>\n\n\n
Run the below command to clean cache and update the list of available packages:<\/p>\n\n\n\n
sudo apt clean -y\nsudo apt update -y<\/code><\/pre>\n\n\n\n
Sometimes, the repositories just need to be refreshed. The above command will refresh it!<\/p>\n\n\n\n
If you are still facing issues like before for updating too. Relax and try updating the correct repositories in your Ubuntu sources.list file. To do it, refer to the blog: https:\/\/www.veeble.org\/kb\/sources-list-file-urls-ubuntu\/<\/a><\/p>\n\n\n\n
Go to the next step if the issue is not solved by now. \ud83e\udd7a<\/p>\n\n\n\n
<\/p>\n\n\n
Fix DNS Issues<\/h3>\n\n\n
Try changing your DNS to a public DNS server like Google\u2019s. To do it, just open the \/etc\/resolv.conf file in a text editor and then update Google nameservers in it, and save it.<\/p>\n\n\n\n
sudo nano \/etc\/resolv.conf<\/code><\/pre>\n\n\n\n
Google nameservers were 8.8.8.8 and 8.8.4.4. Just update them as you can see from the below screenshot:<\/p>\n\n\n\n
\"Update<\/a><\/figure>\n\n\n\n
<\/p>\n\n\n\n
Now, update again with the command: apt update<\/code> -y
This should solve the issue if DNS was the problem.<\/p>\n\n\n\n
If you\u2019re behind a proxy (e.g., in a corporate environment), the proxy could be causing the issue. If the proxy is not configured properly, it can block access to repositories. Set the correct proxy settings by editing your environment variables in ~\/.bashrc<\/strong>
Refer: Ubuntu Forums<\/a><\/pre>\n\n\n\n
If none of the above solutions work, try rebooting the system and also check the firewall for any blocks to the configured repository servers.<\/p>\n\n\n\n