Skip to content

Update troubleshooting section for Google Pagespeed #476

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.

Sign up for GitHub

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

Merged
poespas merged 1 commit into from
May 6, 2026
+1 −1
Merged

Update troubleshooting section for Google Pagespeed #476

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion ...hypernode-platform/nginx/basic-authentication-on-hypernode-development-plans.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -132,5 +132,5 @@ map $http_user_agent $development_exceptions {

## Troubleshooting

- Google Pagespeed analysis uses the Google bot user agent and can therefore not be used on development nodes.
- To allow Google Pagespeed analysis in development hypernodes you can whitelist the following IPs https://www.gstatic.com/ipranges/goog.json. PSI uses different user agents than Google bot and will be able to perform analysis on your frontend without allowing crawling.
- In some cases, particularly if you have not yet enabled [Hypernode Managed Vhosts](../../hypernode-platform/nginx/hypernode-managed-vhosts.md), it’s possible the Basic Authentication blocks the Let’s Encrypt validation server. If you wish to make use of Let’s Encrypt on your development Hypernode, you should add the ‘letsencrypt’ user agent to the whitelist file.
Loading