Wiki source code of 3. Advanced Configurations
Last modified by teamwire001 on 2025/09/11 14:58
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 | |
| |
4.2 | 27 | (% style="border-color:var(--gili_blue_300)" %) |
| 28 | ---- | ||
| |
2.1 | 29 | |
| |
4.2 | 30 | |
| |
4.1 | 31 | {{id name="4-proxyurl"/}} |
| |
2.1 | 32 | |
| |
4.1 | 33 | = Proxy server = |
| |
2.1 | 34 | |
| |
4.1 | 35 | {{tabs idsToLabels="proxy1=Desktop 4, proxy2=Until Desktop 3.4.3"/}} |
| |
2.1 | 36 | |
| |
4.1 | 37 | (% id="proxy1" %) |
| 38 | ((( | ||
| 39 | {{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 | 40 | |
| 41 | |||
| |
4.1 | 42 | 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 | 43 | |
| |
4.1 | 44 | 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 | 45 | |
| |
4.1 | 46 | 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 | 47 | |
| |
4.1 | 48 | * **HTTPS Proxy** |
| 49 | ##https:~/~/your-proxy.com:9000## | ||
| 50 | ##https:~/~/username:password@your-proxy.com:9000## | ||
| |
1.1 | 51 | |
| |
4.1 | 52 | * **PAC Proxy** |
| 53 | ##pac+http:~/~/file-provider.com/proxy.pac## | ||
| 54 | ))) | ||
| |
1.1 | 55 | |
| |
4.1 | 56 | (% id="proxy2" %) |
| 57 | ((( | ||
| 58 | {{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 | 59 | |
| 60 | |||
| 61 | 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.** | ||
| 62 | |||
| |
4.1 | 63 | 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 | 64 | |
| |
4.1 | 65 | 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 | 66 | |
| 67 | * **HTTPS Proxy** | ||
| |
4.1 | 68 | ##https:~/~/your-proxy.com:9000## |
| 69 | ##https:~/~/username:password@your-proxy.com:9000## | ||
| |
1.1 | 70 | |
| 71 | * **SOCKS-5 Proxy** | ||
| |
4.1 | 72 | ##socks5:~/~/your-proxy.com:9000## |
| 73 | ##socks5:~/~/username:password@your-proxy.com:9000## | ||
| |
1.1 | 74 | |
| 75 | * **SOCKS-4 Proxy** | ||
| |
4.1 | 76 | ##socks4:~/~/your-proxy.com:9000## |
| |
1.1 | 77 | |
| 78 | * **PAC Proxy** | ||
| |
4.1 | 79 | ##pac+http:~/~/file-provider.com/proxy.pac## |
| |
1.1 | 80 | ## ## |
| 81 | |||
| |
4.1 | 82 | (% class="box-title" %) |
| 83 | System Proxy | ||
| |
1.1 | 84 | |
| |
1.2 | 85 | 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 | 86 | ))) |
| |
1.1 | 87 | |
| |
4.2 | 88 | (% style="border-color:var(--gili_blue_300)" %) |
| 89 | ---- | ||
| |
1.1 | 90 | |
| |
4.2 | 91 | |
| |
1.1 | 92 | {{id name="certificate"/}} |
| 93 | |||
| |
4.1 | 94 | = Server certificate = |
| |
1.1 | 95 | |
| |
4.1 | 96 | {{tabs idsToLabels="certificate1=Desktop 4, certificate2=Until Desktop 3.4.3"/}} |
| 97 | |||
| 98 | (% id="certificate1" %) | ||
| 99 | ((( | ||
| 100 | Custom server certificates are currently not supported by Desktop version 4. | ||
| 101 | ))) | ||
| 102 | |||
| 103 | (% id="certificate2" %) | ||
| 104 | ((( | ||
| 105 | {{icon name="cog"/}} These settings are accessible during the [[Login and Registration process>>doc:Public.Applications.Desktop.User-Manual.Login-and-Registration.WebHome]]. | ||
| 106 | |||
| 107 | |||
| |
1.1 | 108 | 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. |
| 109 | |||
| 110 | |||
| 111 | {{id name="customcertificatefile"/}} | ||
| 112 | |||
| |
4.1 | 113 | (% class="box-title" %) |
| 114 | Use a custom certificate file | ||
| |
1.1 | 115 | |
| 116 | Click the button and select the file containing the server's certificate chain (format: ##PEM##) via the file explorer. | ||
| 117 | |||
| |
4.1 | 118 | {{info}} |
| 119 | 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 | 120 | |
| 121 | Also note, that the path used to refer to your certificate must not contain any spaces. | ||
| |
4.1 | 122 | {{/info}} |
| |
1.1 | 123 | |
| 124 | |||
| 125 | {{id name="systemcertificatechain"/}} | ||
| 126 | |||
| |
4.1 | 127 | (% class="box-title" %) |
| 128 | Use system certificate chain (Windows) | ||
| |
1.1 | 129 | |
| 130 | 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 | 131 | ))) |
| |
1.1 | 132 | |
| |
4.2 | 133 | (% style="border-color:var(--gili_blue_300)" %) |
| 134 | ---- | ||
| 135 | |||
| |
1.1 | 136 | ## ## |