For users on a corporate network or using VPN for remote connections to the corporate network, HTTPS on port 443 must be open system-wide and a series of URLs must be whitelisted on the firewall. This ensures all users have a seamless experience when they install and use Syncplicity on their PC, Mac, mobile, and web clients.
NOTE: Whitelisting is only required if you are experiencing issues with connectivity.
Core Syncplicity Service
- my.syncplicity.com:443
- eu.syncplicity.com:443 NEW
- download.syncplicity.com:443
- xml.syncplicity.com:443
- xml.eu.syncplicity.com:443 NEW
- rms.syncplicity.com:443
- event.syncplicity.com:443
- event.eu.syncplicity.com:443 NEW
- gol.syncplicity.com:443 NEW
- *.syncplicity.com:443
Cloud Storage
The following cloud storage endpoints should be whitelisted for deployments that use cloud storage. For on-premise storage, the corresponding on-premise storage endpoint URLs should be accessible.
- data.syncplicity.com:443
- data-eu.syncplicity.com:443 NEW
- data-eu.eu.syncplicity.com:443 NEW
- data-us.eu.syncplicity.com:443 NEW
Data Analytics
Online file browser
- fonts.googleapis.com:443
- api.mixpanel.com:443
- ajax.googleapis.com:443
- ajax.aspnetcdn.com:443
API Platform
- api.syncplicity.com:443
- api.eu.syncplicity.com:443 NEW
Developer Portal
Instrumentation
- beacon-1.newrelic.com:443
- health.syncplicity.com:443 (Syncplicity server used for storage connector health checks)
Gravatar Service
If you prevent access to this URL, avatars will not display in the activity feed or mobile apps.
Support Pages
Configuring email servers for Syncplicity
- Whitelist 'syncplicity.com' domain on all email servers
WOPI
- wopi.gov.syncplicity.com:443
- wopi.syncplicity.com:443
- wopi-eu.eu.syncplicity.com:443
- wopi-eu.syncplicity.com:443
- wopi-us.eu.syncplicity.com:443
- bootstrapper.wopi.syncplicity.com:443
- oauth.syncplicity.com:443
- xml.syncplicity.com:443
- xml.eu.syncplicity.com:443
- gol.syncplicity.com:443
Metadata services
Discovery
Special Notes:
- It is STRONGLY recommended to use hostnames and URLs instead of IP addresses. This avoids the risk of a deprecated user experience due to an IP address changes.
- Newer hardware and secureOS have the ability to assign names to IPs with "object-groups." Due to older firewalls it may be difficult to use hostnames, in which case it is recommended to use a reverse proxy.
- To acquire the current Syncplicity Service IP addresses, perform an nslookup on Syncplicity services (such as, xml.syncplicity.com). Keep in mind, IPs can change with minimal warning.
- The full list of addresses are subject to change based upon Microsoft; therefore, they may all not be certified. For a reference see https://docs.microsoft.com/en-us/office365/enterprise/urls-and-ip-address-ranges#microsoft-365-common-and-office-online.