Related

Tool Instant DNS Lookup Tool Tool
Other domains pointing to my IP address and mirroring my website Question Question
DNS Record not updated or changing ? How long it will take to effect Question Question

Question

I started getting an error message when I log in Failed to connect to ubuntu.com meta-release-lts

Posted February 11, 2019 36.1k views
DNSUbuntu 18.04

0 packages can be updated.
0 updates are security updates.

Failed to connect to https://changelogs.ubuntu.com/meta-release-lts. Check your Internet connection or proxy settings

No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.2 LTS
Release: 18.04
Codename: bionic

ping changelogs.ubuntu.com
PING changelogs.ubuntu.com (91.189.95.15) 56(84) bytes of data.
64 bytes from rubay.canonical.com (91.189.95.15): icmpseq=1 ttl=52 time=70.7 ms
64 bytes from rubay.canonical.com (91.189.95.15): icmpseq=2 ttl=52 time=69.4 ms
64 bytes from rubay.canonical.com (91.189.95.15): icmp_seq=3 ttl=52 time=70.3 ms
^C
— changelogs.ubuntu.com ping statistics —
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 69.424/70.170/70.758/0.634 ms

https://askubuntu.com/questions/1073455/log-in-error-after-upgrade-to-18-04-lts

Add a comment
yesitsme
By:
yesitsme

Related

Tool Instant DNS Lookup Tool Tool
Other domains pointing to my IP address and mirroring my website Question Question
DNS Record not updated or changing ? How long it will take to effect Question Question

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
1 answer
charleslapress May 19, 2019

Reading this: https://ubuntuforums.org/showthread.php?t=2391641
addressed it with this: sudo rm /var/lib/ubuntu-release-upgrader/release-upgrade-available

Reply Report
  • axelitus August 28, 2019

    Or just empty the file with:

    sudo truncate -s 0 /var/lib/ubuntu-release-upgrader/release-upgrade-available

    It seems that when the connection can be re-established to check the changelog, this file is not cleaned up properly. So, after the first time it cannot connect, the message is stored in the file and never erased so it will always show up as if it cannot connect (when actually it is connecting).

    Reply Report
Submit an Answer

Related

Looking for something else?

Ask a new question Search for more help