MURAL is an HTML5 web application that works in your browser. If you are having trouble connecting to MURAL see the steps below for potential solutions.

Contents


Use the right browser

MURAL works best in Google Chrome (v51 and above), Firefox (v46 and above), and the most recent version of Microsoft Edge.


MURAL's performance and responsiveness may be lessened if using other browsers. For more information on browsers see our technical requirements article.

ˆ*Note: MURAL is not available on Internet Explorer.


Make sure WebSockets are enabled

If you get a constant reconnecting message, check this link to see if WebSockets are enabled for you.

MURAL needs to have a connection between our real-time servers and our users' apps and browsers in order for real-time collaboration to work. To do this we use the WebSockets protocol.


If your WebSockets are not enabled, please reach out to your IT team. They can follow these instructions to allow your team to use MURAL:

  1. Allow WebSockets and secure WebSockets (on .mural.co).

  2. Don't manipulate headers or user agents internally on IDS/IPS.

  3. Don't filter protocol update answers.


Allowlist MURAL IP addresses

If you cannot access MURAL at all, ask your IT team to allowlist these IP addresses:

Domain

IP addresses

Purpose

app.mural.co

20.42.34.181

23.100.43.226

Our main app URL and how integrations are experienced.

realtime.mural.co

20.42.34.181

23.100.43.226

Allows multiple people to experience the same mural in real time over WSS.

image.mural.co

20.42.34.181

23.100.43.226

Proxy that provides resized images based on user viewpoint and required level of detail.

notifier.mural.co

20.42.34.181

23.100.43.226

Allows integrations that use notifications to function.

enterprise.mural.co

20.185.98.242

23.100.41.136

Reserved for private tenant and BYOK customers. Not needed if a client is not in a private tenant or BYOK configuration.

murally.blob.core.windows.net

N/A

MURAL is hosted on Microsoft Azure. We use blob storage to display images uploaded to murals.

Using a proxy with MURAL

Proxying is not supported by the MURAL application. If your organization uses a web proxy, we recommend that you add a bypass for the following MURAL domains for the intended product experience:

Domain

Port

Protocol

app.mural.co

443

HTTPS / TLS 1.2

realtime.mural.co

443

WSS / TLS 1.2

enterprise.mural.co

443

HTTPS / TLS 1.2

image.mural.co

443

HTTPS / TLS 1.2

notifier.mural.co

443

HTTPS / TLS 1.2

murally.blob.core.windows.net

443

HTTPS / TLS 1.2

Now, you can collaborate more efficiently than ever!

Did this answer your question?