Feeds connects Zoom meeting participants into OBS as individual video sources. On most networks it works with no configuration. On managed or restricted networks (common in libraries, schools, and corporate environments) a firewall or content filter may block the connections Feeds needs, causing login to fail or a paid plan to appear as Free.

If you’re seeing a “couldn’t reach the login server” or “couldn’t reach the licensing server” message, this page has everything your IT team needs to allow Feeds through.

What to allow

All connections are outbound HTTPS on port 443. Feeds does not require any inbound connections or open ports.

Required: Feeds will not log in or activate paid plans without these:

Also required for joining meetings: Feeds uses the official Zoom Meeting SDK to connect to meetings, which needs Zoom’s own network access (meeting media travels over Zoom’s infrastructure, not a single domain). Please also allow Zoom’s published network requirements: https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0060548

Optional: For live-chat and update features. Feeds works without these, they just won’t function if blocked:

A note on the licensing domain

The Feeds login and licensing service runs on Cloudflare Workers, at feeds-entitlement.square-dust-0e00.workers.dev. Some content filters block the workers.dev domain by category. If your filter allows exceptions by hostname, allowing that specific address resolves it. Feeds is a signed application from Let’s Do Video, distributed through the official Zoom App Marketplace.

Still stuck?

If Feeds still can’t connect after allowing the domains above, email me directly at David@LetsDoVideo.com and I’ll help you sort it out. Please include the OBS log file if you can (in OBS: Help → Log Files → Show Log Files).