[Bug]: ppa.launchpad.net is timing out

[varadins]

System

linux

Architecture

amd64

OS version

Ubuntu 24.0.4

Installation method

• Binary
• Source code
• Docker container

Description

For the past week launchpad.net has been timing out. Quick google search shows this is a widespread issue.

Ign:30 https://ppa.launchpadcontent.net/lifailon/lazyjournal/ubuntu noble InRelease                                                     
Ign:30 https://ppa.launchpadcontent.net/lifailon/lazyjournal/ubuntu noble InRelease
Ign:30 https://ppa.launchpadcontent.net/lifailon/lazyjournal/ubuntu noble InRelease
Err:30 https://ppa.launchpadcontent.net/lifailon/lazyjournal/ubuntu noble InRelease
  Could not connect to ppa.launchpadcontent.net:443 (185.125.190.80), connection timed out
Fetched 15.9 MB in 37s (425 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
W: Failed to fetch https://ppa.launchpadcontent.net/lifailon/lazyjournal/ubuntu/dists/noble/InRelease  Could not connect to ppa.launchpadcontent.net:443 (185.125.190.80), connection timed out
W: Some index files failed to download. They have been ignored, or old ones used instead.

[github-actions]

The issue reports that Ubuntu's apt package manager cannot connect to ppa.launchpadcontent.net for PPA updates, consistently timing out and failing to fetch index files. This appears to be a widespread connectivity problem, likely on Launchpad's side, not user-specific. The recommended action is to wait for Launchpad to resolve the outage, and check with their status page or support for updates.

[Lifailon]

The "connection timed out" error indicates that your package manager is unable to contact the Ubuntu PPA mirrors.

This may be due to your regional restrictions. I checked the installation process using GitHub Actions workflow, and it's currently successful. This also confirms that the repository and the PPA itself are configured correctly.

As you mentioned, if this is a widespread issue that many users have recently reported, it's likely caused by temporary glitches on the Launchpad side.

Since this is an external issue independent of this project, I'll close this issue. You can use another installation method, such as directly downloading the executable from GitHub using the installation script.