phuthuycoding/hik-connect-proxy-viewer-stream repository overview

⁠hik-connect-proxy-viewer-stream

Stream proxy for Hikvision recorders (NVR/DVR) whose account only works through Hik-Connect / the SDK port and is refused on RTSP (401). It logs in with Hikvision's HCNetSDK, pulls the channel on demand, remuxes the MPEG-PS output with ffmpeg (no re-encoding) and serves it as HLS through mediamtx.

Part of hik-connect-proxy-viewer⁠: pair it with phuthuycoding/hik-connect-proxy-viewer-web for the password-protected web app, or install both with one Helm chart: oci://ghcr.io/phuthuycoding/charts/hik-connect-proxy-viewer.

⁠What is inside

• mediamtx (PID 1) with runOnDemand on any path ch<N>: the first viewer of /ch7/index.m3u8 triggers a recorder login for channel 7, later viewers share it, the login is dropped when nobody watches.
• pull_stream.py: HCNetSDK real-play callback -> ffmpeg -f mpeg -c copy -> RTSP publish to mediamtx.
• discover.py: probes every channel, keeps the ones the account may view (with the recorder's channel names) and serves them on :9000/channels.
• get_sdk.sh: Hikvision's SDK is not in this image. It is downloaded into /sdk at first start from hikvision.com (or from HCNETSDK_ZIP_URL). Mount a volume on /sdk to keep it.

⁠Usage

docker run -d --name hik-stream \
  -e HIK_DOMAIN=recorder.example.net -e HIK_SDK_PORT=8000 \
  -e HIK_USER=USER -e HIK_PASS=PASS \
  -e MTX_PUBLISH_BASE=rtsp://puller:[email protected]:8554 \
  -v hik_sdk:/sdk \
  -v $PWD/mediamtx.yml:/mediamtx.yml:ro \
  -p 127.0.0.1:8888:8888 -p 127.0.0.1:9000:9000 \
  phuthuycoding/hik-connect-proxy-viewer-stream:latest

mediamtx.yml is in the repo under chart/files/. Ports: 8888 HLS (/ch<N>/index.m3u8), 9000 channel list (/channels). Never run two replicas against the same account: each channel is one SDK session.

Platform: linux/amd64 only (the SDK is x86_64). Tags: latest, sha-<commit>, X.Y.Z.

Runs fine as non-root (--user 10001:10001; /sdk is world-writable in the image). Prefer that on shared Kubernetes nodes: mediamtx needs one inotify instance per process and Linux counts them per UID, so a root container on a busy node can hit couldn't initialize inotify: too many open files.

⁠Disclaimer

For personal use with accounts you are authorized to use. Not affiliated with Hikvision; the Hikvision SDK is proprietary and downloaded by you under Hikvision's terms. MIT licensed, provided as is.