duhlina

This worked for me as well!
THANK YOU, THANK YOU, THANK YOU!!!!!!!!!!!!!!!!!!!!!!!!!!!

I do not have TranslatePress Plugin…

GET https://my.yoast.com/api/sites/current 404 Not Found
HTTP API Transport: curl
DNS Resolution Time: 0.0011
Connection Time: 0.0092
Transfer Start Time (TTFB): 0.2796
Response Size: 65 B
Response Content Type: text/plain;charset=UTF-8
IP Address: 104.18.26.25
WPSEO_MyYoast_Api_Request->do_request()
wp-content/plugins/wordpress-seo/inc/class-my-yoast-api-request.php:111
WPSEO_MyYoast_Api_Request->fire()
wp-content/plugins/wordpress-seo/inc/class-my-yoast-api-request.php:68
Yoast\W\S\S\H\Curl_Runner->check_can_reach_my_yoast_api()
wp-content/plugins/wordpress-seo/src/services/health-check/curl-runner.php:148
Yoast\W\S\S\H\Curl_Runner->run()
wp-content/plugins/wordpress-seo/src/services/health-check/curl-runner.php:104
Yoast\W\S\S\H\Health_Check->run_and_get_result()
wp-content/plugins/wordpress-seo/src/services/health-check/health-check.php:66
WP_Site_Health->perform_test()
wp-admin/includes/class-wp-site-health.php:192

SEO just updated a few days ago, 19.1 installed.
WordPress 6.0 installed
No Yost addons
Theme is BOSS with latest update.
————————————————————————————-

Site Health
Good
Status
Info
Site Health Status
The site health check shows critical information about your WordPress configuration and items that require your attention.

2 recommended improvements

A scheduled event is late
Performance
The scheduled event, action_scheduler_run_queue, is late to run. Your site still works, but this may indicate that scheduling posts or automated updates may not work as intended.

Comments break into multiple pages
SEO
Comments on your posts break into multiple pages. As this is not needed in 999 out of 1000 cases, we recommend you disable it. To fix this, uncheck "Break comments into pages..." on the Discussion Settings page.
Go to the Discussion Settings page
This was reported by the Yoast SEO plugin

Passed tests

Well now, that is interesting. I uninstalled it and no errors. I reinstalled it and it is messing with my Jetpack. How is that possible?
—————————————————————————————–

https://jetpack.wordpress.com/jetpack.test/1/	200 OK
HTTP API Transport: curl
DNS Resolution Time: 0.0004
Connection Time: 0.0446
Transfer Start Time (TTFB): 0.1826
Response Size: 22 B
Response Content Type: text/plain;charset=utf-8
IP Address: 192.0.78.33
Jetpack_Cxn_Tests->test__outbound_http()
wp-content/plugins/jetpack/_inc/lib/debugger/class-jetpack-cxn-tests.php:395
Jetpack_Cxn_Test_Base->run_test()
wp-content/plugins/jetpack/_inc/lib/debugger/class-jetpack-cxn-test-base.php:140
{closure}()
wp-content/plugins/jetpack/_inc/lib/debugger/debug-functions.php:56
WP_Site_Health->perform_test()
wp-admin/includes/class-wp-site-health.php:192
WP_Site_Health->enqueue_scripts()
wp-admin/includes/class-wp-site-health.php:143
do_action('admin_enqueue_scripts')
wp-includes/plugin.php:476

—————————————————————————————
…and this comes back: `https://my.yoast.com/api/sites/current 404 Not Found
HTTP API Transport: curl
DNS Resolution Time: 0.0015
Connection Time: 0.0098
Transfer Start Time (TTFB): 0.2758
Response Size: 65 B
Response Content Type: text/plain;charset=UTF-8
IP Address: 104.18.26.25
WPSEO_MyYoast_Api_Request->do_request()
wp-content/plugins/wordpress-seo/inc/class-my-yoast-api-request.php:111
WPSEO_MyYoast_Api_Request->fire()
wp-content/plugins/wordpress-seo/inc/class-my-yoast-api-request.php:68
Yoast\W\S\S\H\Curl_Runner->check_can_reach_my_yoast_api()
wp-content/plugins/wordpress-seo/src/services/health-check/curl-runner.php:148
Yoast\W\S\S\H\Curl_Runner->run()
wp-content/plugins/wordpress-seo/src/services/health-check/curl-runner.php:104
Yoast\W\S\S\H\Health_Check->run_and_get_result()
wp-content/plugins/wordpress-seo/src/services/health-check/health-check.php:66
WP_Site_Health->perform_test()
wp-admin/includes/class-wp-site-health.php:192
WP_Site_Health->enqueue_scripts()
wp-admin/includes/class-wp-site-health.php:143
do_action(‘admin_enqueue_scripts’)
wp-includes/plugin.php:476`

There is no paid add-on. The site was running exactly as it is for 2-1/2 years and this suddenly appeared and continues…

I was not trying to achieve anything. It just appeared when I looked at the site health about two weeks ago. I just remembered that I can post a question here. It looks like this may be a global issue that not many are seeing because I installed the Yoast on a test site and it does the same thing. Plugin requirements are not the issue. This plugin has been in use on my site for about two and a half years.
Thank you!