In order to ensure full functionality or Orlo, you will need to ensure that the domains we use are not blocked by your network admin.
Below is a full list of domains which will require access in order for Orlo to work fully, please grant access to the following domains:
Orlo general functionality:
www.orlo.app
app.socialsignin.co.uk and api.orlo.app *
ws.socialsignin.net and ws.orlo.app *
( * - the socialsignin domains are deprecated and we will migrate to the orlo.app variants eventually)
Content Library / File Uploads
cdn.uploads.orlo.app
cloud.uploads.orlo.app
static.uploads.orlo.app
upload.uploads.orlo.app
*.amazonaws.com (or alternatively socialsignin-file-library.s3-eu-west-1.amazonaws.com and filestack-uploads-persist-production.s3.amazonaws.com)
Live Chat
*.firebaseio.com (websockets)
live-chat-cdn.orlo.app
europe-west1-production-orlo-live-chat-uk.cloudfunctions.net
live-chat-assets.socialsignin.net
securetoken.googleapis.com
www.googleapis.com
firestore.googleapis.com
production-orlo-live-chat-uk.firebaseapp.com
live-chat-cdn.socialsignin.net
Google API’s, for UX and functionality:
*.firebaseio.com
googleapis.com
firestore.googleapis.com
Photo Editor:
api.photoeditorsdk.com
Amazon Web Services:
amazonnaws.com
filebox-bc764e08f3d5.s3.eu-west-1.amazonaws.com
website-app.s3.amazonaws.com
S3.amazonaws.com (file uploads)
cloudfront.net
images.socialsignin.net (linkedin image post hosting)
Social networks - additionally, users probably want to whitelist
(These will probably be already whitelisted in order to use Twitter or Facebook natively).
pbs.twimg.com (images imported from twitter)
*.fbcdn.net (images from imported facebook posts)
Non core functionality
We can support you better if you also enable these :
cdn.pendo.io - used for some display of informational messages within the app.
app.pendo.io
logs-01.loggly.com - used for logging diagnostics/errors
capture.trackjs.com - used for logging diagnostics/errors