It looks like you are either using directConnect or launching with a local driver provider (not having seleniumAddress or directConnect) in your configuration file. You need to run webdriver-manager update.
Previously I had extra flags to not download standalone or gecko with webdriver-manager update --standalone false --gecko false. This is no longer the case if you are starting via a local driver provider. You will need the selenium standalone jar file.
You could run this with a script in package.json. Something like:
"scripts": { "webdriver-update": "webdriver-manager update" }
Please check that if u behind a firewall:
This looks like you are trying to do the https call to the selenium-release.storage.googleapis.com or chromedriver.storage.googleapis.com.
If you are behind a proxy, then you should use the following flags:

--ignore_ssl Ignore SSL certificates --proxy Proxy to use for the install or update command

It looks like you are either using `directConnect` or launching with a `local` driver provider (not having `seleniumAddress` or `directConnect`) in your configuration file. You need to run `webdriver-manager update`.
Previously I had extra flags to not download standalone or gecko with `webdriver-manager update --standalone false --gecko false`. This is no longer the case if you are starting via a local driver provider. You will need the selenium standalone jar file.
You could run this with a script in package.json. Something like:
"scripts": { "webdriver-update": "webdriver-manager update" }
Then execute this with: `npm run webdriver-update`. How do you check if the binaries are there? In your project, navigate to `node_modules/protractor/node_modules/webdriver-manager/selenium/`. This is where the `update-config.json` and your downloaded binaries are located.