Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have no clue what other program might be using port 80, but after checking the TeamCity log file, it appears to be in use already:

The following is from catalina.2012-12-03.log:

SEVERE: Failed to initialize end point associated with ProtocolHandler ["http-bio-80"] Address already in use: JVM_Bind :80 at at at org.apache.coyote.AbstractProtocol.init( at org.apache.coyote.http11.AbstractHttp11JsseProtocol.init( at org.apache.catalina.connector.Connector.initInternal( at org.apache.catalina.util.LifecycleBase.init( at org.apache.catalina.core.StandardService.initInternal( at org.apache.catalina.util.LifecycleBase.init( at org.apache.catalina.core.StandardServer.initInternal( at org.apache.catalina.util.LifecycleBase.init( at org.apache.catalina.startup.Catalina.load( at org.apache.catalina.startup.Catalina.load( at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.catalina.startup.Bootstrap.load( at org.apache.catalina.startup.Bootstrap.main(

I tried changing the port when the 'Configure Build Agent Properties' window came up during installation, in the serverUrl property, but this didn't seem to have any effect.

Is there a configuration file I use to change the server port, and then maybe restart the TeamCity services?

share|improve this question

closed as not a real question by mdpc, voretaq7 Dec 4 '12 at 2:35

It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

You need to do a little more research before we can possibly help you. For instance have you done netstat -a? Have you looked at ps or lsof? – mdpc Dec 3 '12 at 19:54
netstat -a revealed I'm listening on port 80. – Sam Pearson Dec 3 '12 at 20:08
Strange thing is, going to localhost in my web browser doesn't work (Google Chrome pops up with "Oops! This link appears to be broken") – Sam Pearson Dec 3 '12 at 20:10
Settings should be in <TeamCity Home>/conf/server.xml file (See… ) – sgmoore Dec 3 '12 at 20:17
Thanks sgmoore, found it! – Sam Pearson Dec 3 '12 at 20:20
up vote 1 down vote accepted

I solved the problem by going into TeamCity folder\conf\ and opening up server.xml.

About halfway down there was the following:

<Connector port="80" protocol="HTTP/1.1" connectionTimeout="60000" redirectPort="8543" useBodyEncodingForURI="true" />

So I changed the port attribute to 81 and restarted the build agent and server services and it worked! I can now access TeamCity web at http://localhost:81.

share|improve this answer
You may also have to change the build-agents properties for calling the new port in TeamCity folder\buildAgent\conf\ – cederlof Sep 11 '15 at 10:29

Not the answer you're looking for? Browse other questions tagged or ask your own question.