Syncplicity Support

Follow

Configuring firewall, proxy and email servers for Syncplicity

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 need to be whitelisted on the firewall. This ensures that all the users have a seamless experience when they install and use the Syncplicity on their PC, Mac, mobile, and web clients. This whitelisting is required only if you are seeing issues with the 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

Cloud Storage

The following cloud storage endpoints should be whitelisted for deployments using cloud storage. For on-premises storage, the corresponding on-premises 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

  • SSL.google-analytics.com:443

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

  • developer.syncplicity.com:443

Instrumentation

  • beacon-1.newrelic.com:443
  • lfov.net:443
  • health.syncplicity.com:443

Gravatar Service

Preventing access to this URL would prevent showing avatars in the activity feed and mobile apps.

  • secure.gravatar.com:443 

Support Pages

  • support.syncplicity.com:443
  • syncplicity.zendesk.com:443

Configuring email servers for Syncplicity

  • Whitelist ‘syncplicity.com’ domain on all email servers

Special Notes:

  • We STRONGLY recommend that you find a way to use hostnames and URLs instead of IP addresses. This avoids the risk of a deprecated user experience because of the change in IP addresses.
  • Newer hardware and secureOS have the ability to assign names to IPs via "object-groups."  We understand that with some older firewalls it is difficult to use hostnames, in which case we recommended using a reverse proxy.
  • You can get the current Syncplicity Service IP addresses by doing an nslookup on Syncplicity services (e.g. xml.syncplicity.com) but this comes with a risk that the IPs can change with very little warning.
Powered by Zendesk