Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| faq:faq_desktop_firewall_proxy [2025/07/28 12:44] – external edit 127.0.0.1 | faq:faq_desktop_firewall_proxy [2026/03/23 15:19] (current) – chad | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Can I run the desktop behind a Firewall? ====== | ====== Can I run the desktop behind a Firewall? ====== | ||
| - | |||
| We have the following IP address ranges: | We have the following IP address ranges: | ||
| + | * '' | ||
| + | * '' | ||
| + | * '' | ||
| - | | + | All application traffic uses port 443. The following domain names must also be permitted through your firewall: |
| - | * CenturyLink | + | * '' |
| + | * '' | ||
| + | * '' | ||
| - | Our applications use port 80 & 443 on any of those IP’s. From a domain name perspective then you need *.t4login.com, | ||
| - | |||
| - | If your proxy requires authentication then you will need to allow T4 to bypass it as the Microsoft .Net Framework we use doesn’t support authenticating proxy servers. If your proxy doesn’t require authentication then T4 should work fine, but if it doesn’t then the simplest solution would be to bypass the proxy if that is possible. | ||
| ==== Running Behind a Proxy Server ==== | ==== Running Behind a Proxy Server ==== | ||
| - | The T4 Desktop application supports proxy configuration using the following environment variable: | + | The T4 Desktop application supports |
| + | If your proxy does not require authentication, | ||
| + | |||
| + | Proxy configuration is supported via the following environment variable: | ||
| < | < | ||
| - | |||
| - | ===== PING ===== | ||
| - | |||
| - | |||
| - | We don’t enable ping or tracert across our entire system. You can ping 64.74.232.69. It is a device on the edge of our network. | ||
| - | |||
| - | <button type=" | ||