You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm setting up a new Private Instance using the Dockerfile-php, Dockerfile-nginx, and Dockerfile-wptagent files in the public repository. I have settings.ini, keys.ini, and ec2_locations.ini from an older 21.07 Private Instance configured and working for site performance tests.
The new "Start a Lighthouse test" mechanism, however, does not work. The locations do not populate if a lighthouse.ini file is missing. Nginx points the user to lighthouse_test.php, which appears to be looking for this lighthouse.ini file in /www/settings, but it isn't documented anywhere and I can't find a sample anywhere in the repo. There's no mention of it in documentation, the forums, or in github either.
I tried creating a symlink for lighthouse.ini to point to the ec2_locations.ini, but it only shows the top-level groups in the list. If I try to select one which has a connected agent and run a test, I immediately get an "invalid location" error and the test does not run.
For what it's worth, Lighthouse runs fine if I check the Site Performance | Advanced Configuration | Chromium | Run Lighthouse Audit box in a site performance test.
Steps to reproduce
Set up Private Instances using only the current Dockerfiles in the public repository
Configure the site performance files
Attempt to run a Lighthouse test or Visual Comparison test, Core Web Vitals does not show as an option.
Expected result
Lighthouse test should run and report back its findings.
Visual Comparison test should run and report back its findings.
Core Web Vitals should show up in the test list.
Actual result
Error:
Related issues?
Similarly, the Visual Comparison does not populate with a "Test Configuration" dropdown like you see on the main webpagetest.org testing site, and "Core Web Vitals" does not show at all because we're also missing profiles.ini and profiles_webvitals.ini files.
The text was updated successfully, but these errors were encountered:
Description
I'm setting up a new Private Instance using the Dockerfile-php, Dockerfile-nginx, and Dockerfile-wptagent files in the public repository. I have
settings.ini
,keys.ini
, andec2_locations.ini
from an older 21.07 Private Instance configured and working for site performance tests.The new "Start a Lighthouse test" mechanism, however, does not work. The locations do not populate if a
lighthouse.ini
file is missing. Nginx points the user tolighthouse_test.php
, which appears to be looking for thislighthouse.ini
file in/www/settings
, but it isn't documented anywhere and I can't find a sample anywhere in the repo. There's no mention of it in documentation, the forums, or in github either.I tried creating a symlink for
lighthouse.ini
to point to theec2_locations.ini
, but it only shows the top-level groups in the list. If I try to select one which has a connected agent and run a test, I immediately get an "invalid location" error and the test does not run.For what it's worth, Lighthouse runs fine if I check the
Site Performance | Advanced Configuration | Chromium | Run Lighthouse Audit
box in a site performance test.Steps to reproduce
Set up Private Instances using only the current Dockerfiles in the public repository
Configure the site performance files
Attempt to run a Lighthouse test or Visual Comparison test, Core Web Vitals does not show as an option.
Expected result
Lighthouse test should run and report back its findings.
Visual Comparison test should run and report back its findings.
Core Web Vitals should show up in the test list.
Actual result
Error:

Related issues?
Similarly, the Visual Comparison does not populate with a "Test Configuration" dropdown like you see on the main webpagetest.org testing site, and "Core Web Vitals" does not show at all because we're also missing
profiles.ini
andprofiles_webvitals.ini
files.The text was updated successfully, but these errors were encountered: