Not able to connect to whatever it’s looking for
-
After step one of signing into google and allowing access to everything, the setup process came back to my dashboard and displayed the following error.
Oops! There was a problem during set up. Please try again.
Unknown Error (code: http_request_failed).
-
@ohgoodiee Sorry to hear you’ve been encountering issues during setup. There are some troubleshooting steps on the plugins website which you can try if not already attempted.
If the issue remains after following those steps please share your Site Health information along with your current hosting provider and we can troubleshoot further.
duplicate
Site health = 100%
No issues found in PHP, Access or Error logs.
No issues found in the firewall logs.
No issues found on/in Cloudflare.
Hosting = self managed VPS with plenty of resources.
Second attempt resulted in the following:
getting site failed
I just went through all of your duplicates, no answer there as to why this issue is caused.
Site: https://verygood.coffee
Hosting provider: vpscheap.net
I should mention that I do not have any browser extensions, etc.
- This reply was modified 4 years, 6 months ago by ohgoodiee.
@ohgoodiee thanks for this info!
1) My apologies, duplicate was referencing that my colleague already replied to the topic.
2) For Site Health, could you provide the information that is on the Info tab as demonstrated in this image?
No worries. I did go through all the post that had the same title, hoping to find a clue to go on. Once we get an idea of what’s going on, I’ll reinstall the plug-in and we can try again.
### wp-core ### version: 5.4.1 site_language: en_US user_language: en_US timezone: America/Phoenix permalink: /index.php/%year%/%monthnum%/%day%/%postname%/ https_status: true user_registration: 683 default_comment_status: open multisite: false user_count: 683 dotorg_communication: true ### wp-paths-sizes ### wordpress_path: /var/www/html/coffee wordpress_size: 40.19 MB (42140815 bytes) uploads_path: /var/www/html/coffee/wp-content/uploads uploads_size: 51.18 MB (53662665 bytes) themes_path: /var/www/html/coffee/wp-content/themes themes_size: 2.10 MB (2202158 bytes) plugins_path: /var/www/html/coffee/wp-content/plugins plugins_size: 35.55 MB (37280630 bytes) database_size: 5.98 MB (6275072 bytes) total_size: 135.00 MB (141561340 bytes) ### wp-active-theme ### name: Twenty Sixteen (twentysixteen) version: 2.1 author: the WordPress team author_website: https://www.ads-software.com/ parent_theme: none theme_features: automatic-feed-links, title-tag, custom-logo, post-thumbnails, menus, html5, post-formats, editor-style, editor-styles, wp-block-styles, responsive-embeds, editor-color-palette, customize-selective-refresh-widgets, custom-background, custom-header, widgets theme_path: /var/www/html/coffee/wp-content/themes/twentysixteen ### wp-themes-inactive (1) ### Twenty Twenty: version: 1.3, author: the WordPress team ### wp-plugins-active (14) ### Add From Server: version: 3.3.3, author: Dion Hulse Advanced Excerpt: version: 4.3.5, author: WPKube Cloudflare: version: 3.4.1, author: John Wineman, Furkan Yilmaz, Junade Ali (Cloudflare Team) Contact Form 7: version: 5.1.9, author: Takayuki Miyoshi GA Google Analytics: version: 20200325, author: Jeff Starr Noptin - WordPress Newsletter Plugin: version: 1.2.9, author: Noptin Newsletter Optimize Database after Deleting Revisions: version: 4.9.1, author: CAGE Web Design | Rolf van Gelder, Eindhoven, The Netherlands Post SMTP: version: 2.0.12, author: Yehuda Hassine Shared Counts: version: 1.3.0, author: Bill Erickson & Jared Atchison Simple XML Sitemap Generator: version: 1.9.0, author: Eric-Oliver M?chler Subscribe to Comments Reloaded: version: 200422, author: WPKube User Registration: version: 1.8.3, author: WPEverest WP Crontrol: version: 1.8.3, author: John Blackbourn & crontributors WP Fastest Cache: version: 0.9.0.6, author: Emre Vona ### wp-media ### image_editor: WP_Image_Editor_Imagick imagick_module_version: 1691 imagemagick_version: ImageMagick 6.9.11-11 Q16 x86_64 2020-05-11 https://imagemagick.org imagick_limits: imagick::RESOURCETYPE_AREA: 8 GB imagick::RESOURCETYPE_DISK: 9.2233720368548E+18 imagick::RESOURCETYPE_FILE: 768 imagick::RESOURCETYPE_MAP: 8 GB imagick::RESOURCETYPE_MEMORY: 4 GB imagick::RESOURCETYPE_THREAD: 4 gd_version: 2.3.0 ghostscript_version: not available ### wp-server ### server_architecture: Linux 2.6.32-042stab133.2 x86_64 httpd_software: Apache php_version: 7.3.18 64bit php_sapi: apache2handler max_input_variables: 1000 time_limit: 14400 memory_limit: 256M max_input_time: 60 upload_max_size: 2M php_post_max_size: 8M curl_version: 7.19.7 NSS/3.44 suhosin: false imagick_availability: true htaccess_extra_rules: true ### wp-database ### extension: mysqli server_version: 5.6.48 client_version: mysqlnd 5.0.12-dev - 20150407 - $Id: 7cc7cc96e675f6d72e5cf0f267f48e167c2abb23 $ ### wp-constants ### WP_HOME: undefined WP_SITEURL: undefined WP_CONTENT_DIR: /var/www/html/coffee/wp-content WP_PLUGIN_DIR: /var/www/html/coffee/wp-content/plugins WP_MAX_MEMORY_LIMIT: 256M 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
- This reply was modified 4 years, 6 months ago by ohgoodiee.
@ohgoodiee thanks again. There is actually Site Kit specific details available in the Site Health when the plugin is activated. If possible could you:
1) Update to version 1.8.1 and run through the setup process.
2) If it fails, gather the Site Health information under ### google-site-kit ### under the Info tab.
We’ve been investigating similar reports in this Github issue. The situations have varied, but more consistently it had to do with a block/restriction at the host level. We’ll see if we can replicate the same in a similar environment as yours.
Step 1: Deactivate: GA Google Analytics
Step 2: Install Site Kit and run setup
The errors returned from running setup
Oops! There was a problem during set up. Please try again.
Unknown Error (code: http_request_failed).Version 1.8.1
PHP Version 7.3.18
WordPress Version 5.4.1
Reference Site URL https://verygood.coffee
AMP Mode No
Site Status Not connected
User Status Not authenticated
Active Modules Site Verification, Search Console
Required scopesopenid: ?
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: ?Search Console property None
Let me know what you think about this. I am curious about the “Search Console” as I do have analytics and search console is activated through it.
- This reply was modified 4 years, 6 months ago by ohgoodiee.
Firewall issue. Solved.
dig googleapis.com = 172.217.11.164 (172.217.0.0/16)
Punch hole in firewall for 172.217.0.0/16
Setup completed without issue.
Question: Do I have to leave the hole in the firewall after the setup has completed or can I close it?
@ohgoodiee Thanks for the update, nice troubleshooting.
In relation to your Firewall question is this a hosting based Firewall or local Firewall software? The plugin needs to be able to connect with
https://sitekit.withgoogle.com
so you may need to whitelist that service.If you can share your Firewall solution we’d be happy to check from our side.
It’s complicated. Both on server and cloud based. They work hand-in-hand to keep the crackheads and script kiddies out.
I use CSF on the server and Cloudflare.
About 5 minutes ago, I logged into the site to start a new post to discover that there was a new problem. (backup for a sec. after setup, dashboard, etc all worked, lots of easy communication with all google services).
The new problem now is cURL 7 errors, freezing up the admin area (not able to go to anywhere in the admin area). I deactivated the plug-in, waited while writing this, reactivated the plug-in 5 sec ago and now all is back to normal. Not sure what that is about.
I’ve dealt with cURL 7 errors before so I’ll keep digging around to see what I can find.
btw. dig sitekit.withgoogle.com = 172.217.4.177 which falls into 172.217.0.0/16, so that should not be a problem.
@ohgoodiee thanks for the follow up. I’m curious if whitelisting your IP address would help in this case?
Depending on the setup, (sandbox, test server, etc) you have to have a loopback or your own ip has to be able to communicate back to the server for WP Cron to work.
I use a set scheduled cron from the server to keep the traffic down from WPs’ cron firing every time there’s a visitor.
In this case, for giggles, I disabled the server cron and enabled WPs’ cron to see if it would make a difference (maybe something in the way WP cron spawns off processes) but it didn’t make any difference.
As noted above “dotorg_communication: true” is WP’s way of letting you know that it can loopback.
For now, I haven’t had anymore cURL errors. I’ve been pretty hard on the server for the last few months, so decided to give it a good restart.
Will let you if anything else pops up.
@ohgoodiee really appreciate any updates as we’d like to make sure Site Kit can work in various environments. One tip a hosting provider gave us when there was issues with blocks at the server-level was opening port: 443 and port: 80 on their platform. I’m not sure if this would be helpful in your environment. Thanks again for the all the feedback you’ve provided thus far @ohgoodiee !
- The topic ‘Not able to connect to whatever it’s looking for’ is closed to new replies.