Skip to Content
Last modified by teamwire001 on 2026/07/08 06:30
From version 1.4
edited by teamwire001
on 2023/02/10 13:49
Change comment: reorder by title
To version 6.2
edited by teamwire001
on 2026/07/08 06:30
Change comment: DOC-573

Summary

Details

Page properties
Content
... ... @@ -1,75 +1,40 @@
1 -These settings are accessible during the [[Login and Registration process>>doc:Public.Applications.Desktop.User-Manual.Login-and-Registration.WebHome]] or later by opening the app's [[Settings > Advanced options>>doc:Public.Applications.Desktop.User-Manual.Profile-and-Settings.WebHome||anchor="04-advanced"]].
1 +{{id name="4-hostname"/}}
2 2  
3 += Server =
3 3  
4 -{{id name="hostname"/}}
5 +{{icon name="cog"/}} These settings are accessible during the [[Login and Registration process>>doc:Public.Applications.Desktop.User-Manual-Desktop4.Login-and-Registration.WebHome]].
5 5  
6 -= Backend hostname =
7 7  
8 -If required, please enter the custom backend hostname here. You must not enter the protocol or path but the **hostname only.** It is recommended to add this information in order to speed up the process and prevent registration failures.
8 +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.
9 9  
10 -If your organisation is using the Teamwire Cloud Backend, please enter {{code}}backend.teamwire.eu{{/code}}.
10 +If your organisation is using the Teamwire Cloud Backend, please enter ##backend.teamwire.eu##.
11 11  
12 12  
13 -{{id name="proxy"/}}
13 +{{id name="4-proxyurl"/}}
14 14  
15 15  = Proxy server =
16 16  
17 -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.**
17 +{{icon name="cog"/}} These settings are accessible during the [[Login and Registration process>>doc:Public.Applications.Desktop.User-Manual-Desktop4.Login-and-Registration.WebHome]].
18 18  
19 19  
20 -{{id name="proxyurl"/}}
20 +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.**
21 21  
22 -== Apply proxy URL ==
22 +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.
23 23  
24 -Please enter the complete URL incl. protocol (e.g. {{code}}http{{/code}} or {{code}}https{{/code}}) and port. The different types of proxy and their syntaxes are explained down below. For the following example we assume the proxy is running on a host named {{code}}your-proxy.com{{/code}} with port {{code}}9000{{/code}}. If your proxy needs basic HTTPS or SOCKS-5 authentication, the credentials can be included in the URL as shown.
24 +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.
25 25  
26 26  * **HTTPS Proxy**
27 -{{code language="html"}}https://your-proxy.com:9000{{/code}}
28 -{{code language="html"}}https://username:password@your-proxy.com:9000{{/code}}
27 +##https:~/~/your-proxy.com:9000##
28 +##https:~/~/username:password@your-proxy.com:9000##
29 29  
30 -* **SOCKS-5 Proxy**
31 -{{code language="html"}}socks5://your-proxy.com:9000{{/code}}
32 -{{code language="html"}}socks5://username:password@your-proxy.com:9000{{/code}}
33 -
34 -* **SOCKS-4 Proxy**
35 -{{code language="html"}}socks4://your-proxy.com:9000{{/code}}
36 -
37 37  * **PAC Proxy**
38 -{{code language="html"}}pac+http://file-provider.com/proxy.pac{{/code}}
31 +##pac+http:~/~/file-provider.com/proxy.pac##
39 39  ## ##
40 40  
41 -{{id name="systemproxy"/}}
42 -
43 -== Use system proxy ==
44 -
45 -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.
46 -
47 -
48 48  {{id name="certificate"/}}
49 49  
50 50  = Server certificate =
51 51  
52 -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.
38 +Custom server certificates are currently not supported.
53 53  
54 -
55 -{{id name="customcertificatefile"/}}
56 -
57 -== Choose custom certificate file ==
58 -
59 -Click the button and select the file containing the server's certificate chain (format: ##PEM##) via the file explorer.
60 -
61 -(% class="box infomessage" %)
62 -(((
63 -Please make sure to use the unix line feed {{code}}LF{{/code}} on your certificate. Any other control characters like ##CR## or Windows' ##CR LF## will not be valid.
64 -
65 -Also note, that the path used to refer to your certificate must not contain any spaces.
66 -)))
67 -
68 -
69 -{{id name="systemcertificatechain"/}}
70 -
71 -== Use system certificate chain (Windows) ==
72 -
73 -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.
74 -
75 75  ## ##