Start TeamCity Server
If TeamCity is installed using the
.tar.gz distributions, it can be started and stopped by the
teamcity-server scripts located in the
<TeamCity Home>/bin directory. The scripts accept
run (run in the same console),
start (start a new detached process and exit from the script), and
(evaluation only) To start/stop the TeamCity server and one default agent at the same time, use the
runAll script, for example:
runAll.bat startto start the server and default agent.
runAll.bat stopto stop the server and default agent.
To start/stop the TeamCity server only, use the
teamcity-server scripts and pass the required parameters. Start the script without parameters to see the usage instructions. The
teamcity-server scripts support the following options for the
stop n— sends the stop command to the TeamCity server and waits up to
nseconds for the process to end.
stop n -force— sends the stop command to the TeamCity server, waits up to
nseconds for the process to end, and terminates the server process if it did not stop.
If a TeamCity server is installed as a Windows service, follow the usual procedure of starting and stopping services.
If you need to pass special properties to the server, refer to this article.
You can configure autostart of TeamCity on your machine by the means of the operating systems (see the example for macOS).
Launch TeamCity UI
The TeamCity UI can be accessed via a web browser. The default addresses are
http://localhost/ for the
exe distribution and
http://localhost:8111/ for the
tar.gz distribution. See how to change the server port, if necessary.
If you cannot access the TeamCity UI after a successful installation, please refer to the troubleshooting section.
Troubleshoot TeamCity Installation
If the TeamCity UI cannot be accessed, check the following:
The TeamCity Server service is running (if you installed TeamCity as a Windows service).
The TeamCity server process (Tomcat) is running (a Java process run in the
Any warnings in the console output if you run the server from a console.
teamcity-server.logfile and other files in the
<TeamCity Home>\logsdirectory for error messages.
One of the most common issues with the server installation is using a port that is already used by another program. See how to change the default port.