UserAgent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:61.0) Gecko/20100101 Firefox/61.0

Steps to reproduce the problem:
const CDP = require('chrome-remote-interface');

async function main() {
    const client = await CDP();
    const {Page, Network, Security} = client;

    Security.certificateError(({eventId}) => {
        console.log(`Security.certificateError: ${eventId}`);
        Security.handleCertificateError({eventId, action: 'continue'});
    });

    Network.requestIntercepted(({interceptionId}) => {
        console.log(`Network.requestIntercepted: ${interceptionId}`);
        Network.continueInterceptedRequest({interceptionId});
    });

    await Page.enable();
    await Network.enable();
    await Security.enable();
    await Security.setOverrideCertificateErrors({override: true});
    await Network.setRequestInterception({
        patterns: [{
            urlPattern: '*',
            interceptionStage: 'HeadersReceived'
        }]
    });

    await Page.navigate({url: 'https://self-signed.badssl.com/'});
    await Page.loadEventFired();
    console.log('Done');
    await client.close();
}

main();

What is the expected behavior?
Callback for request interception should be called with interception id.

What went wrong?
Request stays pending, callback never called and no errors were reported.

Did this work before? N/A 

Chrome version: Version 68.0.3440.75 (Official Build) Built on Ubuntu  Channel: stable
OS Version: Ubuntu 18.04, 4.15.0-32-generic
Flash Version: 

Starting Chromium with --ignore-certificate-errors flag fixes the issue but it compromises security.