Skip to main content
tiCrypt 2.17.15

URL Inbox Configuration

ticrypt-mailbox serves the single-page application that outside senders open when a user shares a URL inbox link. It runs outside the external firewall on its own Nginx virtual host, with a one-way path to ticrypt-rest and no route to the internal network. Install and serve it first; this page covers the one setting that connects it to tiCrypt.

tiCrypt needs to know the address the application is served from, because that address is what gets embedded in every link a user shares.

Set the inbox URL​

The tiCrypt frontend reads the inbox URL from the configuration supplied by tiCrypt Connect. There are two places to set it, and the frontend is the one to use.

  1. From the tab, select System Settings.
  2. Edit the Inbox Settings card.
  3. Enter the full URL of the application, including the page it is served as.
  4. Set the priority to Override.

Override means this value takes precedence over the value in the deployment file. Setting it in the deployment file instead is possible but is not recommended, because it takes a redeployment to change.

For example, an application served at https://mailbox.example.com/inbox.html is entered exactly that way, not as the bare host.

The URL must be reachable from outside

Senders open this address on their own machines, with no connection to your network. A value that resolves only on the institution's internal network produces links that no external sender can open.

Restart Nginx and test​

systemctl restart nginx

Open the URL you configured, for example https://mailbox.example.com/inbox.html, in a browser. A working deployment shows the uploader page. Confirm end to end by creating an inbox in the frontend, opening a URL access point, and following the generated link, which is documented in Inboxes.