Title: string(11) “Bad Request” Last modified: February 12, 2024 --- # string(11) “Bad Request” * Resolved [gchris2](https://wordpress.org/support/users/gchris2/) * (@gchris2) * [2 years, 4 months ago](https://wordpress.org/support/topic/string11-bad-request/) * When I try to configure Google Site Kit, I get the following error message after completing the steps to log in. I receive the error message ‘string(11) “Bad Request”‘. I don’t understand why this is happening. It’s a new WordPress installation, and I’ve gone through this process about 15 times with other websites. The URL looks like this when I get the error message: * [https://fakeurl.uu/wp/wp-admin/index.php?oauth2callback=1&authuser=0&code=4%2F0AeaYSHAMiKyL7slTEPTivAtY1866gNOyUQhkmNMvm67vLiIIchHPmJONlfUCGFRr-_sLZA&prompt=consent](https://xxxxxx.uu/wp/wp-admin/index.php?oauth2callback=1&authuser=0&code=4%2F0AeaYSHAMiKyL7slTEPTivAtY1866gNOyUQhkmNMvm67vLiIIchHPmJONlfUCGFRr-_sLZA&prompt=consent) * I’ve tried both Chrome and Firefox, and even incognito mode. Resetting Site Kit also doesn’t help. * ```wp-block-code ` wp-core version: 6.4.3 site_language: nl_NL user_language: nl_NL timezone: Europe/Amsterdam permalink: /%postname%/ https_status: true multisite: false user_registration: 0 blog_public: 1 default_comment_status: closed environment_type: production user_count: 3 dotorg_communication: true wp-paths-sizes wordpress_path: /data/sites/web/xxx/checkout/master/98e6719f8a15063c2595fe0a8d7cf9cac9e9b5c3/web/wp wordpress_size: 54,03 MB (56657267 bytes) uploads_path: /data/sites/web/xxx/checkout/master/98e6719f8a15063c2595fe0a8d7cf9cac9e9b5c3/web/app/uploads uploads_size: 991,61 MB (1039776346 bytes) themes_path: /data/sites/web/xxx/checkout/master/98e6719f8a15063c2595fe0a8d7cf9cac9e9b5c3/web/app/themes themes_size: 172,04 MB (180399946 bytes) plugins_path: /data/sites/web/xxx/checkout/master/98e6719f8a15063c2595fe0a8d7cf9cac9e9b5c3/web/app/plugins plugins_size: 85,46 MB (89614232 bytes) database_size: 6,11 MB (6406144 bytes) total_size: 1,28 GB (1372853935 bytes) wp-dropins (1) advanced-cache.php: true wp-active-theme name: xxx version: 10.0.0-dev author: xx author_website: https://xx.xx parent_theme: none theme_features: sage, widgets-block-editor, soil, menus, editor-color-palette, editor-gradient-presets, editor-font-sizes, custom-units, custom-line-height, custom-spacing, disable-custom-colors, disable-custom-gradients, disable-custom-font-sizes, title-tag, post-thumbnails, align-wide, responsive-embeds, html5, customize-selective-refresh-widgets, widgets theme_path: /data/sites/web/xx/checkout/master/98e6719f8a15063c2595fe0a8d7cf9cac9e9b5c3/web/app/themes/xx wp-mu-plugins (3) Bedrock Autoloader: version: 1.0.3, author: Roots Disallow Indexing: version: 1.0.0, author: Roots Register Theme Directory: version: 1.0.0, author: Roots wp-plugins-active (11) Advanced Custom Fields PRO: version: 6.2.5, author: WP Engine (latest version: 6.2.6.1) Gravity Forms: version: 2.8.3, author: Gravity Forms Gravity Forms reCAPTCHA Add-On: version: 1.4.0, author: Gravity Forms ManageWP - Worker: version: 4.9.19, author: GoDaddy Redirection: version: 5.4.2, author: John Godley Site Kit by Google: version: 1.119.0, author: Google SVG Support: version: 2.5.5, author: Benbodhi WP-PageNavi: version: 2.94.1, author: Lester 'GaMerZ' Chan WP Migrate Lite: version: 2.6.9, author: WP Engine (latest version: 2.6.10) Yoast Duplicate Post: version: 4.5, author: Enrico Battocchi & Team Yoast Yoast SEO: version: 21.9.1, author: Team Yoast (latest version: 22.0) wp-plugins-inactive (1) WP Rocket: version: 3.15.9, author: WP Media wp-media image_editor: WP_Image_Editor_Imagick imagick_module_version: 1691 imagemagick_version: ImageMagick 6.9.11-60 Q16 x86_64 2021-01-25 https://imagemagick.org imagick_version: 3.7.0 file_uploads: 1 post_max_size: 256M upload_max_filesize: 256M max_effective_size: 256 MB max_file_uploads: 20 imagick_limits: imagick::RESOURCETYPE_AREA: 122 MB imagick::RESOURCETYPE_DISK: 1073741824 imagick::RESOURCETYPE_FILE: 768 imagick::RESOURCETYPE_MAP: 512 MB imagick::RESOURCETYPE_MEMORY: 256 MB imagick::RESOURCETYPE_THREAD: 1 imagick::RESOURCETYPE_TIME: 9.2233720368548E+18 imagemagick_file_formats: 3FR, 3G2, 3GP, AAI, AI, APNG, ART, ARW, AVI, AVIF, AVS, BGR, BGRA, BGRO, BIE, BMP, BMP2, BMP3, BRF, CAL, CALS, CANVAS, CAPTION, CIN, CIP, CLIP, CMYK, CMYKA, CR2, CR3, CRW, CUR, CUT, DATA, DCM, DCR, DCX, DDS, DFONT, DJVU, DNG, DOT, DPX, DXT1, DXT5, EPDF, EPI, EPS, EPS2, EPS3, EPSF, EPSI, EPT, EPT2, EPT3, ERF, EXR, FAX, FILE, FITS, FRACTAL, FTP, FTS, G3, G4, GIF, GIF87, GRADIENT, GRAY, GRAYA, GROUP4, GV, H, HALD, HDR, HEIC, HISTOGRAM, HRZ, HTM, HTML, HTTP, HTTPS, ICB, ICO, ICON, IIQ, INFO, INLINE, IPL, ISOBRL, ISOBRL6, J2C, J2K, JBG, JBIG, JNG, JNX, JP2, JPC, JPE, JPEG, JPG, JPM, JPS, JPT, JSON, K25, KDC, LABEL, M2V, M4V, MAC, MAGICK, MAP, MASK, MAT, MATTE, MEF, MIFF, MKV, MNG, MONO, MOV, MP4, MPC, MPG, MRW, MSL, MSVG, MTV, MVG, NEF, NRW, NULL, ORF, OTB, OTF, PAL, PALM, PAM, PANGO, PATTERN, PBM, PCD, PCDS, PCL, PCT, PCX, PDB, PDF, PDFA, PEF, PES, PFA, PFB, PFM, PGM, PGX, PICON, PICT, PIX, PJPEG, PLASMA, PNG, PNG00, PNG24, PNG32, PNG48, PNG64, PNG8, PNM, POCKETMOD, PPM, PREVIEW, PS, PS2, PS3, PSB, PSD, PTIF, PWP, RADIAL-GRADIENT, RAF, RAS, RAW, RGB, RGBA, RGBO, RGF, RLA, RLE, RMF, RW2, SCR, SCT, SFW, SGI, SHTML, SIX, SIXEL, SPARSE-COLOR, SR2, SRF, STEGANO, SUN, SVG, SVGZ, TEXT, TGA, THUMBNAIL, TIFF, TIFF64, TILE, TIM, TTC, TTF, TXT, UBRL, UBRL6, UIL, UYVY, VDA, VICAR, VID, VIDEO, VIFF, VIPS, VST, WBMP, WEBM, WEBP, WMF, WMV, WMZ, WPG, X, X3F, XBM, XC, XCF, XPM, XPS, XV, XWD, YCbCr, YCbCrA, YUV gd_version: bundled (2.1.0 compatible) gd_formats: GIF, JPEG, PNG, WebP, BMP, XPM ghostscript_version: 9.53.3 wp-server server_architecture: Linux 6.1.38-hcl x86_64 httpd_software: Apache php_version: 8.0.30 64bit php_sapi: fpm-fcgi max_input_variables: 20000 time_limit: 300 memory_limit: 256M max_input_time: 60 upload_max_filesize: 256M php_post_max_size: 256M curl_version: 7.74.0 OpenSSL/1.1.1n suhosin: false imagick_availability: true pretty_permalinks: true current: 2024-02-12T17:34:16+00:00 utc-time: Monday, 12-Feb-24 17:34:16 UTC server-time: 2024-02-12T18:34:15+01:00 wp-database extension: mysqli server_version: 5.7.40-43-log client_version: mysqlnd 8.0.30 max_allowed_packet: 67108864 max_connections: 150 wp-constants WP_HOME: https://xxx.xx WP_SITEURL: https://xxx.xx/wp WP_CONTENT_DIR: /data/sites/web/xx/checkout/master/98e6719f8a15063c2595fe0a8d7cf9cac9e9b5c3/web/app WP_PLUGIN_DIR: /data/sites/web/xx/checkout/master/98e6719f8a15063c2595fe0a8d7cf9cac9e9b5c3/web/app/plugins WP_MEMORY_LIMIT: 40M WP_MAX_MEMORY_LIMIT: 256M WP_DEBUG: false WP_DEBUG_DISPLAY: false WP_DEBUG_LOG: /path/to/debug.log SCRIPT_DEBUG: false WP_CACHE: false CONCATENATE_SCRIPTS: undefined COMPRESS_SCRIPTS: undefined COMPRESS_CSS: undefined WP_ENVIRONMENT_TYPE: Ongedefinieerd WP_DEVELOPMENT_MODE: 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.119.0 php_version: 8.0.30 wp_version: 6.4.3 reference_url: https://xx.xx amp_mode: no site_status: connected-site user_status: not authenticated verification_status: not-verified connected_user_count: none active_modules: site-verification, search-console, analytics, analytics-4, pagespeed-insights recoverable_modules: none 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.readonly: ⭕ https://www.googleapis.com/auth/tagmanager.readonly: ⭕ capabilities: googlesitekit_authenticate: ✅ googlesitekit_setup: ✅ googlesitekit_view_posts_insights: ⭕ googlesitekit_view_dashboard: ⭕ googlesitekit_manage_options: ⭕ googlesitekit_update_plugins: ⭕ googlesitekit_view_splash: ✅ googlesitekit_view_authenticated_dashboard: ⭕ googlesitekit_view_wp_dashboard_widget: ⭕ googlesitekit_view_admin_bar_menu: ⭕ googlesitekit_view_shared_dashboard: ⭕ googlesitekit_read_shared_module_data::["search-console"]: ⭕ googlesitekit_read_shared_module_data::["pagespeed-insights"]: ⭕ googlesitekit_manage_module_sharing_options::["search-console"]: ⭕ googlesitekit_manage_module_sharing_options::["pagespeed-insights"]: ⭕ googlesitekit_delegate_module_sharing_management::["search-console"]: ⭕ googlesitekit_delegate_module_sharing_management::["pagespeed-insights"]: ⭕ enabled_features: gm3Components: ⭕ search-console_shared_roles: none search-console_management: owner pagespeed-insights_shared_roles: none pagespeed-insights_management: all_admins search_console_property: none analytics_account_id: none analytics_property_id: none analytics_profile_id: none analytics_use_snippet: yes analytics_4_property_id: none analytics_4_web_data_stream_id: none analytics_4_measurement_id: none analytics_4_use_snippet: yes analytics_4_available_custom_dimensions: none ``` Viewing 9 replies - 31 through 39 (of 39 total) [←](https://wordpress.org/support/topic/string11-bad-request/page/2/?output_format=md) [1](https://wordpress.org/support/topic/string11-bad-request/?output_format=md) [2](https://wordpress.org/support/topic/string11-bad-request/page/2/?output_format=md) 3 * Thread Starter [gchris2](https://wordpress.org/support/users/gchris2/) * (@gchris2) * [2 years, 2 months ago](https://wordpress.org/support/topic/string11-bad-request/page/3/#post-17650103) * Unfortunately, the same error message persists: string(11) ‘Bad Request’. I do notice that the number of services to be linked in a later screen is fewer when I select that option. Unfortunately, linking doesn’t work this way either. * Plugin Support [James Osborne](https://wordpress.org/support/users/jamesosborne/) * (@jamesosborne) * [2 years, 2 months ago](https://wordpress.org/support/topic/string11-bad-request/page/3/#post-17677812) * Thanks for the update [@gchris2](https://wordpress.org/support/users/gchris2/). I’ll check your case with the team tomorrow before reporting back to you here. * Plugin Support [James Osborne](https://wordpress.org/support/users/jamesosborne/) * (@jamesosborne) * [2 years, 2 months ago](https://wordpress.org/support/topic/string11-bad-request/page/3/#post-17680602) * Just to keep you updated on this [@gchris2](https://wordpress.org/support/users/gchris2/), I’m awaiting a discussion with the team on this. It may be tomorrow before I have an update. * Note that as what you’re facing may possibly be hosting related, in the meantime, if feasible, please install a WordPress site (without a bedrock setup) on the same hosting platform, or within a temporary subdirectory of your existing site. From there you can attempt Site Kit setup. * Regardless of whether you are able to perform the above, I will let you know once I’ve discussed your case with the team. Thank you, and appreciate your patience! * Plugin Support [James Osborne](https://wordpress.org/support/users/jamesosborne/) * (@jamesosborne) * [2 years, 1 month ago](https://wordpress.org/support/topic/string11-bad-request/page/3/#post-17688063) * [@gchris2](https://wordpress.org/support/users/gchris2/) From discussing this with the team, another plugin may be trying to use the same URL structure for the OAuth callback as Site Kit. Another possibility is that this is web server related, given the checks you already performed with the Health Check & Troubleshooting plugin. With that, can you let me know if you were able to set up another WordPress site within a subfolder of your current site, and let me know if you’re able to complete Site Kit set up from that site? * If not, please share your debug.log file. You can share this using the [same form previously used](https://docs.google.com/forms/d/1lhjns2K7c0Ny7ME4gxTcsnYtNUtcMr8BvFpPQi23Y1E/), adding a link to your debug log file. * Thread Starter [gchris2](https://wordpress.org/support/users/gchris2/) * (@gchris2) * [1 year, 11 months ago](https://wordpress.org/support/topic/string11-bad-request/page/3/#post-17841631) * Hi James, * I came to say that I give up. We’ve tried many things, but I have the feeling it’s not working. I’m not setting up another WordPress site. We use the same stack for 30 websites, and it works on other domains, but not here. Unfortunately, it’s now giving a blank page for two more websites, but that’s a recent issue and probably a different kind of error. I’m not blaming you, but it’s very frustrating that it isn’t working as it should, and I’m not sure it’s our fault. * Plugin Support [James Osborne](https://wordpress.org/support/users/jamesosborne/) * (@jamesosborne) * [1 year, 11 months ago](https://wordpress.org/support/topic/string11-bad-request/page/3/#post-17841749) * Completely understand [@gchris2](https://wordpress.org/support/users/gchris2/). I certainly can request another reset of your site records if you wish, but there is no guarantee that your site will connect. I can see from checking your site now that you’re still using the `/wp` path and a standard wp-login and wp-admin path. If the same occurs, I can escalate this once more if you wish to share your debug.log file. * Agreed also that it’s frustrating that this will not work on one particular site, in particular on the same hosting platform. This does lead me to believe the cause may be a multi party conflict, between the records for this domain on the Site Kit service, and something within your plugin or host environment specific to this site. * Do let me know if you wish for me to request another reset. Note that such requests take a few days. * Plugin Support [James Osborne](https://wordpress.org/support/users/jamesosborne/) * (@jamesosborne) * [1 year, 11 months ago](https://wordpress.org/support/topic/string11-bad-request/page/3/#post-17864303) * I’m just following up with you to check whether the issue remains? If so please let me know if you wish for me to perform another check of your site records. Thank you! * Thread Starter [gchris2](https://wordpress.org/support/users/gchris2/) * (@gchris2) * [1 year, 11 months ago](https://wordpress.org/support/topic/string11-bad-request/page/3/#post-17865185) * Hi James, * Thank you for your response. No further action is needed; for now, I have made the connection without the plugin. It’s not ideal, but it took so much time that I don’t know what else we could try at this point. It’s a shame we couldn’t solve it, but that’s how it is for now. Thank you for your time and effort nonetheless. * Plugin Support [James Osborne](https://wordpress.org/support/users/jamesosborne/) * (@jamesosborne) * [1 year, 11 months ago](https://wordpress.org/support/topic/string11-bad-request/page/3/#post-17865681) * Sorry to hear Site Kit set up didn’t complete as expected, but glad you were able to connect your site with Search Console and/or Analytics independently. Appreciate you’re willingness to perform various troubleshooting steps, while sharing updates along the way. Best of luck. Viewing 9 replies - 31 through 39 (of 39 total) [←](https://wordpress.org/support/topic/string11-bad-request/page/2/?output_format=md) [1](https://wordpress.org/support/topic/string11-bad-request/?output_format=md) [2](https://wordpress.org/support/topic/string11-bad-request/page/2/?output_format=md) 3 The topic ‘string(11) “Bad Request”’ is closed to new replies. * ![](https://ps.w.org/google-site-kit/assets/icon-256x256.png?rev=3141863) * [Site Kit by Google - Analytics, Search Console, AdSense, Speed](https://wordpress.org/plugins/google-site-kit/) * [Frequently Asked Questions](https://wordpress.org/plugins/google-site-kit/#faq) * [Support Threads](https://wordpress.org/support/plugin/google-site-kit/) * [Active Topics](https://wordpress.org/support/plugin/google-site-kit/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/google-site-kit/unresolved/) * [Reviews](https://wordpress.org/support/plugin/google-site-kit/reviews/) * 39 replies * 2 participants * Last reply from: [James Osborne](https://wordpress.org/support/users/jamesosborne/) * Last activity: [1 year, 11 months ago](https://wordpress.org/support/topic/string11-bad-request/page/3/#post-17865681) * Status: resolved