Site Can't be Reached on Snapshot: /camera/generateSnapshot

[ChristianN1]

Hi, has anyone else been experiencing issues with snapshots for the past 2–3 days?

Everything was working fine before, but now the API returns a URL that leads to either a 400 or 502 error when trying to access the image.

[ConnorL]

Hi @ChristianN1,

Working fine for me (I'm on spn28.meraki.com). Typically when we see a 502 it's due to the connection between spn <> MV being blocked, this relies on TCP 30001 being allowed. Does cloud-streaming work correctly for this MV?

Cheers,

Connor

[ChristianN1]

Yes, in the Meraki network I can access the stream without any issues. Outbound I don’t have any firewall rules in place that would block traffic. Is there anything else I should check? I’m running an MX64.

thanks

[ConnorL]

Is that local LAN streaming, or cloud streaming? Easy test is to stream from a different network, e.g. iPhone portable hotspot.

Feel free to drop me a DM with a link to your MV and I'll check the connectivity stats.

[ChristianN1]

It's definitely cloud streaming.

[ConnorL]

Hmm, just moved my MV to spn3 and I got a 502 the first couple times I attempting to load the returned URL, but then the image did load after ~ 20 seconds after requesting the original snapshot.

If you're consistently seeing a delay, please do raise a support case. 

Cheers,

Connor.

[ConnorL]

Just tried another couple snapshots and it's consistently loading after ~1-2 seconds after the snapshot request. As above if you are seeing issues please do raise a Support case 😁

[ChristianN1]

The situation is that I have multiple devices in the cloud that pull snapshots from this interface. Could continuous parallel access (for example, every 1–2 seconds per device) overload the API? I need to turn off the device at home to test this. I mean, is there a limit on the number of API requests, or are the snapshots only available for a limited time?

[ConnorL]

I believe an MV will only store the last 10 snapshot requests, after this they're written over, and the snapshot URL will no longer be valid (it'll return a 400).

The API globally has a limit of 10 calls per second.

[PhilipDAth]

I've had this issue before.  Frequently.

What I ended up doing was creating a queue of all the snapshots I wanted.  Then grab a request from the queue and try to process it.  If it fails, wait 5s and try again.  Keep doubling the wait time.  Attempt a total of 10 times, then give up.

[ChristianN1]

Thank you so far. Unfortunately, none of that has helped; the call count is correct, and I wait long enough for the image to have loaded. Now I noticed that the JSON returns the following:

{"url":"https://spn3.meraki.com/stream/jpeg/snapshot/<xxx>","expiry":"Access to the image will expire at 2025-08-19T22:33:45-07:00"}

What’s interesting is that the time lies in the past. (Execution time 2025-08-20!) How can that be? I’m not even passing the “timestamp” parameter!?

Edit: Or does 7 a.m. here refer to 08/20? But even then, I don’t know which time zone 7 a.m. refers to – in GMT+2 Berlin, it’s already past.

[ConnorL]

2025-08-19T22:33:45-07:00 = GMT-7 aka Pacific Time PDT

The snapshot URL is valid for 1hr since the snapshot was requested. If you're still facing issues, I'd recommend a support ticket as they'll have more context / visibility into your specific issue(s).

[ChristianN1]

Guys.. it was so simple. A firmware upgrade was needed... it hadn’t been done for about a year. With the new firmware it works again. Thanks for the support!