Apache as reverse proxy for TeamCity

If you point your browser to some URL inside TeamCity and TeamCity detects that you are not authenticated the original URL is remembered and after the login you will be pointed to the remembered url. Probably this is what you are experiencing.

--
Pavel Sher

Add this to your Apache conf file

LoadModule proxy_module bin/mod_proxy.so
LoadModule proxy_http_module bin/mod_proxy_http.so

ProxyPass /TeamCity http://localhost/TeamCity
ProxyPassReverse /TeamCity http://localhost/TeamCity

Add the Context to your TeamCity conf server.xml file in the Host section

<Host name="localhost"  appBase="webapps"

            unpackWARs="true" autoDeploy="true"

            xmlValidation="false" xmlNamespaceAware="false">

<Context path="/TeamCity"

     docBase="C:\TeamCity\webapps\ROOT"

     debug="1"

     reloadable="true" > </Context>


UPDATE by Yegor Yarko:
Please do not add contexts into server.xml. This might result in two TeamCity instances running.
Another approach.

Hi

Im confused with the following line

ProxyPass /TeamCity http://localhost/TeamCity
ProxyPassReverse /TeamCity http://localhost/TeamCity

should or could localhost be the name or ip address of the teamcity server.

I am planning to setup a apache server in a dmz and open ports to the internal teamcity server and am confused what localhost should be ?

Yes, it was just an example.
You need to specify actual address of TeamCity instance.

When i add this
<Context path="/TeamCity"
     docBase="C:\TeamCity\webapps\ROOT"
     debug="1"
     reloadable="true" > </Context>

I get the following error

[2011-05-31 15:35:23,395]  ERROR -   jetbrains.buildServer.SERVER - Server startup exception: jetbrains.buildServer.serverSide.db.SecondTeamCityInstanceException: Attempt to start more than one TeamCity server connected to the same database.

jetbrains.buildServer.serverSide.db.SecondTeamCityInstanceException: Attempt to start more than one TeamCity server connected to the same database.

                at jetbrains.buildServer.serverSide.db.TeamCityDatabaseManager.lock(TeamCityDatabaseManager.java:342)

                at jetbrains.buildServer.rootDispatcher.TeamCityDispatcherServlet.processStartupServerInternal(TeamCityDispatcherServlet.java:130)

                at jetbrains.buildServer.rootDispatcher.TeamCityDispatcherServlet.processStartupServerSafe(TeamCityDispatcherServlet.java:128)

                at jetbrains.buildServer.rootDispatcher.TeamCityDispatcherServlet.access$400(TeamCityDispatcherServlet.java:306)

                at jetbrains.buildServer.rootDispatcher.TeamCityDispatcherServlet$6.run(TeamCityDispatcherServlet.java)

The issue has been resolved by email, but for reference.
To change TeamCity address from http://server/ to http://server/teamcity/, move <TeamCity home>\webapps\ROOT directory to <TeamCity home>\webapps\teamcity.

Reviving an old thread to give a set up that worked for me:

Problem:

• TeamCity is installed in  http://server:8111/
• You want to access it via  http://server/tc/

Solution:
     1. Move TeamCity installation in Tomcat
          cd  <TeamCity>/webapps
          mv  ROOT  tc

          Restart TeamCity
          /sbin/service  teamcity  restart

          Now TeamCity is accessible via  http://server:8111/tc/

     2. Set up reverse proxy on your httpd server
          vi  /etc/httpd/conf.d/<yourconfig>.conf

          Paste in the following:
          ProxyRequests  Off
     ProxyPass         /tc  http://server:8111/tc
     ProxyPassReverse  /tc  http://server:8111/tc

          Restart httpd
          /sbin/service  httpd  restart

          Now TeamCity is accessible via  http://server/tc/

     3. ...?

     4. Profit!

Thanks for sharing!