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 |
| HTTPS, WSS | Live replies (EU region) |
| HTTPS, WSS | Live replies |
| HTTPS, WSS | Live replies |
| HTTPS, WSS | Live replies (includes |
| HTTPS, WSS | Live replies |
Sign-in and Messenger (HTTPS)
Host | Protocol | Used for |
| HTTPS | digipara licensing service (sign-in, unread count) |
| HTTPS | Loads the Messenger |
| HTTPS | Messenger scripts, fonts, images |
| HTTPS | Messenger fonts |
| HTTPS | Messenger service (EU region) |
| HTTPS | Messenger service |
| HTTPS | Messenger API (EU region) |
| HTTPS | Messenger API |
| HTTPS | Messenger code |
| HTTPS | Messenger API |
| HTTPS | Connection check |
| HTTPS | Messenger add-ons (EU region) |
| HTTPS | Messenger add-ons |
| HTTPS | Forms in the Messenger |
Help articles (HTTPS)
Host | Protocol | Used for |
| HTTPS | digipara help articles |
| HTTPS | Help articles (EU region) |
| HTTPS | Help articles |
Files, images, and attachments (HTTPS)
Host | Protocol | Used for |
| HTTPS | Sending screenshots and files to support (EU region) |
| HTTPS | Sending screenshots and files to support (EU region) |
| HTTPS | Sending screenshots and files to support |
| HTTPS | Files in conversations |
| HTTPS | Images and media in messages and articles (EU region) |
| HTTPS | Images and media in messages and articles |
| HTTPS | Messenger images (EU region) |
| HTTPS | Messenger images |
| HTTPS | Attachments sent by support (EU region) |
| HTTPS | Attachments (nine domains, allow each one) |
| HTTPS | GIFs in conversations |
| HTTPS | Video messages in conversations |
| 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 |
| HTTPS | Embedded videos |
| HTTPS | Video thumbnails |
| HTTPS | Video channel images |
| 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.
