Wiki source code of 3. Advanced Configurations
Version 4.1 by teamwire001 on 2025/08/19 08:16
Hide last authors
author | version | line-number | content |
---|---|---|---|
![]() |
2.1 | 1 | {{id name="4-hostname"/}} |
2 | |||
![]() |
4.1 | 3 | = Server = |
![]() |
2.1 | 4 | |
![]() |
4.1 | 5 | {{tabs idsToLabels="server1=Desktop 4, server2=Until Desktop 3.4.3"/}} |
![]() |
2.1 | 6 | |
![]() |
4.1 | 7 | (% id="server1" %) |
8 | ((( | ||
9 | {{icon name="cog"/}} These settings are accessible during the [[Login and Registration process>>doc:Public.Applications.Desktop.User-Manual.Login-and-Registration.WebHome]]. | ||
![]() |
2.1 | 10 | |
11 | |||
![]() |
4.1 | 12 | If required, please enter the custom **server name** here. You must not enter the protocol or path but the name only. It is recommended to add this information in order to speed up the process and prevent registration failures. |
![]() |
2.1 | 13 | |
![]() |
4.1 | 14 | If your organisation is using the Teamwire Cloud Backend, please enter ##backend.teamwire.eu##. |
15 | ))) | ||
![]() |
2.1 | 16 | |
![]() |
4.1 | 17 | (% id="server2" %) |
18 | ((( | ||
19 | {{icon name="cog"/}} These settings are accessible during the [[Login and Registration process>>doc:Public.Applications.Desktop.User-Manual.Login-and-Registration.WebHome]], and in the app's [[Settings ~> Advanced options>>doc:Public.Applications.Desktop.User-Manual.Profile-and-Settings.WebHome||anchor="04-advanced"]] when you are logged in. | ||
![]() |
2.1 | 20 | |
21 | |||
![]() |
4.1 | 22 | If required, please enter the custom **backend hostname** here. You must not enter the protocol or path but the name only. It is recommended to add this information in order to speed up the process and prevent registration failures. |
![]() |
2.1 | 23 | |
![]() |
4.1 | 24 | If your organisation is using the Teamwire Cloud Backend, please enter ##backend.teamwire.eu##. |
25 | ))) | ||
![]() |
2.1 | 26 | |
27 | |||
![]() |
4.1 | 28 | {{id name="4-proxyurl"/}} |
![]() |
2.1 | 29 | |
![]() |
4.1 | 30 | = Proxy server = |
![]() |
2.1 | 31 | |
![]() |
4.1 | 32 | {{tabs idsToLabels="proxy1=Desktop 4, proxy2=Until Desktop 3.4.3"/}} |
![]() |
2.1 | 33 | |
![]() |
4.1 | 34 | (% id="proxy1" %) |
35 | ((( | ||
36 | {{icon name="cog"/}} These settings are accessible during the [[Login and Registration process>>doc:Public.Applications.Desktop.User-Manual.Login-and-Registration.WebHome]]. | ||
![]() |
2.1 | 37 | |
38 | |||
![]() |
4.1 | 39 | In order to work properly with a proxy server, Teamwire needs your proxy to support the **HTTP CONNECT method,** the **HTTP Upgrade mechanism** and has to allow all **Sec-Websocket-* headers.** |
![]() |
1.1 | 40 | |
![]() |
4.1 | 41 | Please enter the complete URL incl. protocol (e.g. ##http## or ##https##) and port. The different types of proxy and their syntaxes are explained down below. |
![]() |
1.1 | 42 | |
![]() |
4.1 | 43 | For the following example we assume the proxy is running on a host named ##your-proxy.com## with port 9000. If your proxy needs basic HTTPS authentication, the credentials can be included in the URL as shown. |
![]() |
1.1 | 44 | |
![]() |
4.1 | 45 | * **HTTPS Proxy** |
46 | ##https:~/~/your-proxy.com:9000## | ||
47 | ##https:~/~/username:password@your-proxy.com:9000## | ||
![]() |
1.1 | 48 | |
![]() |
4.1 | 49 | * **PAC Proxy** |
50 | ##pac+http:~/~/file-provider.com/proxy.pac## | ||
51 | ))) | ||
![]() |
1.1 | 52 | |
![]() |
4.1 | 53 | (% id="proxy2" %) |
54 | ((( | ||
55 | {{icon name="cog"/}} These settings are accessible during the [[Login and Registration process>>doc:Public.Applications.Desktop.User-Manual.Login-and-Registration.WebHome]], and in the app's [[Settings ~> Advanced options>>doc:Public.Applications.Desktop.User-Manual.Profile-and-Settings.WebHome||anchor="04-advanced"]] when you are logged in. | ||
![]() |
1.1 | 56 | |
57 | |||
58 | In order to work properly with a proxy server, Teamwire needs your proxy to support the **HTTP CONNECT method,** the **HTTP Upgrade mechanism** and has to allow all **Sec-Websocket-* headers.** | ||
59 | |||
![]() |
4.1 | 60 | Please enter the complete URL incl. protocol (e.g. ##http## or ##https##) and port. The different types of proxy and their syntaxes are explained down below. |
![]() |
1.1 | 61 | |
![]() |
4.1 | 62 | For the following example we assume the proxy is running on a host named ##your-proxy.com## with port 9000. If your proxy needs basic HTTPS or SOCKS-5 authentication, the credentials can be included in the URL as shown. |
![]() |
1.1 | 63 | |
64 | * **HTTPS Proxy** | ||
![]() |
4.1 | 65 | ##https:~/~/your-proxy.com:9000## |
66 | ##https:~/~/username:password@your-proxy.com:9000## | ||
![]() |
1.1 | 67 | |
68 | * **SOCKS-5 Proxy** | ||
![]() |
4.1 | 69 | ##socks5:~/~/your-proxy.com:9000## |
70 | ##socks5:~/~/username:password@your-proxy.com:9000## | ||
![]() |
1.1 | 71 | |
72 | * **SOCKS-4 Proxy** | ||
![]() |
4.1 | 73 | ##socks4:~/~/your-proxy.com:9000## |
![]() |
1.1 | 74 | |
75 | * **PAC Proxy** | ||
![]() |
4.1 | 76 | ##pac+http:~/~/file-provider.com/proxy.pac## |
![]() |
1.1 | 77 | ## ## |
78 | |||
![]() |
4.1 | 79 | (% class="box-title" %) |
80 | System Proxy | ||
![]() |
1.1 | 81 | |
![]() |
1.2 | 82 | If the proxy data are already provided to the (Windows) system, you can select **Use system proxy** to apply the operating system's internet settings. |
![]() |
4.1 | 83 | ))) |
![]() |
1.1 | 84 | |
85 | |||
86 | {{id name="certificate"/}} | ||
87 | |||
![]() |
4.1 | 88 | = Server certificate = |
![]() |
1.1 | 89 | |
![]() |
4.1 | 90 | {{tabs idsToLabels="certificate1=Desktop 4, certificate2=Until Desktop 3.4.3"/}} |
91 | |||
92 | (% id="certificate1" %) | ||
93 | ((( | ||
94 | Custom server certificates are currently not supported by Desktop version 4. | ||
95 | ))) | ||
96 | |||
97 | (% id="certificate2" %) | ||
98 | ((( | ||
99 | {{icon name="cog"/}} These settings are accessible during the [[Login and Registration process>>doc:Public.Applications.Desktop.User-Manual.Login-and-Registration.WebHome]]. | ||
100 | |||
101 | |||
![]() |
1.1 | 102 | If the backend server uses a self-signed certificate or if it is signed by a Certificate Authority (CA), that is not well known, you will have to provide the certificate chain. |
103 | |||
104 | |||
105 | {{id name="customcertificatefile"/}} | ||
106 | |||
![]() |
4.1 | 107 | (% class="box-title" %) |
108 | Use a custom certificate file | ||
![]() |
1.1 | 109 | |
110 | Click the button and select the file containing the server's certificate chain (format: ##PEM##) via the file explorer. | ||
111 | |||
![]() |
4.1 | 112 | {{info}} |
113 | Please make sure to use the unix line feed ##LF## on your certificate. Any other control characters like ##CR## or Windows' ##CR LF## will not be valid. | ||
![]() |
1.1 | 114 | |
115 | Also note, that the path used to refer to your certificate must not contain any spaces. | ||
![]() |
4.1 | 116 | {{/info}} |
![]() |
1.1 | 117 | |
118 | |||
119 | {{id name="systemcertificatechain"/}} | ||
120 | |||
![]() |
4.1 | 121 | (% class="box-title" %) |
122 | Use system certificate chain (Windows) | ||
![]() |
1.1 | 123 | |
124 | Select this option if the custom certificate has been applied to the Microsoft Management Console. Teamwire will automatically check the so-called Certificate Trust Store for any necessary information. | ||
![]() |
4.1 | 125 | ))) |
![]() |
1.1 | 126 | |
127 | ## ## |