-
Notifications
You must be signed in to change notification settings - Fork 799
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Debugger / Site Health Displaying False-Positive Errors #12881
Comments
Ticket: 2169467-zen
|
Ticket: 2202245-zen
|
Ticket: 2213829-zen
|
Tix: 2250241-zen
|
Ticket: 2254863-zen
|
Ticket: 2272084-zen Jetpack Debug is good. Site ID: 155898264
|
2290973-zen
|
2299364-zen
|
2290680-zen
|
Ticket: 2312741-zen
|
Ticket: 2317282-zen
|
2318941-zen |
@aheckler and @jeremypaavola - Site ID and JPDB result are good enough. Avoid providing site URLs in this public issue ;) |
Note: this is a Team51 site |
Updating the priority to |
2328536-zen |
2329845-zen |
324579-zen |
2328310-zen |
Ticket: 2343601-zen
|
2341843-zen |
2360289-zen
|
I'd like to see if we can break up this issue some.
|
2409631-zen
|
Also reported in 2463999-zen, user on Jetpack 7.8. |
User on 7.9, Site Health reports a curl 28 timeout error. All tests pass in the debugger. |
The loopback request mentioned in the ticket is from Core -- their site did not respond to a request to itself as expected ( https://github.com/WordPress/WordPress/blob/f1b5f2aa94c45aa087e96ac91ca53d241ee3146b/wp-admin/includes/class-wp-site-health.php#L1642 ). The All in all, I think that is the site debug working as expected. It isn't a false positive error -- loopback isn't working as expected and whatever the http request, it was expecting to get a response back within 10 seconds and didn't. That could indicate the test is expecting something too quickly or network issues between the Jetpack site and the server, etc. I think this site is just slow. |
2496139-zen |
2514574-zen |
2525376-zen |
@kraftbj - We're seeing more and more reports. Do you think we should report this in a separate issue? |
2535860-zen |
2535296-zen |
2535251-zen |
2531506-zen |
2534598-zen |
2540352-zen |
Going to just not run the self test and moving forward with using the newer suite. |
2543967-zen |
No need to keep reporting these. |
@kraftbj Just saw another instance of this in 2601672-zen using Jetpack 8.0. Should this still be happening or do you think there's a new problem? |
@kraftbj I have one in 2615740-zen as well.
They're on 8.0 and the debug is OK. |
@chaselivingston & @csonnek Pulling out the old debugger is coming in Jetpack 8.1 and converting the server-side old debugger to use the new suite is pending review in D37439 |
Another report in 17798236-zen |
Seeing this happening consistently in Atomic sites atm. When running jetpack status, common error message is:
Disconnecting and reconnecting doesn't help. 2629897-zen |
This issue should remain closed and any others should have a new ticket. The impacted test was removed in #14198, but that code didn't ship until 8.1 (today). If there are still issues, please confirm they are not running an older version. If they are running 8.1 or higher, please open a new issue as it is not related to this one since the test is no longer running by default (requires a filter to enable it currently). |
Purpose of this GitHub issue
Details of the issue.
Everything looks great!
.What to report
Other info
Originally in 3927-gh-jpop-issues
The text was updated successfully, but these errors were encountered: