Domains, Protocols and Ports required for Loom to work on your servers

If you're recording on a protected network, there can be firewalls/proxies blocking Loom. This can block your ability to record successfully. 

Issue symptoms

  • Repeated failed recordings (video ending prematurely, can't start a recording, etc...).
  • Loom application displays as a blank box.
  • Abrupt recording endings - due to 1006 websocket error. 
  • Recording error from Chrome.

Here's how to fix this:

Allow the below Domains and Ports in your firewall. 

When whitelisting access for Loom, it's best to whitelist all addresses listed under "Domains" in order to ensure future services we add behind a new subdomain don't get blocked. In the case you're decrypting SSL traffic and are having issues, please turn off decryption to non-URL SSL traffic on your network. 

Please whitelist:

  • *.loom.com 
  • icanhazip.com
  • api.ipify.org
  • cdn.segment.com
  • api.segment.io
  • *.intercom.io
  • *.s3.us-west-2.amazonaws.com
  • *.logs.datadoghq.com

These are the whitelist specifications:

Domains

  • www.loom.com
  • record.loom.com
  • cdn.loom.com

Protocols

  • wss
  • https

Ports

  • 80
  • 443

To do this, you may need to contact your network administrator to configure your firewall and allow the above.

For additional information on our security infrastructure, read our Loom Security White Paper

 Questions, comments, concerns? Contact us here.   

Happy recording! 🎥 😄

2 out of 2 found this helpful