GET STARTED

Why am I getting "HTTP Error 500.19 - Internal Server Error" after a fresh on-premise install/update to version 5.11.0+
Webinar: 7pace Timetracker FAQs
7pace Timetracker Reporting and API common errors and states. Why is my Reporting or API not working?
Why am I getting a message saying "Error calling DevOps API. Provided application token signature is not present or is invalid" in an on-prem deployment of Timetracker?
How does 7pace Timetracker use cookies and why should I enable them?
Cookie declaration
Why do I get a timeout expired error in Timetracker's Reporting API and how do I avoid it?
What IP range or ports should we white-list on our firewall to use 7pace Timetracker?
Remaining & Completed Work Questions
Why am I seeing work item form contribution errors when installing 7pace Timetracker?

See more

What IP range or ports should we white-list on our firewall to use 7pace Timetracker?

Leah Copeland

May 12, 2021 08:20
Updated

Question

Is there any specific IP range or ports that must be set up on our firewall for 7pace TimeTracker ?

Answer

Timetracker is using the following IP addresses right now:

40.114.210.78
13.89.172.5
13.71.123.138
13.70.72.34

The following domains should be also white-listed:
*.cdn.7pace.com
*.timehub.7pace.com/
timehub.7pace.com
timehub-prod.azureedge.net

Comments

0 comments

Please sign in to leave a comment.

Powered by Zendesk