Some users are constantly being asked to re-authenticate Site Kit after some days. A notice appears from their dashboard as below:

This seems to occur in particular with the Analytics module connected.
In some cases deactivating and deleting the plugin in full works (When setting up from a browser incognito window)
Examples of users facing this issue:
This issue may be related to ModSecurity configurations as per #1113
One user was happy to share information as below:
https://vimeo.com/390419409 (Access using "Google")
_Do not alter or remove anything below. The following sections will be managed by moderators only._
This video is private
https://vimeo.com/390419409
what is the password
This video is private
https://vimeo.com/390419409
what is the password
pass: google
Setup 2 SK sessions:
SK 1.3.0 with Search Console, Adsense, Analytics, Page View Insights and Tag Manager - With anonymous tracking
SK 1.3.1 with Search Console, Analytics, and Tag Manager - No anonymous tracking
During my testing I left these idle after specific scenarios: Uninstalling services, reinstalling services, navigating to and from the dashboard, adjusting duration on the dashboard. I wasn't able to see the issue today.
Sending to Level 2 Escalarion
@jamesozzie In the case of users who are setting up Site kit on many, many sites - (eg. they mention "100s of sites") - with a single (Google) login - I suspect they may be hitting an OAuth limitation (https://github.com/google/site-kit-wp/issues/1115) that restricts the number of OAuth sessions a single account can maintain and causes older access (refresh) tokens to become invalidated.
More information on general OAuth limitations: https://developers.google.com/identity/protocols/OAuth2#expiration. This is an account/API restriction and the recommendation here is:
If you need to authorize multiple programs, machines, or devices, one workaround is to limit the number of clients that you authorize per user account to 15 or 20.
Worth noting that some services further restrict the number of connections (to 25), for example Analytics: https://developers.google.com/analytics/devguides/config/mgmt/v3/authorization#invalid_grant
We can keep investigating the other cases reported here.
@adamsilverstein Good to know, thanks for the update. I'll follow up with users.
Reproduced
Pre-condition:
Notice when logged in as user without GA account:

SK Dashboard:

Moving to Execution
@jamesozzie We recently corrected a bug in the service that may help alleviate or resolve some of the issues reported here.
To summarize the bug we fixed: when the plugin detected a failed token under certain circumstances it previously made a call to invalidate the token which _had the unfortunate side effect of invalidating all of the user's access and refresh tokens_.
The result was that user's who became disconnected from one site (including disconnecting from the user dropdown) were then additionally disconnected from all sites under their login.
After this change, we no longer invalidate the user's tokens. So for example when a user sets up 26 websites under one account, the first account will become invalidated due to API/User limits, however, the other 25 will retail valid logins.
@jamesozzie any insight from the forum side which indicates this is no longer an issue, other for users with more than 25 sites?
@ThierryA All confirmed as resolved or awaiting user response(2). No users have reported the same issue since the plugin update. I think we can mark this issue as resolved, great work @adamsilverstein
Confirming this overall issue has been resolved. We are no longer seeing regular reports from users that they need to re-authenticate. There are still some issues with setup being tackled elsewhere (eg unicode domains, domain mismatches), however the main issue with users loosing access to all sites is resolved. We have followed up with user support threads as well.
Closing this issue as resolved.
I have a brand new WordPress install and I'm getting this error:

@dpouliot Thanks for reporting. Initial support requests can be submitted using the plugins WordPress support forum.
If you open a new support topic there while providing your Site Health information we can try and determine the root cause in your case, while revisiting this GitHub issue if necessary.
I removed www. from my Wordpress site settings and now it works, thanks!
Most helpful comment
I removed www. from my Wordpress site settings and now it works, thanks!