Skip to main content

Allowing We Are through your company firewall

The two domains your IT team needs to allow so We Are works through your firewall, web filter or proxy.

If your organisation uses a firewall, web filter or proxy, it may block We Are until your IT team allows it. In most cases, allowing two domains is all it takes for learners to play Stories and for creators to use Studio from your company network.

Let me show you what to ask your IT team for.

What to allow

Ask your IT team to allow these two domains, including all their subdomains:

  • *.wearelearning.com

  • *.wearelearning.io

That's all most organisations need. These two domains cover the Player, Studio, sign-in, our API and all Story content. All traffic is encrypted HTTPS on port 443.

🦸🏽‍♀️ Pro tip: You don't need to allow individual addresses such as play.wearelearning.com or api.wearelearning.io one by one. The two domains above already include them, and any new ones we add later.

Why we can't give you an IP address

We Are runs on global cloud networks whose IP addresses are shared and change without notice. An IP allowlist would stop working, so please allow the domains above instead. Most firewalls, web filters and proxies support this.

Only if your network blocks everything that isn't approved

Some organisations block every address that isn't on an approved list. Only in that case, your IT team also needs to allow these outside services that We Are uses:

Needed for

Addresses

Images and fonts in Stories and Studio

res.cloudinary.com, fonts.googleapis.com, fonts.gstatic.com

Video in Stories, only if your Stories use YouTube, Vimeo or Wistia

*.youtube.com, *.ytimg.com, *.youtube-nocookie.com, *.vimeo.com, *.vimeocdn.com, *.wistia.com, *.wistia.net

Support chat in Studio

*.intercom.io, *.intercomcdn.com, *.intercomcdn.eu, *.intercomassets.eu, *.intercom-messenger.com

Billing in Studio

js.stripe.com

Stock images in Studio

images.unsplash.com

Product analytics in Studio

*.posthog.com

Studio also keeps a live connection to api.wearelearning.io using secure WebSockets, so make sure WebSockets are allowed for that domain.

If you track Stories in your LMS

With SCORM, your LMS opens the Story from play.wearelearning.com, so the two domains above are all you need.

With xAPI or cmi5, our servers send the learner's progress to your LMS over the internet, so your LMS must be reachable from the internet. If it only accepts requests from known IP addresses, contact us before you set it up.

Checking that it works

Once your IT team has allowed the domains, test it from a computer on your company network:

1) Open a published Story from its Story link. The 3D scene should load and the Story should play with sound.

2) If you build Stories, sign in to Studio and open a Story in the nodemap.

3) If you use an LMS, start the same Story from the LMS as a test learner.

Troubleshooting

The Story still doesn't load

Ask your IT team to open a Story while they watch their firewall or web filter logs, and to send us any blocked addresses. We'll tell you whether they belong to We Are.

The Story starts loading but never finishes

The Player downloads large 3D files, and some proxies that scan or rewrite downloads can break them. Ask your IT team to exclude *.wearelearning.com and *.wearelearning.io from download scanning and HTTPS inspection.

You see "Your browser must have WebGL enabled"

This isn't a network block. The browser can't show 3D content on this computer. See Enable WebGL.

Still stuck? Reach out via the chat and include a screenshot of the error, your browser, and whether you're playing a Story or using Studio.

Related Articles

Did this answer your question?