Pa11y-CI cannot be run on https with self-signed certificate about pa11y-ci HOT 6 CLOSED

@drnickyoung If that's a copy from your configuration, check the spelling of the "defaults" property.

from pa11y-ci.

Did you set ignoreHTTPSErrors as part of the chromeLaunchConfig? This works for me:

{
    "defaults": {
        "chromeLaunchConfig": {
            "ignoreHTTPSErrors": true
        }
    }
}

from pa11y-ci.

I've tried - but in the ends I just made a new self signed certificate and added it on "Trusted Root Authorities" :)

from pa11y-ci.

Was this ever resolved, using the config scripts that is? I am facing the same error using:

{
    "default": {
        "chromeLaunchConfig": {
            "ignoreHTTPSErrors": true
        },
        "standard": "WCAG2AA",
        "timeout": 5000,
        "wait": 2000,
        "page": {
            "viewport": {
                "width": 320,
                "height": 480
            }
        }
    },
    "urls": [
        "https://xyz/",
        "https://xyz/about"
    ]
}

and getting this back:

Errors in https://xyz/:

 • Error: net::ERR_CERT_AUTHORITY_INVALID at https://xyz/

I have used ignoreHTTPSErrors in pa11y-dashboard config and it works fine at ignoring the certificate issue. Just Pa11y-ci doesn't seem to use it in the config, ot I am doing something wrong.

from pa11y-ci.

@aarongoldenthal going by the main readme "default" is correct. Changing it "defaults" creates the error:

Errors in https://xyz

 • Error: page.on is not a function

Now on investigating further I see "page" is and issue, presumably it is not supported or there is some other issue. Anyway together with your suggestion I now have a working set-up:

{
    "defaults": {
        "chromeLaunchConfig": {
            "ignoreHTTPSErrors": true
        },
        "standard": "WCAG2AA",
        "timeout": 10000,
        "wait": 5000
    },
    "urls": [
        "https://xyz",
        "https://xyz/about"
    ]
}

Would suggest someone reviews the main readme and updates it, default to defaults (or point out what I have got wrong!).

from pa11y-ci.

Thanks for creating this issue. It looks like this is now fixed, feel free to reopen the issue if not.

from pa11y-ci.