TeamCity 2017.2.3版本登录失败问题求助

Hey there, let's tackle this TeamCity login issue you're facing after upgrading to 2017.2.3 (build 51047). That error about needing a domain usually pops up when the authentication settings get adjusted during the upgrade—especially since you've been using local TeamCity accounts for years. Here are the most straightforward fixes to try:

1. Use the Local Domain Prefix for Your Username #

Since you’re working with local (non-domain/LDAP) accounts, the upgraded TeamCity now expects a domain identifier for local users. You can use either:

• .\your_username (the dot represents your local machine's domain)
• localhost\your_username

This should work if the authentication mode still allows local users but just requires the domain prefix now.

2. Check Authentication Settings via Guest Login (If Enabled) #

If your TeamCity instance has guest access turned on, you can bypass the login screen temporarily to tweak settings:

• Visit http://<your-teamcity-url>/login.html?auth=Guest
• Once logged in as guest, go to Administration > Authentication
• Verify the authentication mode:
  • If it’s set to domain-based options like "NTLM" or "Kerberos", switch it back to LOCAL or DEFAULT to use your existing local accounts
  • Save changes and try logging in again (with or without the local prefix from step 1, depending on what works)

3. Manually Adjust the Server Configuration File #

If guest login isn’t enabled, you’ll need to edit the TeamCity config directly:

1. Stop the TeamCity server service
2. Navigate to your TeamCity installation directory, then open conf\teamcity-server.xml
3. Look for the <auth-type> element (usually inside the <web-app> section)
4. Change its value to LOCAL or DEFAULT (e.g., <auth-type>LOCAL</auth-type>)
5. Save the file and restart the TeamCity server
6. Try logging in with your regular username, or use the .\your_username format if needed

4. Confirm Your User Account Status #

Once you get access via one of the above methods, head to Administration > Users to double-check that your account is still active and has the correct permissions—sometimes upgrades can accidentally toggle account statuses.

内容的提问来源于stack exchange，提问作者Jay