Bug 15960 - Sanity check fails: default CONNECTIVITY_CHECK_URIS unreachable
Summary: Sanity check fails: default CONNECTIVITY_CHECK_URIS unreachable
Status: RESOLVED FIXED
Alias: None
Product: BitBake
Classification: Build System, Metadata & Runtime
Component: bitbake (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Undecided normal
Target Milestone: 0.0.0
Assignee: Richard Purdie
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2025-08-29 09:46 UTC by ​Thomas Vandenabeele
Modified: 2025-09-04 14:33 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ​Thomas Vandenabeele 2025-08-29 09:46:17 UTC
Since August 27, 2025, the default sanity check in Yocto fails after recreating the build folder and running bitbake. The connectivity test URL https://yoctoproject.org/connectivity.html is no longer accessible, and the build aborts with the following error:

ERROR:  OE-core's config sanity checker detected a potential misconfiguration.
    Either fix the cause of this error or at your own risk disable the checker (see sanity.conf).
    Following is the list of potential problems / advisories:
    Fetcher failure for URL: 'https://yoctoproject.org/connectivity.html'. URL doesn't work.
    Please ensure your host's network is configured correctly.
    Please ensure CONNECTIVITY_CHECK_URIS is correct and specified URIs are available.
    If your ISP or network is blocking the above URL,
    try with another domain name, for example by setting:
    CONNECTIVITY_CHECK_URIS = "https://www.example.com/"    You could also set BB_NO_NETWORK = "1" to disable network
    access if all required sources are on local disk.

Observed behavior:
- The default connectivity check URL https://yoctoproject.org/connectivity.html fails consistently.
- Updating CONNECTIVITY_CHECK_URIS to either https://www.yoctoproject.org/connectivity.html or https://google.com in local.conf resolves the issue.
- The problem occurs across multiple build systems and different networks/PCs, so it does not appear to be a local network or ISP issue.

Expected behavior:
The default connectivity check at https://yoctoproject.org/connectivity.html should succeed.

Question:
Has the Yocto Project recently changed or deprecated this URL?
Comment 1 ​Thomas Vandenabeele 2025-08-29 09:51:34 UTC
Looks like it is fixed today.

Before today:
$ curl https://yoctoproject.org/connectivity.html
curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: https://curl.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.

Today:
$ curl -I https://yoctoproject.org/connectivity.html
HTTP/2 301 
content-type: text/html; charset=utf-8
location: https://www.yoctoproject.org/connectivity.html
x-redirector-version: 192efcc
date: Fri, 29 Aug 2025 09:50:38 GMT


Seems like it was a SSL certificate error?