Lighthouse CI in github action fails to run with error: ERR_CONNECTION_REFUSED

Describe the bug I run Lighthouse CI in my github action and it fails with an error. I used the same configuration in my local environment and it worked fine.

To Reproduce Steps to reproduce the behavior:

1. Use the following Lighthouse configuration file:

module.exports = {
	ci: {
		collect: {
			numberOfRuns: 3,
			startServerCommand: 'yarn run start',
			url: ['http://localhost'],
		},
		assert: {
			preset: 'lighthouse:recommended',
		},
		upload: {
			target: 'temporary-public-storage',
		},
	},
};

1. Insert a Lighthouse package.json script to run: "lighthouse": "lhci autorun"

2. Insert a Lighthouse step in Github action file:

name: Snippet

on:
  pull_request:
    branches: [ main ]

jobs:
  test_pull_request:
    name: Testing & Checking the code
    runs-on: ubuntu-latest

    steps:
      - name: Checkout
        uses: actions/checkout@v2
      
      - name: Setup Node.js
        uses: actions/setup-node@v2
        with:
          node-version: 14

      - name: Installing dependencies
        run: yarn install --immutable --immutable-cache --check-cache

      - name: Check build command
        run: yarn run build

      - name: Lighthouse Benchmark
        run: yarn run lighthouse

Run it in GH and watch it failing (at-least for me…)

Expected behavior Run without any issue

Logs/Screenshots

Error: Lighthouse failed with exit code 1
    at ChildProcess.<anonymous> (/home/runner/work/landing-page/landing-page/node_modules/@lhci/cli/src/collect/node-runner.js:120:21)
    at ChildProcess.emit (events.js:400:28)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:282:12)

Thu, 03 Mar 2022 21:34:47 GMT LH:ChromeLauncher Killing Chrome instance 2161
Runtime error encountered: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Details: net::ERR_CONNECTION_REFUSED)
error Command failed with exit code 1.

Environment (please complete the following information):

• OS: Ubuntu
• Browser: Chrome
• Version: Unknown

Additional context Add any other context about the problem here.

[tal-rofe]

@AshNaz87

So the problem occurred because the server ran on port “80” in the Github Action machine. Apparently port “80” is protected to root permissions, so either run “sudo yarn run start” or open the server with other port. Something like “8080”. I took the second option.

[tal-rofe]

@AshNaz87

I do have a custom server. That’s why I needed it. Anyway- this works fine. But yet, I have the issue only in the github action been running.

Really strange because I just followed known guides. Nothing special in my configuration