search

Automattic / wp-calypso

The JavaScript and API powered WordPress.com
https://developer.wordpress.com
GNU General Public License v2.0
12.41k stars 1.99k forks source link

Bug: 'Please check your Primary Site's Jetpack connection' error sometimes directs to incorrect wp-admin, blocking users from fixing #79324

Open cuemarie opened 1 year ago

cuemarie commented 1 year ago

This issue was reported here: https://github.com/Automattic/jpop-issues/issues/8387 Then merged over into this feature request: https://github.com/Automattic/wp-calypso/issues/56550 I think we can still do a better job tracking and triaging this as it's own report, so I'm recreating here.

Quick summary

Users are stuck on wordpress.com/stats/day/ with the notice Please check your Primary Site's Jetpack connection when either no primary site selected or primary site legitimately disconnected from Jetpack (i.e. old self hosted site that's no longer in use).

Markup 2023-06-25 at 10 03 58

The wp-admin link shown on the error tries to link to a different site's dashboard.

From @Nic-Sevic

wpcom users are not able to resolve this themselves and shouldn't be seeing this message in the first place. The issue appears to be that the correct assignment of the primary site isn't happening. Users could potentially fix this on their own by changing the primary site in their account but there's nothing to indicate this to them.

And

It looks like the "Please check your Primary Site's Jetpack connection" error should show up only when user has one site and that one isn't reachable: fbhepr%2Skers%2Spnylcfb%2Spyvrag%2Szl%2Qfvgrf%2Spbagebyyre.wf%3Se%3Q0639q560%23546-og In these cases, users had other sites connected so I'm not sure how they got here. That may be the reason this is so hard to reproduce.

Steps to reproduce

Steps to reproduce have not been nailed down yet.

A clear and concise description of what you expected to happen.

Primary site should default to one that's live if the previous value no longer exists Even if primary site not available (not connected to JP), when you're trying to go to another site it shouldn't matter

What actually happened

Regardless of site user is trying to go to, they get the Please check your Primary Site's Jetpack connection notice and then have no indication of what's wrong.

Impact

Some (< 50%)

Available workarounds?

No and the platform is unusable

Platform (Simple and/or Atomic)

Atomic

Logs or notes

No response

cuemarie commented 1 year ago

Recent interactions noted on https://github.com/Automattic/wp-calypso/issues/56550 :

  1. 6460967-zd-woothemes - Troubleshooting Thread: p1687689160318619-slack-C03TY6J1A
  2. 6463319-zd-woothemes - Troubleshooting Thread: p1687678991583859-slack-C03TY6J1A
  3. 6521896-zd-woothemes - Troubleshooting Thread: p1689029333516649-slack-C03TY6J1A
github-actions[bot] commented 1 year ago

Support References

This comment is automatically generated. Please do not edit it.