We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Original report: https://talk.plesk.com/threads/extension-google-pagespeed-insights-issue.345160/
using this extension in the domain page we got the link:
Download optimized image, JavaScript, and CSS resources for this page.
which points to: https://developers.google.com/speed/pagespeed/insights/optimizeContents?url=http://DOMAIN.TLD&strategy=desktop
but clicking it we got error from Google API:
The referrer https://OURPLESKSERVERNAME:8443/modules/pagespeed-insights/index.php/index/result?dom_id=5&site_id=5 does not match the referrer restrictions configured on your API key. Please use the API Console to update your key restrictions.
I swapped urls for privacy reasons.
The text was updated successfully, but these errors were encountered:
This bug was fixed in the latest release (2.0.0): https://ext.plesk.com/packages/3d2639e6-64a9-43fe-a990-c873b6b3ec66-pagespeed-insights
Sorry, something went wrong.
No branches or pull requests
Original report: https://talk.plesk.com/threads/extension-google-pagespeed-insights-issue.345160/
using this extension in the domain page we got the link:
Download optimized image, JavaScript, and CSS resources for this page.
which points to: https://developers.google.com/speed/pagespeed/insights/optimizeContents?url=http://DOMAIN.TLD&strategy=desktop
but clicking it we got error from Google API:
The referrer https://OURPLESKSERVERNAME:8443/modules/pagespeed-insights/index.php/index/result?dom_id=5&site_id=5 does not match the referrer restrictions configured on your API key. Please use the API Console to update your key restrictions.
I swapped urls for privacy reasons.
The text was updated successfully, but these errors were encountered: