Get the hardware and network ready.

Choose a player that can run the display app.

Use an Apple TV HD or Apple TV 4K connected to a display by HDMI. Check that the device can install the version offered in the official App Store listing. Apple TV models without a tvOS App Store, including Apple TV (3rd generation), cannot install this app.

The published listing currently requires tvOS 15.6 or later. Check its Compatibility section before buying or updating devices, since requirements can change. A working older installation is not proof that it can install the next release.

For 4K output, use an Apple TV 4K, a 4K display and an HDMI connection that supports the chosen output mode. A 4K source alone does not make every part of the display chain 4K. See 4K Google Slides synchronization and media formats.

Check the physical setup before the content.

• Connect HDMI, select the correct input and confirm tvOS itself appears on the display.
• Keep the Apple TV powered, ventilated and accessible for maintenance. Follow the display and mount manufacturers’ installation instructions.
• Choose the display mode and text size for the viewing distance. Test any adapter, extender, receiver or splitter in the actual setup.
• For portrait screens, set TV Orientation and prepare media in the matching shape.
• Check the display’s power timer and the Apple TV’s sleep settings. App power-save schedules do not guarantee physical TV power control.

For a new installation, prefer a current Apple TV 4K that meets your network and display needs. Verify whether the chosen model includes Ethernet if you plan a wired connection. Pilot the actual media and daily operating hours before ordering a fleet.

Keep management and playback separate.

The Apple TV runs the display app. Your team manages content through app.urbanloop.ai or the management app on iPhone, iPad or Mac. Both need internet access, but remote management does not require them to be on the same local network.

The published App Store record currently lists iOS/iPadOS 15.6 or later and macOS 12.2 or later for its management app. Recheck the listing for the version you are installing. Older apps may still say EZ Plus or EZTV during the transition to UrbanLoop.

For managed Apple TVs, follow MDM deployment and Auto-Sync. App distribution, device settings and UrbanLoop content assignments are separate parts of that setup.

Allow the services your setup actually uses.

Core UrbanLoop management and player API traffic uses outbound HTTPS on TCP port 443. Start with these hosts for current UrbanLoop builds:

This is a starting point, not a complete firewall allowlist. Media downloads, connected sources and optional content use additional hosts. They vary with the files and services you choose. Earlier installed EZTV/EZ Plus builds can still use old domains, so keep existing rules until a version-specific migration has been tested.

Use the intended network for the pilot. Make sure the player can resolve hostnames, use the correct date/time and complete any required network onboarding. A working dashboard in a staff browser does not prove that the Apple TV can download its media.

No inbound port forwarding is needed for normal cloud management. AirPlay and MDM have their own network requirements. Do not replace those requirements with the two core UrbanLoop hosts.

Check downloads and connected content too.

• Uploaded media: allow the actual delivery hosts used by your content, including any redirected download destination. A successful API request alone does not confirm a video download.
• Google content: management sign-in, source selection and continuing source access are separate checks. Use the Google Workspace help if organization policy blocks the connection.
• Feeds, individual YouTube videos and remote video: test the source and playback on the target Apple TV. Hosts and delivery paths depend on the source.
• Website snapshots: the capture service must be able to reach the page. A private intranet that opens on a staff laptop is not necessarily reachable by that service. See website snapshots.
• Weather and other optional services: test the enabled features, not just the first uploaded slide.

Device activation, app installation, updates and managed-device services also need Apple access. Use Apple’s current enterprise network requirements for those services rather than copying an old ports list.

Run a small, useful network pilot.

1. Start with one screen

   Record its Apple TV model, tvOS version and display-app version. Link it using the setup guide.

2. Test representative content

   Show a still image, a complete video and each connected source you plan to use. Change a source item and check that the update reaches the screen.

3. Check remote operations

   Take a fresh screen capture and test a planned content refresh. Review timestamps as well as the image.

4. Review failures with IT

   Match the failure time with firewall, DNS or proxy logs and the exact blocked hostname. Request a targeted rule through your normal IT process. Do not disable certificate checks to hide a connection failure.

Previously downloaded content can help during an outage, but new files and connected-source updates need connectivity. Test offline behavior with your own content; a cached image is not evidence that every source will keep working.

Narrow down the failing part.

If you need help, contact UrbanLoop with app versions, device model, the affected content type, error time and blocked hostname if available. Remove tokens, private URLs and account secrets from screenshots or logs before sharing.