For administrators
Configuration of users’ devices
- Read these recommendations if Olvid does not work.
Internet connectivity
Here’s how to ensure that your devices are freely connected to the Internet, without any specific network restrictions or third-party applications interfering with normal Olvid operation.
Interventions of third party applications
Applications that filter network connections (such as firewalls, VPN or Proxy configurations, Blokada, AdGuard…) may prevent Olvid from working properly.
Configuring or stopping them, or even uninstalling them, will confirm whether this solves the problem.
iPhone iPad
Apple Support
Android
Android Help
Manage advanced network settings on your Android phone.
For network administrators
Contact your network administrator or Internet service provider, providing them with the following information.
Servers required for mobile and desktop applications
- server.olvid.io, TCP:443 (HTTPS)
- REST API for sending and receiving messages.
- Cloudfront distribution on API Gateway, IPv4 only for now.
- olvid-attachment-chunks.s3.eu-west-3.amazonaws.com, TCP:443 (HTTPS)
- For storing message attachments.
- S3 Bucket with HTTP GET/POST requests.
- ws-server.olvid.io, TCP:443 (WebSocket in HTTPS)
- WebSocket for some notifications.
- Cloudfront distribution on API Gateway.
- transfer.olvid.io, TCP:443 (WebSocket in HTTPS)
- Relay server used to import a profile in order to use Olvid on a second device.
- Cloudfront distribution on API Gateway.
- turn-scaled.olvid.io, UDP:5349, TCP:443
- Used as a TURN server for Olvid calls.
- During a call, one (or more) other UDP port will be chosen on these servers and it will be necessary to be able to connect to it.
- Geolocated IP to 3 regions:
- ap.turn-scaled.olvid.io, eu.turn-scaled.olvid.io, us.turn-scaled.olvid.io
- Each region has an elastic load balancer with an internal AWS DNS.
- You can choose to set up your own TURN server(s) for audio and video calls, especially if particular network conditions prevent Olvid’s TURN servers from offering optimal quality of service. (This option is currently only available on Android).
- invitation.olvid.io, configuration.olvid.io, openid-redirect.olvid.io, TCP:443 (HTTPS)
- Used to add contacts remotely or to add contacts from your company’s directory.
- Various static web pages hosted in S3 buckets.
- map.olvid.io, TCP:443 (HTTPS)
- Used to share a location.
- Map server (OpenStreetMap style and tile files).
- You can choose to not use map service or to use another custom OpenStreetMap server.
- pelias.olvid.io, TCP:443 (HTTPS)
- Used for location sharing.
- Address search server.
- You can choose to disable address search or to use another custom address server.
Other servers
-
Apple and Google push notification servers for iOS and Android mobile apps.
-
No specific server for the desktop version. Notifications go through the WebSocket on ws-server.olvid.io.
-
iCloud and Google Drive servers for iOS and Android Olvid profiles backups.
- You can choose to configure your own WebDAV server for automatic backup of Olvid profiles. (This option is currently only available on Android).
- web.olvid.io, TCP:443 (HTTPS) for Olvid Web with an Android.
- Elastic load balancer with an internal AWS DNS.
- When sharing a link, a request to the site involved can be made to retrieve a preview.
Keycloak server hosted on premise
- server.olvid.io, TCP:443 (HTTPS)
- Cloudfront distribution on API Gateway, IPv4 only for now.
- REST API where only the https://server.olvid.io/keycloakQuery point is called, in POST.
Silent installation of Olvid for Windows
To silently install Olvid for Windows, run the command:
msiexec /i Olvid-2.2.0.msi INSTALLDIR="C:\Program Files\Olvid\" /passive /qn /norestart
Deploying and configuring Olvid via an MDM
Like any app in the stores, Olvid can be deployed and configured via an MDM (a mobile device management app).
