Bobcares

Could not connect to mirrors.linode.com:80 | Fixed

by | Jan 6, 2025

We can easily resolve the “Could Not Connect to mirrors.linode.com:80” error using the steps in our article. Bobcares, as a part of our Linode Managed Services offers solutions to every query that comes our way.

Overview
  1. Resolving the “Could Not Connect to mirrors.linode.com:80” Error
  2. Common Causes
  3. How to Fix It?
  4. Prevention Tips
  5. Conclusion

Resolving the “Could Not Connect to mirrors.linode.com:80” Error

The error message “Could not connect to mirrors.linode.com:80” often appears when a system fails to establish a connection to the Linode mirror server. This server provides essential resources like software packages and updates, and the error disrupts the normal operation of package management tools. Here, we break down the causes, symptoms, and solutions to resolve this issue effectively.

What is mirrors.linode.com?

Linode Mirror Server: A server hosted by Linode that mirrors Ubuntu packages and updates.

Port 80: The default port for HTTP traffic. The error indicates a failure to connect over this port.

Common Causes

1. Network Connectivity Issues: The Linode instance may lack outbound network connectivity.

2. Firewall Blocking Connections: Firewall rules may block access to the mirror server.

3. End of Life (EOL) Ubuntu Version: If the Ubuntu version is past its EOL, the Linode mirror server stops supporting it.

4. Misconfigured Sources: Incorrect entries in the /etc/apt/sources.list file can cause the system to look for unavailable resources.

5. Proxy Server Problems: Misconfigured proxies may block access to the mirror server.

When attempting an update, we may encounter:

Could not connect to mirrors.linode.com:80

Or similar messages indicating the inability to connect to the Linode mirror server.

How to Fix It?

1. Verify Network Connectivity

Test if the Linode instance has outbound connectivity:

curl -I linode.com
curl -I google.com

2. Check Firewall Rules

Ensure that the firewall isn’t blocking connections to port 80:

iptables -L -nv –line-numbers

Allow required ports:

sudo ufw allow 80/tcp
sudo ufw allow 443/tcp

3. Update Sources List for EOL Versions

Modify /etc/apt/sources.list to use Ubuntu’s old-release server:

sudo nano /etc/apt/sources.list

Replace:

http://mirrors.linode.com/ubuntu

With:

http://old-releases.ubuntu.com/ubuntu

4. Ping or Trace the Server

Check if the server is reachable:

ping mirrors.linode.com
traceroute mirrors.linode.com

5. Update Ubuntu

Consider upgrading to a supported Ubuntu version for continued updates:

sudo do-release-upgrade

Prevention Tips

1. Regular Updates: Avoid using EOL Ubuntu versions by upgrading the system timely.

2. Firewall Maintenance: Keep firewall rules updated to ensure smooth connectivity.

3. Use Supported Sources: Always verify the validity of the sources in the configuration file.

[Want to learn more? Click here to reach us.]

Conclusion

The “Could not connect to mirrors.linode.com:80” error typically arises due to network issues, outdated Ubuntu versions, or misconfigurations. By following the steps outlined, we can restore connectivity and ensure smooth access to necessary updates. Keeping the system updated and well-maintained is essential to prevent such errors in the future.

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF