[🐛 Bug]: Chromium does not trust HTTPS certs

[Chekote]

What happened?

Steps to reproduce:

Start a container using the seleniarm/standalone-chromium:4.1.1-alpha-20220119 image. Connect to the VNC server in the container. Load Chromium. Visit an HTTPS site, such as https://www.google.com.

Expected Behavior:

The site should load normally.

Actual Behavior:

The error "Your connection is not private" error appears, stating that the cert authority is not valid.

Command used to start Selenium Grid with Docker

version: '3.9'

services:
  chrome:
    image: seleniarm/standalone-chromium:4.1.1-alpha-20220119
    healthcheck:
      test: ["CMD", "wget", "localhost:4444", "-O", "/dev/null"]
      interval: 30s
      timeout: 10s
      retries: 3
    depends_on:
      - web
      - proxy
    environment:
      SCREEN_WIDTH: $WEBDRIVER_WIDTH
      SCREEN_HEIGHT: $WEBDRIVER_HEIGHT
      http_proxy: http://proxy:3128
      https_proxy: http://proxy:3128
      no_proxy: REDACTED
    shm_size: 2g
    volumes:
      - project:/var/www
      - ../features/artifacts/chrome-downloads:/home/seluser/Downloads/
    env_file: .env
    networks:
      default:
         aliases:
            - REDACTED.chrome

### Relevant log output

```shell
Your connection is not private

Attackers might be trying to steal your information from www.google.com (for example, passwords, messages, or credit cards). Learn more

NET::ERR_CERT_AUTHORITY_INVALID

To get Chrome's highest level of security, turn on enhanced protection

Operating System

Mac OS X

Docker Selenium version (tag)

seleniarm/standalone-chromium:4.1.1-alpha-20220119

[Chekote]

You can ignore this. I determined it was because of our HTTP proxy.

[github-actions[bot]]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.