Some users experience UI-related issues when browsing TeamCity UI

Symptoms

• Some users experience issues related to the TeamCity web UI.
• They are reproduced only for some users and not reproduced on other computers or browsers.

Cause

The simplest and most common cause is that the browser uses a cached version of the UI, and there is a problem with the cache.

If the users experience 400: Request Header too large or 502: Bad Gateway errors, check this article.

Resolution

Make sure the browser does not use cached content by opening the UI in a new Incognito window or by clearing browser caches.

If the issue persists after clearing the cache and is reproduced in an Incognito window as well, contact TeamCity support and provide:

1. A detailed description of the issue, with screenshots or screen recordings if possible.
2. HAR logs from the browser, recorded while reproducing the issue. They may indicate possible causes.
3. A timestamp when the issue was reproduced.
4. TeamCity server logs (contents of <TeamCity Server Home>/logs). If sending all logs from the server is not feasible, the following are most likely to be useful:
   • teamcity-server.log covering the timestamp mentioned in (3).
   • If there are any automatically created thread dumps in the logs directory, they should be shared too.