Unable to render embedded object: File (TeamCity48.png) not found.

TeamCity 2018.x Documentation

Documentation for Previous Versions


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.
Comment: related to https://youtrack.jetbrains.com/issue/TW-57175


If you did not change the default port (80) during the installation, the TeamCity web UI can be accessed via "http://localhost/" address in  in a web browser running on the same machine where the server is installed. Please note that port 80 can be used by other programs (e.g. Skype, or other web servers like IIS). In this case you can specify another port during the installation and use "http://localhost:<port>/ " address in the browser.



Ensure you have JRE or JDK installed and the JAVA_HOME environment variable is pointing to the Java installation directory. Oracle Java 8 JDK is JDK 1.8.0_16 or later is required.



For automated server installation, use the .tar.gz distribution.

Typically, you will need to unpack it and make the script perform the steps noted in Configuring Server for Production Use section.

If you want to get a pre-configured server right away, put files from a previously configured server into the Data Directory. For each new server you will need to ensure it points to a new database (configured in <Data Directory>\config\database.properties) and change <Data Directory>\config\main-config.xml file not to have the "uuid" attribute in the root XML element (so new one can be generated) and setting appropriate value for "rootURL" attribute.

Notes on configuring Windows for the server setup (based on Windows Server 2016):
- enable Remote desktop connections
- create dedicated user (e.g. "TeamCity") and assign it administrator permissions
- disable disk indexing for all disks (or at least for the disks where TeamCity home and TeamCity Data Directory are located)
- disable real-time protection и cloud-based protection in Windows Defender
- check Windows Firewall is enabled (counter-intuitively this changes Windows network stack behavior to handle more incoming but not yet accepted network connections)
on Windows Firewall settings:
-- enable incoming connections to TeamCity application ports
-- enable ICMP pings
-- enable ports for monitoring agent, etc.
- (if IPv6 network is not used) disable ipv6 on network adapter settings
- disable weekly schedule for fragmentation analyzing
- disable "Optimize drive" service
- (for manual updates application) set Windows updates policy to "DownloadOnly" via sconfig utility
- consider enabling jumbo frames and ensuring that the network supports the setting (check that all the related network infrastructure supports it e.g. via "ping -l 8960 -f <host>")

Using another Version of Tomcat

If you want to To use another version of the Tomcat web server instead of the one bundled in the .tar.gz and .exe distributions), you have the choices of whether to can either use the .war TeamCity distribution (not recommended) or perform the Tomcat upgrade/patch for TeamCity installed from the .exe or .tar.gz distributions.

For the latter, you might want to: