faq:faq_desktop_firewall_proxy

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
faq:faq_desktop_firewall_proxy [2024/12/06 20:10] – robfaq: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:
 +  * ''74.201.6.0 /24 (Mask: 255.255.255.0)''
 +  * ''4.8.174.128 /25 (Mask: 255.255.255.128)''
 +  * ''162.43.176.128 /27 (Mask: 255.255.255.224)''
  
-  * Internap - EQ-CER Range: 74.201.6.0 /24 Mask: 255.255.255.0 +All application traffic uses port 443. The following domain names must also be permitted through your firewall: 
-  * CenturyLink - EQ-CER Range: 69.44.110.0 /24 Mask: 255.255.255.0+  * ''*.t4login.com'' 
 +  * ''*.sim.t4login.com'' 
 +  * ''https://futures-technologies.plus500.com/''
  
-Our applications use port 80 & 443 on any of those IP’s. From a domain name perspective then you need *.t4login.com, *.sim.t4login.com and www.ctsfutures.com open. 
- 
-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 unauthenticated proxy servers. If your proxy requires authentication, you will need to configure T4 to bypass it, as the Microsoft .NET Framework does not support authenticated proxy servers.
  
 +If your proxy does not require authentication, T4 should connect without any additional configuration. If connectivity issues persist, bypassing the proxy entirely is recommended if that option is available.
 +
 +Proxy configuration is supported via the following environment variable:
 <code>HTTPS_PROXY=http://proxy.example.com:8080</code> <code>HTTPS_PROXY=http://proxy.example.com:8080</code>
-  
-===== 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="success" size="sm" icon="glyphicon glyphicon-edit">[[http://172.28.253.55/doku.php?id=faq:faq|FAQ Home]]</button> 
  • faq/faq_desktop_firewall_proxy.1733515810.txt.gz
  • Last modified: 2024/12/06 20:10
  • by rob