Corporate network setup
Customer IT supplies the permitted backend/proxy addresses and approved certificate authority (CA). The deployment team applies them on the robot and in any containers that make those connections. Nimbus support uses the network report to distinguish routing, trust, and protocol failures.
Configure the proxy
Merge the relevant connection settings into the active nimbus.json, normally
/etc/nimbus/nimbus.json, preserving its API key and other settings:
{
"server": "https://api.cognimbus.com",
"httpsProxy": "http://proxy.company.example:8080"
}
Use the actual backend and proxy approved for this installation. server identifies Nimbus;
httpsProxy identifies the gateway used for outbound connections. Leave the proxy unset for a
direct installation. This example does not configure proxy credentials or client certificates.
Restart the affected Nimbus services during a suitable maintenance window after changing their
connection settings. Installer tools and the Docker daemon have separate proxy configuration;
changing nimbus.json alone does not configure them. Customer IT must allow the required backend
destinations and preserve HTTP/2 through any HTTPS inspection or CONNECT tunnel. Proxy traffic
using HTTP/1.1 for CONNECT can still carry HTTP/2 to the backend inside the tunnel.
Trust a CA supplied by IT
An inspection gateway or private server may use a certificate issued by the company's own CA.
Installing the approved CA in the OS trust store lets Agent verify that server normally. This
requires no new certificate setting in nimbus.json. It does not make the robot present a client
certificate.
On Ubuntu/Debian, the deployment team obtains the approved CA certificate from customer IT in
PEM format with a .crt extension, using one certificate per file. With the ca-certificates
package installed, install the file and rebuild the trust store:
sudo install -m 0644 company-root-ca.crt /usr/local/share/ca-certificates/company-root-ca.crt
sudo update-ca-certificates
This affects applications that use the system trust store. Customer IT should confirm the CA's identity before deployment. See the Ubuntu certificate-store manual for the file and update requirements.
Restart Agent and any installed Sidecar during a suitable maintenance window so new connections use the updated trust store. For a standard systemd installation:
sudo systemctl restart nimbus
# When nimbus-sidecar is installed:
sudo systemctl restart nimbus-sidecar
Other supported systems use their own trust-store and service-management procedures. Installer tools also need the approved trust before downloading through inspection. Containerized Agent or other outbound workloads need the CA in their own trust store; adding it only to the host is insufficient. For lasting container setup, add it to the image and rebuild the image rather than editing a disposable running container. See Docker CA certificate guidance.
Customer IT owns CA expiry and renewal. Replace the approved certificate through the same
deployment procedure, refresh the trust store, and restart affected services. The existing
/etc/nimbus/tls/agent.pfx serves incoming local HTTPS; it has a separate role and should not be
replaced with the corporate CA.
Verify the installation
Use the supported Release Agent/Sidecar deployment for qualification. Some developer-build transport paths bypass certificate verification, so their success is insufficient evidence. Keep normal certificate verification enabled.
nimbus debug network --timeout 15
# If Agent cannot stay running:
sudo nimbus debug network --offline --config /etc/nimbus/nimbus.json --timeout 15
Check TLS verification and backend HTTP/2 separately. Trusting the CA does not make an HTTP/1.1-only gateway suitable for native gRPC. If the check reports a proxy, trust, or protocol failure, send its redacted report to customer IT and Nimbus support. See the Debug Manager for options and result meanings.