Configure Network Access

While many users enjoy hassle-free access to Appetize without any network adjustments, certain corporate security protocols may restrict connections.

For most users there is no need for any network configuration to be able to use Appetize. However, some company's security policies might restrict network access.

Streaming Server Access

To make sure you can access our streaming servers from behind a firewall:

• Identify your deployment type: Public Cloud or Enterprise Private Cloud Instance.

• Find the IP Blocks used by our streaming servers:

  • For Public Cloud Instances, visit https://appetize.io/ip-blocks.

  • For Enterprise Private Cloud Instances, visit https://custom.appetize.io/ip-blocks, replacing 'custom' with your assigned domain.

• Make sure that your network configuration doesn't restrict connectivity to all of the listed IPs.

Web Server Access

To make sure you can access our web servers from behind a firewall:

• Identify your deployment type: Public Cloud or Enterprise Private Cloud Instance.

• Find your assigned domain name:

  • For Public Cloud Instances, this will be appetize.io.

  • For Enterprise Private Cloud Instances, this will be custom.appetize.io replacing 'custom' with your assigned domain.

• Ensure all outgoing connections to your domain e.g. appetize.io have been whitelisted.

For our Enterprise Private Cloud Instances, you can also configure which IPs have access to your private instances. Contact us to learn more.

Web Socket Access

Our system relies on WebSockets to communicate with our streaming servers. However, corporate web proxies may block WebSocket connections, preventing you to successfully make use of our service. To ensure proper setup, you can verify your connection using websites like https://websocketstest.com/.