-
Notifications
You must be signed in to change notification settings - Fork 291
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Page Speed Insights - Data Error on Subdomains #68
Comments
@jamesozzie |
Thanks @ivankristianto. Thanks for the update. It's working fine when I reset, I never made any changes or set restrictions on that project in GCP. I copied and pasted the API directly. But if it arises again I will report. |
@ivankristianto. I have a video here where you can see the issue again, not just on a subdomain. Would there be something else causing this? Even after resetting Site Kit and repeating the process using incognito mode: |
@jamesozzie can you check for excess spaces in the api key? |
@ivankristianto While there appears to be an additional space in the generated API key this is not the cause of the problem, as the copied API key does not include this space (copied directly via the copy button or copied via selecting the text, copying & pasting). This is not the root cause of this issue. |
@jamesozzie |
@ivankristianto There are no restrictions set, see below: |
Let's re-test this after #81 is fixed. |
Describe the bug
Tested on site hosted within subdomain and subpath (demo.***.io/sample).
Newly setup site, Site Kit just added, API key is correct and no restrictions, copied as per setup process. PageSpeed services/module is appearing as "Connected" under 'connected services' tab in Site Kit Admin.
To Reproduce
Install Site Kit on subdomain & subpath.
pagespeed-insights::site-pagespeed-desktop::last-28-days::d41d8cd98f00b204e9800998ecf8427e: {errors: {400: ["Bad Request"]}, error_data: {400: {status: 500, reason: "keyInvalid"}}}
error_data: {400: {status: 500, reason: "keyInvalid"}}
errors: {400: ["Bad Request"]}
pagespeed-insights::site-pagespeed-mobile::last-28-days::d41d8cd98f00b204e9800998ecf8427e: {errors: {400: ["Bad Request"]}, error_data: {400: {status: 500, reason: "keyInvalid"}}}
error_data: {400: {status: 500, reason: "keyInvalid"}}
errors: {400: ["Bad Request"]}
Response:
{"pagespeed-insights::site-pagespeed-mobile::last-28-days::d41d8cd98f00b204e9800998ecf8427e":{"errors":{"400":["Bad Request"]},"error_data":{"400":{"status":500,"reason":"keyInvalid"}}},"pagespeed-insights::site-pagespeed-desktop::last-28-days::d41d8cd98f00b204e9800998ecf8427e":{"errors":{"400":["Bad Request"]},"error_data":{"400":{"status":500,"reason":"keyInvalid"}}}}
System Information (please complete the following information):
WordPress Version: 5.2.2
Web Host OS: Linux
Site Kit Plugin version: 1.0.0-beta.1
Browser: Chrome
Operating System: Macos 10.13.6
PHP Version: 7.2
The text was updated successfully, but these errors were encountered: