FAQ

For network administrators

Mobile or desktop applications

Servers required for operation

  • server.olvid.io, TCP:443 (HTTPS)
    • Cloudfront distribution on API Gateway, IPv4 only for now.
    • REST API for sending and receiving messages.
  • olvid-attachment-chunks.s3.eu-west-3.amazonaws.com, TCP:443 (HTTPS)
    • S3 Bucket with HTTP GET/POST requests.
    • For storing message attachments.
  • ws-server.olvid.io, TCP:443 (WebSocket en HTTPS)
    • Cloudfront distribution on API Gateway, IPv4 only for now.
    • WebSocket for some notifications.
  • turn-scaled.olvid.io, UDP:5349, TCP:443
    • 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.
    • 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.
  • invitation.olvid.io, configuration.olvid.io, openid-redirect.olvid.io, TCP:443 (HTTPS)
    • Various static web pages hosted in S3 buckets.

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.
  • web.olvid.io, TCP:443 (HTTPS)
    • Elastic load balancer with an internal AWS DNS.
    • Olvid Web client for Android.
  • 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.

Configurations of users’ devices

Related articles