Elvis contains numerous features for collaborating with users who access Elvis remotely, such as:
- Sending an e-mail link to view assets in Elvis
- Sending an e-mail link to upload assets to Elvis.
- Accessing Elvis Server remotely through the Server client
- Integrating other web applications through the Elvis API
This typically involves accessing Elvis Server through the Internet. Connecting to Elvis Server remotely is done using standard HTTP (port 80) or HTTPS communication.
Using the external domain everywhere
When the Pro client sends out an e-mail link, the URL of that link is based on the Elvis Server URL through which the Pro client connects to Elvis.
However, remote users cannot connect to Elvis through that link because the IP address is only available on the local company network.
See the following diagram:
To resolve this, the internal Pro clients need to connect to Elvis Server in the same way as it would access it from remote locations.
This can be done by using a domain name linked to the external IP address of Elvis Server. The DNS server on your local company network can redirect any local clients to the internal IP address of the Elvis server.
Another option is to configure an explicit external server URL for e-mail links that are composed in the Pro client.
When Elvis Server has a different external and internal address or domain, this setting will force the server URL used in e-mail links, even when the initiating Pro client is connected to an internal address.
Note: In most cases it is preferred to use a proper DNS setup so that the internal and external domain of Elvis Server are the same.
- 9 May 2019: Re-written the article in places.
- 9 May 2019: Replaced all references of the 'AIR client' with 'Pro client'.