Tulip is designed to have minimal IT requirements. The most simple description is: If you can access the web, you can access Tulip. The rest of this article is meant for individuals with a background in Information Technology (IT) and addresses the specific firewall settings required to access Tulip.
- The Tulip admin interface (https://your-account.tulip.co) can be accessed from your web browser just like any other website. The admin interface currently only supports the Google Chrome browser and requires HTTPS over port 443.
- The Tulip Player for Mac and Windows must make outgoing requests to https://your-account.tulip.co using TCP on port 443 to run Apps.
- Photos and videos are loaded with outgoing requests using TCP on port 443 to https://s3.amazonaws.com/co.tulip.factory/.
- The Tulip Player app does support HTTP proxies.
- Updates to the Tulip Player are pulled automatically from https://download.tulip.co and https://s3.amazonaws.com/co.tulip.cdn/.
Tulip Gateway - Normal Operation
- The Gateway must make outgoing requests to https://your-account.tulip.co using TCP on port 443.
- The Gateway must resolve https://your-account.tulip.co with a DNS. This is usually done using TCP on port 53, but may be done through a proxy.
- The Gateway must make outgoing requests to a variety of NTP time servers using UDP on port 123 in order to synchronize its clock.
- The Tulip Gateway does support HTTP proxies and custom SSL certificates.
Tulip Gateway - Over-the-air Updates
- The Gateway must make outgoing requests to https://firmware.tulip.co using TCP on port 443 to connect to our device management server.
- The Gateway must make outgoing requests to https://s3.amazonaws.com/co.tulip.mender-artifact-storage/ using TCP on port 443 to download new updates.
Tulip Connector Host
- In order for a Cloud Connector Host to connect to an external system, incoming connections will need to be allowed from Tulip. Please contact us for specific IP ranges to whitelist.
- If you will be running a Connector Host on-site, please refer to our Connector Host Requirements article.