SE-NET-010: Hub not reachable through the relay
From SecureEyes 1.2. Away from home, video comes from your Hub through the SecureEyes relay. HTTP 502 means the relay answered and could not reach the Hub behind it: the Hub may be off, offline, or not connected to the relay. This device also gets this code when it could not fetch the video through the relay at all, so a connection problem on this device's side can cause it too.
What it says
SE-NET-010: Hub not reachable through the relay. The relay is up, but your Hub did not answer it. Check that the Hub is on and online, then try again.
Where you see it
On the Live stage (full screen shows no code), for a camera that plays through the Hub's relay away from home: the camera's panel reads "The Hub is not serving <camera>" with the badge OFFLINE ("Loading <camera>" while a camera that has never played is still being tried), and an amber line under it ends with "Error SE-NET-010". The amber line reads "HTTP 502 · the relay could not reach the Hub" before the code. The same failure is the subtitle of the connection row in the camera's settings under Connection & Access, and on a Mac wall window the tile shows NO SIGNAL or RECONNECTING with the bare code under it. The app files any failure whose words carry the status 502 or "bad gateway" under this code, so it also comes as an error message after a camera action (Run test and Reboot under Maintenance, Check Again, Fetch Thumbnail, the Change OSD name switch, Light on Live) whose failure says so.
What to do
- Check that the Hub has power and that its internet connection works. The Hub keeps its line to the relay open only while it is online.
- Check that this device is connected to the internet.
- Choose More, then Hub. If the page reads The Hub is not answering, see When the app cannot reach your Hub.
- Back on Live, choose Retry Now on the panel. While it reads "Loading <camera>" it is still retrying on its own and has no buttons.