# Opening the camera and pulling the calibration file hangs in SDK, not through browser

**URL:** <https://community.stereolabs.com/t/opening-the-camera-and-pulling-the-calibration-file-hangs-in-sdk-not-through-browser/11775>\
**Category:** Software\
**Tags:** calibration\
**Created:** [October 7, 2026, 11:34am UTC](https://community.stereolabs.com/t/opening-the-camera-and-pulling-the-calibration-file-hangs-in-sdk-not-through-browser/11775 "2026-10-07T11:34:47Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ejr-sterolabs](https://community.stereolabs.com/user_avatar/community.stereolabs.com/ejr-sterolabs/32/6526_2.png) [@ejr-sterolabs](https://community.stereolabs.com/u/ejr-sterolabs)\
**Post date:** [October 7, 2026, 11:34am UTC](https://community.stereolabs.com/t/opening-the-camera-and-pulling-the-calibration-file-hangs-in-sdk-not-through-browser/11775/1 "2026-10-07T11:34:47Z")

</div>

On a camera with no cached `SN<serial>.conf`, `Camera::open()` blocks and never  
returns. No error code, no timeout — the thread sits in `open()` indefinitely.

Fetching the same file manually works:  
`https://calib.stereolabs.com/?SN=<serial>` returns the .conf from a browser on  
another machine. Dropping that file into `/usr/local/zed/settings/SN<serial>.conf`  
makes `open()` succeed immediately, so the camera and the rest of the setup are fine. If I delete it, the download step always fails though.

Could this be a difference on the hosting side between getting it on HTTP port 80 vs HTTPS?

---

<div class="post-metadata">

**Author:** ![Myzhar](https://community.stereolabs.com/user_avatar/community.stereolabs.com/myzhar/32/11_2.png) [@Myzhar](https://community.stereolabs.com/u/Myzhar)\
**Post date:** [October 7, 2026, 3:27pm UTC](https://community.stereolabs.com/t/opening-the-camera-and-pulling-the-calibration-file-hangs-in-sdk-not-through-browser/11775/2 "2026-10-07T15:27:05Z")

</div>

Hi @ejr-sterolabs,  
welcome to the [StereoLabs](http://www.stereolabs.com) community.

> [@ejr-sterolabs](#):
>
> Could this be a difference on the hosting side between getting it on HTTP port 80 vs HTTPS?

The calibration server answers the same way on both ports, so the difference is most likely on the network path of the machine running the ZED SDK; a blocking `open()` with no error usually means the outgoing request is silently dropped or held by a firewall, proxy, or container network, rather than refused. Please run these two commands **on the same machine where the SDK hangs** and share the output:

```auto
curl -v --max-time 15 -o /dev/null "http://calib.stereolabs.com/?SN=<serial>"
curl -v --max-time 15 -o /dev/null "https://calib.stereolabs.com/?SN=<serial>"

```

Please also tell us the ZED SDK version, the camera model, the platform (Jetson/x86, OS or JetPack version), and whether you are running inside Docker or behind a proxy.

Meanwhile, copying the file to `/usr/local/zed/settings/` is the official procedure for offline or restricted networks, as described in [What is the calibration file?](https://support.stereolabs.com/articles/3095519603-what-is-the-calibration-file)

Best,  
Walter
