Instructions for allowing traffic to Tidepool domains [IT]

Introduction

This information is intended to assist IT personnel and ensure that communication between your network and Tidepool is fully enabled and unhampered by firewalls or other settings. 

Firewall or network related issues can result in difficulty signing up or logging in, as well as a general lack of access to Tidepool while on the locked-down network. 

The ideal solution is to allow traffic to all of Tidepool's DNS entries.

 

1. Add the generic "*.tidepool.org" to the exception list

Your IT department will need to ensure that all URLs in the tidepool.org domain are accessible over HTTPS (port 443). 

The best way to do this is to add the generic " *.tidepool.org " to the exceptions list.

 

2. Add these specific domains to the exception list

If you are unable to except the generic domain, you can add exceptions for these Specific Domains: 

  • "app.tidepool.org"
  • "auth.tidepool.org"
  • "api.tidepool.org"
  • "upload.tidepool.org"
  • "www.tidepool.org"
  • "tidepool.org" 
  • "support.tidepool.org"
  • "downloads.tidepool.org"

Please note: Tidepool is hosted by AWS. Our IP and other addresses will change. For this reason, it is not ideal to try and add exclusions to the list by IP address.

 

3. Add all domains to the exceptions

If you wish to allow traffic to/from all domains for all Tidepool's sites:

 

Please reach out to support@tidepool.org if you have any questions or feedback on this article.

Image displaying the Tidepool logo