If your Tulip IoT Gateway is not working as you would expect, use this short guide to troubleshoot some of the most common issues.

1- Confirm that the Gateway’s power and ethernet cables are plugged in.

Ensure that you are using a 24V power supply and that the connection is secure. A multimeter can be used to confirm the voltage output of your power supply. If the lights above the power connection are not lit, your Gateway may need to be replaced.

An ethernet cable should securely connect the ethernet port on your Gateway to an ethernet port on a network switch or router that is connected to the internet. This internet connection is necessary for your IoT Gateway to connect to the Tulip platform.

2- Verify that your Gateway has a "heartbeat"

A Gateway that is properly supplied with power will have a green blinking light on the ethernet side of the Gateway.

3- Check to see if the Gateway is online in Shop Floor

Next, verify that your Gateway appears online in the Shop Floor tab of your Tulip account.

If a Gateway is online, it will have a green 

icon, and a listed uptime in the sidebar


If the Gateway has a red 

icon, it isn’t successfully connecting to the Tulip platform. Verify that the ethernet connection supplied to the Gateway has a functional network connection. 

A Gateway not appearing "online" in the Shop Floor is usually the result of a local network interruption

Ensure that the ethernet cable connected to the gateway has an active network connection. You can do this by plugging it into a laptop computer, turning off WiFi, opening up a browser and visiting a website such as tulip.co

If the network is not active, then it is an IT issue that needs to be resolved locally. 

4- Restart the Gateway

If your Gateway has an adequate power supply and access to a network, a power cycle can help restore functionality. 

Remove the power connection to the Gateway, wait 20 seconds, and then restore power to the Gateway. Allow up to 5 minutes for the Gateway to appear as "online" in the Shop Floor.

5- Ports & Whitelisting

It is possible that your IT has blocked ports or created a whitelist that prevents the Tulip Gateway from connecting out. 

The gateway needs to be able to connect to the internet over TCP ports 53, 80, 123, and 443.

To check if this is the case, log into the Gateway Portal. To do this:

1- Open your Wi-Fi network settings and select the gateway’s local Wi-Fi network. Ex Network Name: 'Tulip-GTW-03-E60240E3'

  • The name of the network will be the device serial number - which can also be found on the physical gateway near the clip.
  • The password is tulip-gw

2. Relaunch Chrome. Navigate to http://10.0.3.1. It will route you to the Gateway Portal.

Having Trouble? Be sure you are using http://10.0.3.1 and NOT https://10.0.3.1.

3. Click the "View log files" link in the menu on the left of the screen.

4. Click the "Diagnostics" tab in the following screen.

5. Select the "Network Health" dropdown on the Diagnostics page.

6. Review the resulting diagnostics to see if your network is blocking ports 53, 80 or 443. In the example below, port 443 is being blocked.

If this is the case, you will need to work with your IT department to unblock the port or whitelist the device.

6- Contact support via live chat

If your Gateway is still not performing as expected, it is time to contact Tulip Support for more detailed help. A Tulip team member can help you diagnose a variety of other issues such as restrictive firewall configurations or misconfigured devices.

A Tulip team member will need a few details about your IoT Gateway. To obtain them, go to the Diagnostics tab as instructed in the step above. Then, use the "All" filter, and click "Copy to Clipboard" in the top right of the page. Send that with any support request. 

You can access Tulip Support by clicking on the "Support Request" option under the Help icon in the menu bar of your Tulip account.

Did this answer your question?