These settings are accessible during the Login and Registration process.

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.

If your organisation is using the Teamwire Cloud Backend, please enter backend.teamwire.eu.

  These settings are accessible during the Login and Registration process, and in the app's Settings > Advanced options when you are logged in.

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.

If your organisation is using the Teamwire Cloud Backend, please enter backend.teamwire.eu.

  These settings are accessible during the Login and Registration process.

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.

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.

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.

• HTTPS Proxy
  https://your-proxy.com:9000
  https://username:password@your-proxy.com:9000

• PAC Proxy
  pac+http://file-provider.com/proxy.pac

  These settings are accessible during the Login and Registration process, and in the app's Settings > Advanced options when you are logged in.

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.

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.

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.

• HTTPS Proxy
  https://your-proxy.com:9000
  https://username:password@your-proxy.com:9000

• SOCKS-5 Proxy
  socks5://your-proxy.com:9000
  socks5://username:password@your-proxy.com:9000

• SOCKS-4 Proxy
  socks4://your-proxy.com:9000

• PAC Proxy
  pac+http://file-provider.com/proxy.pac
   

System Proxy

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.

Custom server certificates are currently not supported by Desktop version 4.

  These settings are accessible during the Login and Registration process.

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.

Use a custom certificate file

Click the button and select the file containing the server's certificate chain (format: PEM) via the file explorer.

Use system certificate chain (Windows)

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.