No cloud / internet connection#
Symptom: local devices respond, but the Octave platform shows the device as offline, or remote access fails.
Quick check#
On the Configuration page, the Connectivity card already checks the default gateway and the DNS servers. Then, on the Troubleshooting page:
| # | Card | If it fails |
|---|---|---|
| 1 | Network Overview — exactly one default route, on eth0 | No default route → set a gateway (Static) or check DHCP |
| 2 | Connectivity to the default gateway | Wrong gateway, or the gateway isn't in eth0's subnet |
| 3 | Connectivity to 1.1.1.1 | The site blocks internet, or the gateway doesn't route out |
| 4 | DNS Lookup octave.energy | DNS is broken → add a DNS server, or use Override (Scenario 1) |
| 5 | Octave Connectivity | One or more Octave endpoints blocked → firewall (see below) |
| 6 | HTTP / HTTPS Test https://octave.energy | TLS inspection or a proxy — ask the site to exempt the device |
| 7 | NTP Connectivity | Time sync blocked (UDP 123). A wrong clock breaks TLS. |
Tip
Connectivity to 1.1.1.1 works but DNS Lookup fails almost always means a DNS problem. It's the most common cause after a change from DHCP to static.
Octave Connectivity#
Octave Connectivity tests TCP — and TLS where relevant — to every fixed endpoint the device needs. Each row shows the resolved IP, the TCP and TLS result, and the impact.
Firewall requirements for the site's IT team#
The device only makes outbound connections. Nothing on the internet connects into the site.
| Purpose | Destination | Port |
|---|---|---|
| Octave Cloud | octave.energy | TCP 443 |
| AWS IoT Core, credentials, control plane | *.iot.eu-west-1.amazonaws.com, *.credentials.iot.eu-west-1.amazonaws.com | TCP 443 |
| AWS Greengrass | greengrass-ats.iot.eu-west-1.amazonaws.com | TCP 443 |
| AWS IoT Secure Tunneling (remote access) | data.tunneling.iot.eu-west-1.amazonaws.com | TCP 443 |
| Certificate trust | www.amazontrust.com | TCP 443 |
| Logs, secrets, metrics, packages | logs.eu-west-1.amazonaws.com, secretsmanager.eu-west-1.amazonaws.com, aps-workspaces.eu-west-1.amazonaws.com, *.d.codeartifact.eu-west-1.amazonaws.com | TCP 443 |
| Software updates (Mender) | eu.hosted.mender.io, *.r2.cloudflarestorage.com | TCP 443 |
| Octave remote support | 34.246.245.148 | TCP 22 |
| Time sync | be.pool.ntp.org (or the site's NTP server) | UDP 123 |
| DNS | the site's DNS server, or a public resolver | UDP/TCP 53 |
Note
Most of these are cloud services whose IP addresses change. Ask the site to allow them by hostname, not by IP. Remote support is the exception: it uses a fixed IP.