Connecting cameras from locations where there isn't a possibility to get a public IP address

Using AngelBox instead of paying for a static IP or DDNS service for connections with a dynamic public IP address

Making the connection to the cameras more secure

Bypassing firewall rules in corporate networks

Solving issues with changing local IP addresses of cameras

Avoiding configuring multiple ports when using more than one camera

When moving the cameras from one location to another

Find your cameras on the network

Doesn't need a public IP address

Doesn't need a static IP address or DDNS hostname

Keeps your network secure (no ports are open)

The communication is end-to-end encrypted

Keeps track of any changes within your network and adjusts itself

Automatic, free updates

Make sure that the devices you plan to connect are using the default ports

The AngelBox will need to have an internet connection and, at the same time, be on the subnet with the cameras/DVRs you want to connect

Some network components might block the scanning process. In that case, try connecting the AngelBox to a network switch rather than directly to the router. The same thing might happen when using business-grade network components with management options.

If your firewall filters outgoing connections as well as whitelists the ports and servers listed below

AngelBox scans the network every 5 minutes, some old devices might not handle that well. A separate network or VLAN is recommended either for security cameras or for other devices.

AngelBox, in its default configuration, requires a DHCP server to be active in the network. It is usually handled by the router. The DHCP server doesn't have to control all the devices, you can just limit the IP range, let it assign a pre-defined IP to the AngelBox, and leave all the other devices set to a static IP

When using AngelBox with wireless cameras, please note that this will double the bandwidth in your local network (stream is coming wirelessly from the camera, through the router to the AngelBox, then back to the router and to Angelcam)

With wireless cameras, be sure that the wireless network uses the same subnet with the wired devices; otherwise, those cameras won't be detected

AngelBox needs to be powered by the supplied power adapter, using adapters with lower amp ratings can result in random reboots or its inability to finish the booting process, PoE isn't supported.

Only the ethernet and micro USB ports are used at the moment. USB, HDMI*, and audio ports are intended for possible future use only.

After moving the AngelBox, make sure that the SD card is correctly inserted. When in doubt, disconnect the AngelBox, remove the SD card, put it back, and connect the AngelBox again

Ports AngelBox scans:
554, 88, 81, 555, 7447, 8554, 7070, 10554 80, 81, 8080, 8081, 8090

Ports used for outbound communication:
8900, 8901

Servers it is connecting to:
arr-rs.angelcam.com, arr-rs-eu.angelcam.com, arr-rs-na.angelcam.com and all streaming servers

Maximum number of connected cameras: 10 cameras with 2Mbps bitrate for each stream (20Mbps of total traffic shouldn't be exceeded)

Avoid restarting the AngelBox within the first 5 minutes after connecting it to your network to prevent an SD card failure