Unable to connect Analytics – “Error: cURL error 2:”

  • Resolved MP

    (@therealmikep)


    4 years, 5 months ago

    Continuously displays “Error: cURL error 2:” while trying to connect Analytics. Search Console connects fine.

    I’ve run through as many troubleshooting suggestions as I can find: full disconnect and reinstall in private browser, default theme, no plugins, etc.

    2 Console errors:
    Failed to load resource: the server responded with a status of 500 (Internal Server Error) -> /wp-json/google-site-kit/v1/modules/analytics/data/accounts-properties-profiles?existingPropertyID=&_locale=user:1 Failed to load resource: the server responded with a status of 500 (Internal Server Error)

    googlesitekit-api.js?ver=1.9.0:1 Google Site Kit API Error -> googlesitekit-api.js?ver=1.9.0:1

    Verified correct Google SC and Analytics accounts being used.

    Glad to share screenshots, etc.
    Please help.

    Thanks!

    • This topic was modified 4 years, 5 months ago by MP.
Viewing 6 replies - 1 through 6 (of 6 total)

  • @therealmikep really appreciate the details.

    You may be affected by this issue we’re currently investigating, so it would be great to troubleshoot with you. Could you let us know/ provide the following:

    1) Is this your first time trying to connect to Analytics on this site?

    2) Do you have additional sites using Site Kit in the same hosting environment/ server that you are able to connect to Analytics?

    3) Your Site Health Information

    4) Your hosting provider and plan

    I am getting the same error as well.

    @iqwebsolutions feel free to follow this topic or open a new topic if you’d like us to look into and track your case specifically.

    Thread Starter MP

    (@therealmikep)

    @reneesoffice

    Sure thing!

    1) I don’t recall if my above post was the first time attempting to connect. But it failed to auth since the first time trying on this site (and a few others).

    2) Yes, confirmed at least one other install on the same server and environment.

    3) Site health:
    – Running an outdated PHP version (but the site mentioned above is running same version as this)
    – Two PHP modules not enabled (but they’re not available on the site above either)

    4) Hosting provider and plan: VPS leased from a well-known hosting company, fully self managed.

    @therealmikep thanks for the reply!

    We’re suspecting this error is related to server configurations particularly with the version of PHP and cURL being used in the environment. We think this Guzzle issue may have something to do with it.

    As we continue to monitor this, could you provide the Site Health that is on the Info tab as seen in this screenshot here or through this form?

    @therealmikep I’m following up on your topic regarding the issue with Analytics.

    While we were not able to recreate the issue, we indeed suspect that it could be related to an aspect of the server environment your site is in at your host- particularly the cURL library being used (see this issue for more details).

    Unfortunately, we’re limited on the solutions we can provide there, but we’re working on a way to detect these issues sooner at setup. The next best course of action would be to contact your host.

    We greatly appreciate your report and patience as we looked into this.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Unable to connect Analytics – “Error: cURL error 2:”’ is closed to new replies.