You are viewing the documentation of TeamCity 2018.x, which is not the most recently released version of TeamCity.
View this page in the latest documentation or refer to the listing to choose the documentation corresponding to your TeamCity version.


Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


Wiki Markup
Some NGINX configuration resource: https://nginxconfig.io/
some more NGINX params which might also relate:

client_header_timeout  10m;
client_body_timeout    10m;
send_timeout           10m;
proxy_max_temp_file_size 10240m;
Note: Some TeamCity resource names might start with "." symbol (e.g. hidden artifacts under .teamcity directory), so make sure not to blindly deny resources with the name names starting with a dot.

Other servers


For small servers, you can set up HTTPS via the internal Tomcat means, but this is not recommended as it can may significantly increase the CPU load.

For configuring clients to access TeamCity server via HTTPS while using self-signed certificate, check the related instructions.

Configure TeamCity to Use Proxy Server for Outgoing Connections


Move TeamCity Installation to a New Machine

If you need to move the an existing TeamCity installation to a new hardware or a clean OS, you can install the same TeamCity version on the new machine, stop the old server, connect the new server to the same TeamCity Data Directory and make sure the server uses the same environment.
Alternatively, you can follow the instructions on copying the server from one machine to another.

After the move, make the clients use the new server address, if changed.