Skip to main content
All CollectionsSetup and Account Management
Jolt Platform Allow-List Information
Jolt Platform Allow-List Information

Whitelisting, allow listing, firewall exceptions

Curtis Nash avatar
Written by Curtis Nash
Updated over 2 months ago

Jolt Platform Allow-List Information

To ensure seamless communication between the Jolt platform, its app, and hardware within your network environment, you need to configure your firewall to allow necessary connections. This process involves whitelisting specific ports and addresses.

Here's a comprehensive guide to the ports and domains you need to whitelist for Jolt to function correctly:

Allow-list Requirements

1. Website Access:

  • Domain: *.joltup.com

  • TCP Ports: 80 (HTTP), 443 (HTTPS)

2. Mobile App Access:

  • Domains:

    • *.jolt.com (TCP Ports: 80, 443)

    • *.joltup.com (TCP Ports: 80, 443)

    • *.googleapis.com (TCP Ports: 80, 443)

    • *.amazonaws.com (TCP Ports: 80, 443)

    • codepush.appcenter.ms (TCP Ports: 80, 443)

    • codepush.blob.core.windows.net (TCP Ports: 80, 443)

    • codepushupdates.azureedge.net (TCP Ports: 80, 443)

    • forecast.weather.gov (TCP Ports: 80, 443)

3. Sensor Connectivity:

  • Domains:

    • *.jolt.com (WebSockets Ports: 80/443; UDP Ports: 1700)

    • *.google.com (NTP Port: 123)

    • *.devicehq.com (TCP Ports: 5798, 5799)

4. Label Printing:

  • TCP Port: 6101 (Used for configuration and print commands)

  • UDP Port: 4201 (Used for printer discovery)

  • SFTP Port: 22 (Used for firmware update server endpoint)

Next Steps

  1. Contact Your Network Administrator: If you’re unsure how to configure these settings, please reach out to your network management provider for assistance.

  2. Verify Configuration: After whitelisting these addresses and ports, ensure that your Jolt app and hardware are communicating properly with our servers.

Additional Resources

  • How to Whitelist Ports in Your Firewall

  • Troubleshooting Network Connectivity Issues

For further assistance, please refer to the support resources provided or contact our support team directly.

Did this answer your question?