...
...
Anchor | ||||
---|---|---|---|---|
|
Question
I'm using DevOps Server over HTTPS and am experiencing loading issues.
...
In the browser console (F12), I receive the following error when I try to try to open the Timetracker address directly in my browser: "7pace.TimetrackerOnPremises.TimeMonthly:1 Mixed Content: The page at <_____> was loaded over HTTPS, but requested an insecure resource 'http://timetracker_url_'. This request has been blocked; the content must be served over HTTPS."
Answer
You are using DevOps Server over HTTPS, therefore, 7pace Timetracker needs to be configured over HTTPS as well. This is because Timetracker (and any other extension for DevOps Server) is located in the iframe, and browsers prevent HTTPS iframes from loading on pages with HTTPS.
Please go to the Timetracker Configuration Tool and change it so that the DevOps URL is the same for your end-users (it looks like this: https://TFS_URL/tfs/). After that, you should be asked to configure HTTPS binding for Timetracker and to select the SSL certificate.
...
If Timetracker runs properly, it should display an empty page with the following text: "Welcome to 7pace Timetracker".
Common issues:
Port is blocked by firewall
The Certificate is not trusted and the browser revokes connection
The address is not reachable from your PC
Anchor | ||||
---|---|---|---|---|
|
Question
I'm seeing "Timetracker is taking longer than expected to load" messages. I looked in our browser's Dev console and see multiple errors about DOM elements. Can you help?
Answer
This can occur if your browser has some extensions or security settings that prevents the Referer header from being passed to iFrames. 7paceTimetracker relies on this header and expects that it is present when you open a page. Please Please check your browser settings and see if something is blocking this header (it can be settings in browser, ad-blocking extension or any script blocking extensions).
Anchor | ||||
---|---|---|---|---|
|
...