As an addition to my colleague’s response, just to check, in your first reply you say ‘I did get everything working whilst using my cellphone as a wifi hotspot’. Does this mean you used the hotspot to connect both your laptop and the Pi (ie. the Pi was not running on your corporate network, as if it was then it sounds like there’s some other issue going on).
If you had connected both the Pi and the laptop to your hotspot, and now neither is working as expected on the corporate network, then the first issue is connecting the laptop to balenaCloud, as you’ve stated. To expand a bit on the above answer, you’ll need to create a new file that contains both proxy certificates, one pasted after the other, eg:
Proxy Certificate 1
Proxy Certificate 2
which will look something like this:
You should save this as something like
proxy-ca-certs.pem, and then set
NODE_EXTRA_CA_CERTS=proxy-ca-certs.pem in the shell where you’ll run
balena-cli. With this set, you should then be able to run
balena login correctly and login then use balenaCloud.
The Pi is a slightly different matter. There’s a config variable that can be added into the
config.json in the boot partition of the provisioning image for the Pi that will allow the Pi to verify the Proxy certificates. You can do this a few different ways, the simplest is to download the provisioning image from the balenaCloud Dashboard, then mount the image on your development machine and manually editing the
config.json in the boot partition. You’ll need to add a
balenaRootCA key whose value is the contents of
proxy-ca-certs.pem which has been Base64 encoded.
config.json will end up looking something like this:
Add this to the end of the `config.json`, unmount the image, then flash it to an SD card and provision the Pi.