# How to connect HikVision cameras off site **URL:** \ **Category:** Discussion & Solutions\ **Tags:** solved\ **Created:** [July 9, 2026, 6:26am UTC](https://onehack.st/t/how-to-connect-hikvision-cameras-off-site/323740 "2026-07-09T06:26:55Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Stick\_Chick](https://onehack.st/user_avatar/onehack.st/stick_chick/32/154033_2.png) [@Stick\_Chick](https://onehack.st/u/Stick_Chick)\ **Post date:** [July 9, 2026, 6:26am UTC](https://onehack.st/t/how-to-connect-hikvision-cameras-off-site/323740/1 "2026-07-09T06:26:56Z")
I’m doing an internship at a company and I had to connect cameras in construction site to a completely off site office that has a different network. I connected using Cloud P2P but that streams only for 5 minutes and then stops streaming but my Manager doesn’t want that. How can I stream the live feed 24/7 for free? ---
**Author:** ![Timmy1](https://onehack.st/user_avatar/onehack.st/timmy1/32/173894_2.png) [@Timmy1](https://onehack.st/u/Timmy1)\ **Post date:** [July 9, 2026, 9:36pm UTC](https://onehack.st/t/how-to-connect-hikvision-cameras-off-site/323740/2 "2026-07-09T21:36:14Z")
Just use the Hik-Connect app from the app stores - its free and you can view them on any phone at any time. ---
**Author:** ![Emanuel\_Branson](https://onehack.st/user_avatar/onehack.st/emanuel_branson/32/178452_2.png) [@Emanuel\_Branson](https://onehack.st/u/Emanuel_Branson)\ **Post date:** [July 10, 2026, 8:54pm UTC](https://onehack.st/t/how-to-connect-hikvision-cameras-off-site/323740/3 "2026-07-10T20:54:05Z")
# πŸ”₯πŸ“Ή 24/7 CONSTRUCTION-SITE CAMERA STREAMING TO AN OFF-SITE OFFICE β€” FREE, STABLE & SECURE πŸŒπŸ— * * * > 🎯 **Cloud P2P stopping after five minutes is usually a vendor/app limit, not a camera limit. The practical free solution is to access the cameras or NVR through their RTSP/ONVIF stream over a secure site-to-office VPN β€” not by exposing camera ports directly to the internet.** πŸ‘‡ * * * ## 🧠 FIRST β€” CHECK WHAT YOU HAVE ```plaintext IDENTIFY THE CAMERA SETUP: ────────────────────────────────────────────── β‘  IP cameras connected directly to the site router β‘‘ IP cameras connected to an NVR β‘’ A vendor cloud-P2P app only LOOK FOR THESE FEATURES: β†’ RTSP support β†’ ONVIF support β†’ NVR web interface β†’ Main stream + sub-stream options β†’ Local username/password creation WHY IT MATTERS: β†’ RTSP/ONVIF gives you a direct live stream β†’ An NVR can provide one managed source for multiple cameras β†’ Cloud P2P apps often impose session limits ``` Many IP cameras and NVRs support RTSP/ONVIF, which lets third-party clients access authenticated live feeds; the exact menu and URL format depend on the manufacturer. [1][2] * * * ## πŸ₯‡ BEST FREE OPTION β€” TAILSCALE VPN + NVR/RTSP ```plaintext RECOMMENDED ARCHITECTURE: ────────────────────────────────────────────── CONSTRUCTION SITE OFFICE ──────────────── ────── Cameras β†’ NVR / mini-PC β†’ Tailscale ═══ VPN ═══> Office PC encrypted tunnel WHY THIS IS THE BEST OPTION: βœ… No five-minute P2P limit βœ… No router port forwarding βœ… Encrypted end-to-end βœ… Works across different networks βœ… Free for a small team/personal use βœ… Office sees the site NVR as if it were local ``` Install Tailscale on a device that can reach the cameras locally β€” ideally the NVR if it supports it, otherwise a small always-on Windows PC, Linux mini-PC, or Raspberry Pi at the construction site β€” and also install it on the office viewing PC. Mesh VPN access is specifically recommended over publicly exposing camera interfaces or RTSP ports. [3][4] * * * ## πŸ”§ SETUP PATH A β€” VIEW DIRECTLY IN VLC ```plaintext BEST FOR: β†’ One or a few cameras β†’ Quick proof-of-concept β†’ No recording required STEP 1: Enable RTSP or ONVIF in each camera/NVR settings. STEP 2: Create a LIMITED "viewer" account: β†’ Live-view permission only β†’ No admin or configuration rights STEP 3: Install Tailscale at site + office. STEP 4: From the OFFICE PC, open VLC: Media β†’ Open Network Stream STEP 5: Enter the site camera/NVR RTSP URL, using its Tailscale IP or hostname: rtsp://viewer:password@ :554/ IMPORTANT: β†’ The stream path is manufacturer-specific. β†’ Find it in the camera/NVR manual or web UI. β†’ Use the sub-stream for lower bandwidth. ``` VLC can open an authenticated RTSP live feed, and NVR documentation commonly provides a live-stream URL format plus channel and stream selection. [2][5] * * * ## πŸ–₯ SETUP PATH B β€” BEST FOR MULTIPLE CAMERAS ```plaintext BEST FOR: β†’ Construction site with multiple cameras β†’ One central office dashboard β†’ 24/7 live viewing β†’ Optional motion recording later AT THE SITE: Cameras β†’ NVR OR always-on mini-PC INSTALL ONE OF THESE FREE OPTIONS: β†’ Frigate + go2rtc β†’ Agent DVR β†’ Shinobi CE RECOMMENDED SIMPLE STACK: Cameras/NVR RTSP β†’ go2rtc / Frigate dashboard β†’ Tailscale VPN β†’ Office browser ADVANTAGES: β†’ One dashboard for every camera β†’ One connection to each camera, then restream to multiple office viewers β†’ Easier health monitoring β†’ Optional recording and motion alerts ``` Frigate’s bundled go2rtc component can take an RTSP source and present it for live viewing/restreaming; its documentation recommends deliberately controlling external exposure and keeping direct RTSP ports private. [6][7] * * * ## ⚠ DO NOT DO THIS ```plaintext ❌ Do not forward RTSP port 554 directly to the internet ❌ Do not expose NVR admin panels publicly ❌ Do not use the default camera admin password ❌ Do not give every office user an admin account ❌ Do not run the camera main stream at maximum bitrate if site upload bandwidth is limited WHY: β†’ Camera/NVR interfaces are frequent targets β†’ Direct RTSP endpoints often lack modern browser-grade protections β†’ A VPN keeps the system off the public internet ``` Frigate’s remote-access guidance explicitly warns against exposing RTSP and go2rtc administration ports publicly because they may lack authentication, and recommends using a mesh VPN such as Tailscale instead. [3] * * * ## πŸ“‘ BANDWIDTH β€” THE PART THAT DECIDES IF 24/7 WORKS ```plaintext ESTIMATE SITE UPLOAD NEEDS: ────────────────────────────────────────────── SUB-STREAM PER CAMERA: 480p/720p at 0.5–1.5 Mbps MAIN STREAM PER CAMERA: 1080p at 2–4 Mbps 4K at 8–16+ Mbps EXAMPLE: 4 cameras Γ— 1 Mbps sub-stream = ~4 Mbps continuous SITE upload BEST PRACTICE: β†’ Use sub-streams for the office wall/dashboard β†’ Open main stream only when investigating β†’ Set H.264 or H.265 depending on compatibility β†’ Prefer wired Ethernet from camera to NVR/switch ``` A central restreaming setup is valuable because it can avoid opening separate direct connections from every viewer to each camera; go2rtc/Frigate is designed for this kind of stream handling. [8][7] * * * ## πŸ“Š WHICH ROUTE TO CHOOSE? | SETUP | COST | DIFFICULTY | BEST FOR | 24/7 VIEW | | --- | --- | --- | --- | --- | | **Vendor Cloud P2P** | Usually free | Easy | Occasional viewing | ❌ Limited | | **Tailscale + VLC RTSP** | Free | Easy–medium | 1–4 cameras, quick setup | βœ… | | **Tailscale + NVR web UI** | Free | Easy | Existing NVR, multi-camera view | βœ… | | **Tailscale + Frigate/go2rtc** | Free software | Medium | Many cameras, dashboard, future recording | βœ… | | **Public port forwarding** | Free | Medium | None β€” avoid it | 🚨 Unsafe | * * * ## πŸ’‘ PRO TIPS - πŸ”₯ **Use the existing NVR if there is one** β€” it is usually the quickest stable route because all cameras are already consolidated there. - 🎯 **Create a separate read-only `office_viewer` account** β€” never use the NVR/camera admin credentials on office machines. - πŸ“Ά **Test one camera’s sub-stream in VLC first** before deploying an entire dashboard; this proves RTSP, permissions, routing, and bandwidth. - πŸ— **Use a wired connection for the site gateway/NVR** where possible; construction-site Wi-Fi is often the real cause of stream drops. - πŸ’» **Use an always-on mini-PC at the site only if the NVR cannot run Tailscale or provide remote access through the VPN.** - πŸ”’ **Get manager approval before changing surveillance networking or enabling external access** β€” camera feeds are sensitive company/security data. * * * _For a free 24/7 setup, stop relying on the vendor’s Cloud P2P session. Enable RTSP/ONVIF on the existing NVR or cameras, create a read-only viewing account, connect the site and office through Tailscale, then view the stream in VLC or a Frigate/go2rtc dashboard. That replaces a time-limited cloud relay with private, continuous, encrypted access._ πŸ”₯πŸ“ΉπŸ— ---
**Author:** ![Stick\_Chick](https://onehack.st/user_avatar/onehack.st/stick_chick/32/154033_2.png) [@Stick\_Chick](https://onehack.st/u/Stick_Chick)\ **Post date:** [July 12, 2026, 6:07am UTC](https://onehack.st/t/how-to-connect-hikvision-cameras-off-site/323740/4 "2026-07-12T06:07:26Z")
Thank you so much That’s a really nice workaround but is there any method to do it without a 24/7 computer or hardware at the site? Also, isn’t remote desktop a good solution for 24/7 streaming if there is a computer at the site? Also um could someone please tell me the port forwarding method It’s really complex for me ---
**Author:** ![Ze380y](https://onehack.st/user_avatar/onehack.st/ze380y/32/48760_2.png) [@Ze380y](https://onehack.st/u/Ze380y)\ **Post date:** [July 23, 2026, 4:38pm UTC](https://onehack.st/t/how-to-connect-hikvision-cameras-off-site/323740/5 "2026-07-23T16:38:18Z")
![Watch Your Site Cameras Anywhere 24/7 Free](https://onehack.st/uploads/default/original/3X/0/d/0d2a0fe0dbff9f00a888db9bbc10a7e6022d35a9.jpeg) Good questions β€” let me hit all three straight, because the answers change everything. First, the thing nobody said: **that 5-minute cutoff is a limit of the free _preview_ in the app, not your cameras.** The actual video (the camera’s RTSP feed β€” a standard live-video link) runs forever. The whole job is just getting that feed to the office 24/7. So: ━━━━━━━━━━━━━━━━━━━━━━━━━ πŸ–₯ **β€œIs remote desktop good for this?”** β†’ **No β€” it’s the wrong tool.** RDP/AnyDesk stream a _picture of a PC’s screen_, not the camera. That means it **needs a PC switched on 24/7** (the exact thing you’re trying to avoid), only **one person can watch at a time** , it’s heavy/laggy, and if the PC hiccups the feed is just gone. Fine for a quick peek, useless as a 24/7 wall of cameras. ━━━━━━━━━━━━━━━━━━━━━━━━━ πŸ”Œ **β€œExplain port forwarding simply.”** β†’ 4 steps β€” but read the ⚠ first, it’s probably why it’ll fail on a site. > **πŸ”§ The 4 steps (do this only if the site has a real public IP β€” see warning)** > > 1. In the site router, give the **NVR a fixed local IP** (e.g. 192.168.1.64) so it never changes. > 2. In the router’s **Port Forwarding** page, forward port **554** (the RTSP video port) β€” and 8000 β€” to that NVR IP. > 3. Sign up for **free DDNS** (a fixed web name for your changing home IP) β†’ [https://www.duckdns.org](https://www.duckdns.org) (or the NVR’s built-in **Hik-Connect DDNS** ). > 4. From the office, open **VLC β†’ Network Stream** and type: > `rtsp://user:pass@yourname.duckdns.org:554/Streaming/Channels/101` > (101 = camera 1 main; use 102 for a lighter sub-stream, better for 24/7.) > πŸ”’ **Must-do:** change the camera’s **default password** and use a non-standard port β€” open Hik ports get hit by bots within hours. > Find the NVR’s IP with Hikvision’s **SADP** tool β†’ [https://www.hikvision.com/en/support/tools/hitools/](https://www.hikvision.com/en/support/tools/hitools/) ⚠ **The catch that wastes everyone’s day: CGNAT.** Most construction sites run on a **4G/mobile router** , and mobile ISPs don’t give you a real public IP β€” so **port forwarding silently does nothing** , no matter how perfectly you set it up. Quick test: check your router’s WAN IP, then open **[whatismyip.com](http://whatismyip.com)** β€” if they _don’t match_, you’re behind CGNAT and port-forwarding is dead. Use one of the no-hardware paths below instead πŸ‘‡ ━━━━━━━━━━━━━━━━━━━━━━━━━ πŸ“‘ **β€œAny way without a 24/7 computer at the site?”** β†’ **Yes β€” three, and none needs a PC.** Your **NVR is already the always-on device.** Lean on it: **β‘  Just fix Hik-Connect (zero hardware, zero setup)** On the NVR: _Network β†’ Platform Access β†’ enable_, then **share the device** to the office’s Hik-Connect account. A properly _added_ device streams continuously β€” the 5-min stop only happens on the anonymous quick-preview. β†’ setup: [https://supportusa.hikvision.com/support/solutions/articles/17000110900-how-to-setup-hikconnect](https://supportusa.hikvision.com/support/solutions/articles/17000110900-how-to-setup-hikconnect) **β‘‘ A $30 travel router = the tunnel box (not β€œa computer”)** ⭐ The NVR can’t run a VPN itself, so drop a tiny **GL.iNet** pocket router at the site β€” it has **Tailscale/ZeroTier built in (just toggle it on)**. It joins a private mesh with the office; you then open the NVR exactly like you’re on-site. **Beats CGNAT, nothing exposed to the internet.** β”œβ”€ enable Tailscale on GL.iNet β†’ [https://docs.gl-inet.com/router/en/4/interface\_guide/tailscale/](https://docs.gl-inet.com/router/en/4/interface_guide/tailscale/) β”œβ”€ full Hik-NVR + Tailscale walkthrough β†’ [https://cats.fish/posts/Free-Secure-Remote-HIKVision-NVR-Access/](https://cats.fish/posts/Free-Secure-Remote-HIKVision-NVR-Access/) └─ or on any cheap OpenWrt router β†’ [https://github.com/adyanth/openwrt-tailscale-enabler](https://github.com/adyanth/openwrt-tailscale-enabler) **β‘’ Make the NVR dial OUT to a free server (EHome/ISUP) β€” the 4G-proof trick** ⭐⭐ Hik gear speaks a push protocol ( **ISUP/EHome** ): the NVR _calls out_ to a server you run on a cheap/free cloud box and hands it the stream. **No port-forward, no fixed IP, works on any 4G/CGNAT connection** , and the only thing at the site is the NVR you already have. β”œβ”€ πŸ“„ field-by-field setup β†’ [https://www.cnblogs.com/kumukim/p/18815023](https://www.cnblogs.com/kumukim/p/18815023) β”œβ”€ 🧰 server that receives it β†’ [https://github.com/yingyemin/simple-media-server](https://github.com/yingyemin/simple-media-server) └─ πŸ” republish as a normal stream β†’ [https://github.com/CharlesPu/HIKPusher](https://github.com/CharlesPu/HIKPusher) > **πŸŽ₯ Want the office to watch in a plain browser tab (unlimited people, no app)?** > > Run **go2rtc** (one tiny file) next to the NVR or on the same VPS β€” it turns the camera’s RTSP into a **browser WebRTC** page anyone can open, no login, no app, lowest lag: > β†’ [https://github.com/AlexxIT/go2rtc](https://github.com/AlexxIT/go2rtc) > Put **Cloudflare Tunnel** in front of it for a clean public link with no open ports: > β†’ [https://github.com/blakeblackshear/frigate/discussions/6144](https://github.com/blakeblackshear/frigate/discussions/6144) ━━━━━━━━━━━━━━━━━━━━━━━━━ **For a construction site specifically:** it’s almost certainly on 4G β†’ **skip port-forwarding, go straight to β‘‘ (travel router + Tailscale) or β‘’ (EHome push).** Both are free, survive CGNAT, and add zero hardware beyond the NVR that’s already sitting there. The cameras were never the wall β€” the app’s timer was. Move off the app and the feed never stops. ---
**Author:** ![Stick\_Chick](https://onehack.st/user_avatar/onehack.st/stick_chick/32/154033_2.png) [@Stick\_Chick](https://onehack.st/u/Stick_Chick)\ **Post date:** [July 25, 2026, 7:59am UTC](https://onehack.st/t/how-to-connect-hikvision-cameras-off-site/323740/6 "2026-07-25T07:59:47Z")
Hey, Thank you so much! Could you please explain the (EHome/ISUP) one, I couldn’t get it to work. Also, my company has Webuzo subscription, would that be of any help? ---
**Author:** ![Ze380y](https://onehack.st/user_avatar/onehack.st/ze380y/32/48760_2.png) [@Ze380y](https://onehack.st/u/Ze380y)\ **Post date:** [July 25, 2026, 10:58am UTC](https://onehack.st/t/how-to-connect-hikvision-cameras-off-site/323740/7 "2026-07-25T10:58:54Z")
πŸ”Œ **The EHome/ISUP fix** β€” it only works when a machine on a **public IP** is actually listening for the NVR to dial into. In the NVR: _Platform Access β†’ ISUP_, then match these **3 fields on both ends** πŸ‘‡ β”œβ”€ πŸ“‘ **Version:** EHome **v5.0** β”œβ”€ 🌐 **Server IP + Port:** your public IP Β· **7660** └─ πŸ”‘ **EHome key + Account:** same on device and server ⚠ If nothing is actually running/listening on **7660** , it just _silently_ fails β€” that’s 90% of β€œI couldn’t get it to work.” πŸ–₯ **The receiver** (the thing listening on 7660): β”œβ”€ ⚑ easiest β†’ **iVMS-4200** (it _is_ the ISUP server) └─ 🧰 self-host β†’ [simple-media-server](https://github.com/yingyemin/simple-media-server) Β· [LiveNVR field-by-field guide](https://www.cnblogs.com/kumukim/p/18815023) ━━━━━━━━━━━━━━━━━━━━━━━━━ βœ… **And yes β€” Webuzo is a BIG help!** It means your company already runs a **VPS with a public IP** β€” which is the exact box EHome was missing. β†’ `SSH in β†’ run the ISUP receiver (or go2rtc/MediaMTX, or a Tailscale/WireGuard node) β†’ point the NVR at its-ip:7660` πŸ’‘ That VPS becomes your free, always-on relay β€” no extra hardware at the site at all.