Site-kit-wp: Analytics: existing account not found, re-fetching account does not work

Created on 19 May 2020 · 9Comments · Source: google/site-kit-wp

Bug Description

Several users have reported the Analytics module is not able to detect their existing accounts. Clicking "Re-fetch my account" also does not locate the account.

-- Various browser console errors are on the request to connect the service (locale=user): _404_, _500_ (sometimes includes a _WP Error data in response, curl error 2_)
-- Can happen in various hosting environments, but unable to replicate
-- Still occurs in an incognito browser

Steps to reproduce

Go to '...'
Click on '....'
Scroll down to '....'
See error

Screenshots

Console errors:

404 error re-fetch analytics

500 error re-fetch analytics

Additional Context

PHP Version:
OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Plugin Version [e.g. 22]
Device: [e.g. iPhone6]

1548 might also be related

_Do not alter or remove anything below. The following sections will be managed by moderators only._

Acceptance criteria

Implementation Brief

QA Brief

Changelog entry

Escalation Bug

Source

ernee

All 9 comments

Console error:

Google Site Kit API Error 
{…}

code: "unknown"

data: {…}

reason: ""

status: 500

<prototype>: Object { … }

message: "cURL error 2: easy handle already used in multi handle"

<prototype>: {…}

__defineGetter__: function __defineGetter__()

__defineSetter__: function __defineSetter__()

__lookupGetter__: function __lookupGetter__()

__lookupSetter__: function __lookupSetter__()

__proto__: 

constructor: function Object()

hasOwnProperty: function hasOwnProperty()

isPrototypeOf: function isPrototypeOf()

propertyIsEnumerable: function propertyIsEnumerable()

toLocaleString: function toLocaleString()

toString: function toString()

valueOf: function valueOf()

<get __proto__()>: function __proto__()

<set __proto__()>: function __proto__()
googlesitekit-api.js:1:11004
    g https://peacerivercampground.com/wp-content/plugins/google-site-kit/dist/assets/js/googlesitekit-api.js?ver=1.8.0:1
    k https://peacerivercampground.com/wp-content/plugins/google-site-kit/dist/assets/js/googlesitekit-vendor.js?ver=1.8.0:1
    _invoke https://peacerivercampground.com/wp-content/plugins/google-site-kit/dist/assets/js/googlesitekit-vendor.js?ver=1.8.0:1
    e https://peacerivercampground.com/wp-content/plugins/google-site-kit/dist/assets/js/googlesitekit-vendor.js?ver=1.8.0:1
    k https://peacerivercampground.com/wp-content/plugins/google-site-kit/dist/assets/js/googlesitekit-vendor.js?ver=1.8.0:1
    e https://peacerivercampground.com/wp-content/plugins/google-site-kit/dist/assets/js/googlesitekit-vendor.js?ver=1.8.0:1
    e https://peacerivercampground.com/wp-content/plugins/google-site-kit/dist/assets/js/googlesitekit-vendor.js?ver=1.8.0:1

ernee on 19 May 2020

Error: https://jmp.sh/S75ub4d
https://jmp.sh/I8wNsuG

ernee on 22 May 2020

Same happened to me in Safari (latest version). Worked fine in Chrome

vladarte on 23 May 2020

@ernee Sounds similar to #1548

jamesozzie on 25 May 2020

Tested

Ran a series of tests around Analytics setup and re-fetching my account. Was unable to reproduce this with the latest 1.11.1 release.

Sending to L2.

cole10up on 13 Jul 2020

Just noting here that we're suspecting some of these issues to be related to this issue with Guzzle: https://github.com/guzzle/guzzle/issues/2617

ernee on 14 Jul 2020

@felixarntz I haven't able to reproduce this issue either. After researching it a little bit, I tend to say that it is not our issue at all. This seems to be cURL related problem that happened on some hosting poviders like GoDaddy or its resellers. See this comment for reference.

Plus, it looks like this issue has stopped appearing for folks that makes me think that it might be already fixed by hosting providers and we have nothing to do here. Assigning this to you to make a decision what to do next with it.

eugene-manuilov on 24 Jul 2020

@ernee This issue (like the other cURL issues we've been seeing) are most likely out of our control. We're working on detecting this problem early on, per #1549, so that users should be informed before even setting up Site Kit. Let's keep an eye on these issues and support threads and inform the reporters that this is likely a host-specific problem, and we're working on some changes to detect it earlier.