“easy handle already used in multi handle” when connecting to GA

  • Resolved aleksanderadamski

    (@aleksanderadamski)


    4 years, 9 months ago

    I’ve installed google site kit on my website ([ redundant link removed ]). It has verified the ownership and connected to search console correctly. However when trying to connect to google analytics it only returns the message: “Error: cURL error 2: easy handle already used in multi handle”.

    I’ve searched other topics and double checked account priviliges and they seem to be fine. Only lead I have for now is this topic – https://github.com/google/site-kit-wp/issues/1548

    Here’s the site health dump:

    
### wp-core ###

version: 5.4.1
site_language: pl_PL
user_language: pl_PL
timezone: Europe/Warsaw
permalink: /%category%/%postname%/
https_status: true
user_registration: 0
default_comment_status: open
multisite: false
user_count: 55
dotorg_communication: true

### wp-paths-sizes ###

wordpress_path: /home/pmiorgpl/public_html
wordpress_size: 42,08 MB (44126578 bytes)
uploads_path: /home/pmiorgpl/public_html/wp-content/uploads
uploads_size: 384,94 MB (403637890 bytes)
themes_path: /home/pmiorgpl/public_html/wp-content/themes
themes_size: 10,75 MB (11272648 bytes)
plugins_path: /home/pmiorgpl/public_html/wp-content/plugins
plugins_size: 29,00 MB (30410582 bytes)
database_size: 4,76 MB (4987829 bytes)
total_size: 471,53 MB (494435527 bytes)

### wp-active-theme ###

name: PMI Theme (PMI)
version: 0.0.2
author: Mateusz Misiak
author_website: https://www.behance.net/MateuszMis94b3
parent_theme: none
theme_features: post-thumbnails, html5, post-formats, custom-logo, responsive-embeds, menus, widgets
theme_path: /home/pmiorgpl/public_html/wp-content/themes/PMI

### wp-themes-inactive (5) ###

Twenty Fifteen: version: 2.6, author: zespó? WordPressa
Twenty Nineteen: version: 1.5, author: zespó? WordPressa
Twenty Seventeen: version: 2.3, author: zespó? WordPressa
Twenty Sixteen: version: 2.1, author: zespó? WordPressa
Twenty Twenty: version: 1.3, author: zespó? WordPressa

### wp-mu-plugins (1) ###

WP Migrate DB Compatibility: version: 1.2, author: Delicious Brains

### wp-plugins-active (12) ###

Advanced Custom Fields PRO: version: 5.8.11, author: Elliot Condon
Conditional Menus: version: 1.1.8, author: Themify
Contact Form 7: version: 5.1.9, author: Takayuki Miyoshi
Custom Post Type UI: version: 1.7.4, author: WebDevStudios
Duplicate Page: version: 4.2, author: mndpsingh287
Max Mega Menu: version: 2.7.7, author: megamenu.com
Redirection: version: 4.8, author: John Godley
Regenerate Thumbnails: version: 3.1.3, author: Alex Mills (Viper007Bond)
SBGD Wrapper Block: version: 1.1.6, author: Shawn Beelman Graphic Design
Site Kit by Google: version: 1.8.1, author: Google
WP Migrate DB: version: 1.0.13, author: Delicious Brains
WP Rollback: version: 1.7.0, author: Impress.org

### wp-plugins-inactive (3) ###

Akismet Anti-Spam: version: 4.1.5, author: Automattic
Hello Dolly: version: 1.7.2, author: Matt Mullenweg
iThemes Security Pro: version: 5.0.1, author: iThemes

### wp-media ###

image_editor: WP_Image_Editor_GD
imagick_module_version: Niedost?pne
imagemagick_version: Niedost?pne
gd_version: bundled (2.1.0 compatible)
ghostscript_version: unknown

### wp-server ###

server_architecture: Linux 5.4.10-x86_64-linode132 x86_64
httpd_software: Apache
php_version: 7.3.18 64bit
php_sapi: fpm-fcgi
max_input_variables: 1000
time_limit: 300
memory_limit: 512M
max_input_time: 600
upload_max_size: 128M
php_post_max_size: 128M
curl_version: 7.69.1 OpenSSL/1.1.1g
suhosin: false
imagick_availability: false
htaccess_extra_rules: false

### wp-database ###

extension: mysqli
server_version: 5.6.47-log
client_version: mysqlnd 5.0.12-dev - 20150407 - $Id: 7cc7cc96e675f6d72e5cf0f267f48e167c2abb23 $

### wp-constants ###

WP_HOME: undefined
WP_SITEURL: undefined
WP_CONTENT_DIR: /home/pmiorgpl/public_html/wp-content
WP_PLUGIN_DIR: /home/pmiorgpl/public_html/wp-content/plugins
WP_MAX_MEMORY_LIMIT: 512M
WP_DEBUG: false
WP_DEBUG_DISPLAY: true
WP_DEBUG_LOG: false
SCRIPT_DEBUG: false
WP_CACHE: false
CONCATENATE_SCRIPTS: undefined
COMPRESS_SCRIPTS: undefined
COMPRESS_CSS: undefined
WP_LOCAL_DEV: undefined
DB_CHARSET: utf8mb4
DB_COLLATE: undefined

### wp-filesystem ###

wordpress: writable
wp-content: writable
uploads: writable
plugins: writable
themes: writable
mu-plugins: writable

### google-site-kit ###

version: 1.8.1
php_version: 7.3.18
wp_version: 5.4.1
reference_url: https://pmi.org.pl
amp_mode: no
site_status: connected-site
user_status: authenticated
active_modules: site-verification, search-console, analytics
required_scopes: 
	openid: ?
	https://www.googleapis.com/auth/userinfo.profile: ?
	https://www.googleapis.com/auth/userinfo.email: ?
	https://www.googleapis.com/auth/siteverification: ?
	https://www.googleapis.com/auth/webmasters: ?
	https://www.googleapis.com/auth/analytics: ?
	https://www.googleapis.com/auth/analytics.readonly: ?
	https://www.googleapis.com/auth/analytics.manage.users: ?
	https://www.googleapis.com/auth/analytics.edit: ?
search_console_property: https://pmi.org.pl/
analytics_account_id: none
analytics_property_id: none
analytics_profile_id: none
analytics_use_snippet: yes

    The page I need help with: [log in to see the link]

Viewing 10 replies - 1 through 10 (of 10 total)

  • @aleksanderadamski thanks for your topic and the detailed info.

    We’ve had reports of this error specifically as well and we’re investigating it in this Github issue.

    We suspect it may be related to the cURL configuration on the server and the request to made to Analytics.

    1) On the screen where you get the error, could you check for and provide any browser console errors?

    2) Could you share your hosting provider and plan so we can attempt to replicate it on our side?

    Thread Starter aleksanderadamski

    (@aleksanderadamski)

    @reneesoffice thanks for replying.

    1.) I had GA code installed via pasting the code manually and it’s working fine. I’ve disabled it for a minute and used site kit – still no success. So here’s the screenshot -https://imgur.com/a/TUWIu6z

    2.) Fastcomet

    Plugin Support James Osborne

    (@jamesosborne)

    @aleksanderadamski Many thanks for the additional information. Can you update to the latest version of the plugin and check whether the same issue persists?

    If you do happen to encounter the same issue some additional troubleshoot steps you can try would be as follows:
    – Contacting your hosting provider and ask them to modify the current cURL version
    – Switch to a different PHP version if your control panel allows it

    As referenced the issue has came up for other users recently, although not specific to Site Kit. Other users of plugins with Guzzle library dependencies have also reported the same issue, as you can find here.

    Can you let me know if any of the above fix this issue in your case?

    Thread Starter aleksanderadamski

    (@aleksanderadamski)

    ok, it’s super weird as now the plugin has completely stopped working in Chrome.
    The lefhand side menu options are visible but clicking any of them results only with blank page. I’ve rolled back to previous version and same thing happens.

    It works in Firefox, tough, but same issue occurs. Maybe some particular mix of plugins, cache and whatnot causes Chrome issue but nevermind.

    Server runs on PHP 7.3. I’d rather not tinker with this one as I don’t want to risk breaking the website. Further pursuing this topic requires more effort than I’m able to give to this sideproject at the moment, so if it’s ok with you guys I’d leave this one as it is, with other solution to GA code.

    Plugin Support James Osborne

    (@jamesosborne)

    @aleksanderadamski Many thanks for the useful insights, totally understood in relation to your preference to not modify any PHP settings or components.

    I’ll keep this support topic open and inform you of any updates as I speak with the team on this. We can also try recreate the same issue using the same server setup and check whether it’s something we can possibly address on the plugin side.

    In the meantime if you have any alternative WordPress site on the same hosting environment let me know if you encounter the same issue.

    Hello Support Team,

    We are also having the same issue. We had GADW plugin installed earlier for Google Analytics and we were planning to move to Sitekit. The search console and PageSpeed have been connected, however google Analytics gives the CURL error that you mentioned. We are also hosted on fastcomet.

    Thanks

    Raminder

    Plugin Support James Osborne

    (@jamesosborne)

    @dbellyrulesdmind If you can open a new support topic we can investigate your specific case. While the problem you’re encountering may be server/hosting related please include your Site Health information, hosting provider and hosting details (cloud, operating system or package). You can use this form to share privately once you’ve created a new support topic.

    @aleksanderadamski While you’ve mentioned your hosting provider can you also share your Site Health information?

    While I suspect there is little we can do from our side, I’ve checked with FastComet and all their hosting plans use CentOS7. Others have reported recent compatibility issues with cURL library versions for other plugins using Guzzle. We can inspect further with your Site Health information.

    Alternatively your hosting provider should be able to assist with changing cURL library version, you can ask them to downgrade versions to test.

    Thread Starter aleksanderadamski

    (@aleksanderadamski)

    Hi @jamesosborne, you can find the sitehealth info in my opening post. Nothing really changed sinced then so it should be up to date.

    Plugin Support James Osborne

    (@jamesosborne)

    @aleksanderadamski Apologies, you did indeed provided your Site Health info. From my side the cURL version we have is 7.19.7, with no issues during Site Kit or Analytics setup using the same hosting provider (although on a shared hosting plan).

    Can you open a support ticket with FastComet asking them to switch your cURL library version to 7.19.7? They’ve confirmed with me that this is the supported version for all their shared hosting plans, and I suspect your current CURL version is causing this error.

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

    While we were not able to recreate the issue, we 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 10 replies - 1 through 10 (of 10 total)
  • The topic ‘“easy handle already used in multi handle” when connecting to GA’ is closed to new replies.