---
title: "Firewall Configuration"
slug: "firewall-white-list"
description: "This article outlines firewall configuration for ScreenMeet. "
updated: 2025-11-21T18:05:53Z
published: 2025-11-21T18:05:53Z
canonical: "docs.screenmeet.com/firewall-white-list"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.screenmeet.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Firewall configuration / whitelisting

## ScreenMeet Network Whitelisting (Firewall and Proxy)

### Introduction

This article lists the ports, hostnames, and static IP addresses that must be allowed through your firewall or proxy to ensure reliable ScreenMeet connectivity. It is intended for network and security administrators.

### When to Whitelist

Whitelist the entries below if ScreenMeet sessions fail to start, agents cannot connect, or your network blocks outbound traffic to ScreenMeet services.

For inbound API allowlisting into your CRM, refer to the ScreenMeet egress IP list: [Egress IP list](/v1/docs/salesforce-ip-ranges).

Dynamic IP Notice

ScreenMeet uses both static and dynamic infrastructure. Only static IPs are listed here. You may occasionally see additional IPs in your logs; these are expected and may change over time.

To avoid future connection issues, prioritise hostname-based allowlisting where possible.

### Required Ports and Hostnames

Allow outbound traffic to the following hostnames over the listed ports.

| **Port** | **Protocol** | **Hostname** |
| --- | --- | --- |
| 443 | UDP | `*.screenmeet.com` |
| 443 | TCP | `*.screenmeet.com` |

### Static IP Addresses

If your security policy requires IP-based allowlisting, add the following static ScreenMeet IPs.

| **IP** | **Region** |
| --- | --- |
| 13.248.175.59 | ca-central-1 |
| 3.33.180.41 | ca-central-1 |
| 15.197.157.44 | eu-north-1 |
| 35.71.167.48 | eu-north-1 |
| 75.2.16.11 | eu-south-2 |
| 35.71.147.51 | eu-south-2 |
| 15.197.171.20 | me-central-1 |
| 3.33.138.39 | me-central-1 |
| 13.248.173.33 | us-west-2 |
| 76.223.44.10 | us-west-2 |
| 13.248.157.15 | us-east-2 |
| 76.223.24.3 | us-east-2 |
| 13.248.182.10 | eu-west-1 |
| 76.223.49.44 | eu-west-1 |
| 13.248.193.55 | ap-east-1 |
| 76.223.1.26 | ap-east-1 |
| 13.248.164.27 | ap-northeast-2 |
| 76.223.61.40 | ap-northeast-2 |
| 75.2.104.21 | ap-northeast-1 |
| 99.83.194.6 | ap-northeast-1 |
| 75.2.88.60 | ap-southeast-1 |
| 99.83.179.35 | ap-southeast-1 |
| 75.2.99.59 | ap-southeast-2 |
| 99.83.162.42 | ap-southeast-2 |
| 75.2.95.59 | ap-south-1 |
| 99.83.171.51 | ap-south-1 |
| 75.2.88.11 | eu-central-1 |
| 99.83.157.5 | eu-central-1 |
| 75.2.122.59 | sa-east-1 |
| 99.83.161.30 | sa-east-1 |
| 13.248.160.23 | us-east-1 |
| 76.223.33.31 | us-east-1 |
| 15.197.215.28 | multi (proxy) |
| 3.33.194.1 | multi (proxy) |

### Notes and Best Practices

- Prefer allowlisting `*.screenmeet.com` over IP-based rules to avoid disruption from dynamic infrastructure.
- Ensure both TCP and UDP on port 443 are permitted for optimal performance.
- If you use SSL inspection, add ScreenMeet domains to your inspection bypass list.

### Conclusion

After applying these firewall and proxy rules, ScreenMeet traffic should flow normally. If connectivity issues continue, verify that your network is not blocking dynamic endpoints and contact ScreenMeet support with relevant timestamps and firewall logs.