Skip to main content

Network Requirements for the digipara Assistant

System requirements and all HTTPS and WSS hosts your firewall or proxy must allow so the digipara Assistant works in Liftdesigner.

Written by Sabine Bunese

The digipara Assistant in Liftdesigner runs on the Intercom Messenger. To work behind a company firewall or proxy, the computer running Liftdesigner must reach all hosts below over HTTPS (port 443). The realtime hosts also need WSS (secure WebSocket, port 443).

If a host is blocked, the panel can't connect, and messages, attachments, or images don't load.

System requirements

  • Liftdesigner 2027. The digipara Assistant is part of the application. There is no separate installation.

  • An activated Liftdesigner license.

  • Microsoft Edge WebView2 Runtime (Evergreen). It is preinstalled on current Windows 10 and 11. If it is missing, the digipara Assistant tells you and links to Microsoft's download page.

  • Outbound HTTPS (TCP 443) to the hosts below, including WebSocket (WSS) connections for live replies.

Why allowing *.intercom.io is not enough

The Messenger doesn't run on one domain. It loads its code, fonts, images, uploaded files, and the live chat connection from several separate domains.

A wildcard like *.intercom.io only matches subdomains of intercom.io. It does not match these other domains. If only *.intercom.io is allowed:

  • the Assistant can't sign in, can't connect, or doesn't show new replies

  • images, GIFs, and file attachments don't load or can't be uploaded

Hosts to allow

Add every host in the tables to your firewall or proxy allowlist. A * stands for any subdomain.

Realtime chat connection (HTTPS and WSS)

Host

Protocol

Used for

nexus-europe-websocket.intercom.io

HTTPS, WSS

Live replies (EU region)

nexus-websocket-a.intercom.io

HTTPS, WSS

Live replies

nexus-websocket-b.intercom.io

HTTPS, WSS

Live replies

*.intercom-chat.com

HTTPS, WSS

Live replies (includes nexus-websocket-a.intercom-chat.com)

*.intercom-messenger.com

HTTPS, WSS

Live replies

Sign-in and Messenger (HTTPS)

Host

Protocol

Used for

activation.digipara.com

HTTPS

digipara licensing service (sign-in, unread count)

widget.intercom.io

HTTPS

Loads the Messenger

js.intercomcdn.com

HTTPS

Messenger scripts, fonts, images

fonts.intercomcdn.com

HTTPS

Messenger fonts

api-iam.eu.intercom.io

HTTPS

Messenger service (EU region)

api-iam.intercom.io

HTTPS

Messenger service

api.eu.intercom.io

HTTPS

Messenger API (EU region)

api.intercom.io

HTTPS

Messenger API

app.intercom.io

HTTPS

Messenger code

via.intercom.io

HTTPS

Messenger API

api-ping.intercom.io

HTTPS

Connection check

messenger-apps.eu.intercom.io

HTTPS

Messenger add-ons (EU region)

messenger-apps.intercom.io

HTTPS

Messenger add-ons

intercom-sheets.com

HTTPS

Forms in the Messenger

Help articles (HTTPS)

Host

Protocol

Used for

help.digipara.com

HTTPS

digipara help articles

intercom-help.eu

HTTPS

Help articles (EU region)

intercom.help

HTTPS

Help articles

Files, images, and attachments (HTTPS)

Host

Protocol

Used for

uploads.intercomcdn.eu

HTTPS

Sending screenshots and files to support (EU region)

uploads.eu.intercomcdn.com

HTTPS

Sending screenshots and files to support (EU region)

uploads.intercomcdn.com

HTTPS

Sending screenshots and files to support

uploads.intercomusercontent.com

HTTPS

Files in conversations

downloads.intercomcdn.eu

HTTPS

Images and media in messages and articles (EU region)

downloads.intercomcdn.com

HTTPS

Images and media in messages and articles

static.intercomassets.eu

HTTPS

Messenger images (EU region)

static.intercomassets.com

HTTPS

Messenger images

*.intercom-attachments.eu

HTTPS

Attachments sent by support (EU region)

*.intercom-attachments-1.com to *.intercom-attachments-9.com

HTTPS

Attachments (nine domains, allow each one)

gifs.intercomcdn.com

HTTPS

GIFs in conversations

video-messages.intercomcdn.com

HTTPS

Video messages in conversations

www.intercom-reporting.com

HTTPS

Embedded Messenger content

Videos in help articles (HTTPS, optional)

Only needed if users should see embedded YouTube videos in help articles inside the digipara Assistant.

Host

Protocol

Used for

www.youtube.com

HTTPS

Embedded videos

i.ytimg.com

HTTPS

Video thumbnails

yt3.ggpht.com

HTTPS

Video channel images

www.gstatic.com

HTTPS

Video player resources

Proxy and TLS inspection

  • Proxy settings: Liftdesigner uses the Windows system proxy settings.

  • TLS inspection: If your proxy inspects HTTPS traffic, it must let WebSocket connections through. Otherwise help articles still work, but replies from support don't arrive while Liftdesigner is open. The digipara Assistant shows this as a limited connection.

Did this answer your question?