Build Status problem after update to 2017.2.1
Hi all,
after the latest update of my server to version 2017.2.1 I don't get live build information anymore (the green bars in the project overview indication approx. build time, build agents running and builds queued). I need to manually refresh my browser (f5) to see the current status.
Does anyone else got this problem and/or knows how to fix this?
Best regards
Please sign in to leave a comment.
Hi,
such issues are probably caused by a misconfigured network software (reverse proxy, antivirus) between the browser and TeamCity Server.
Such proxies close WebSocket connections and TeamCity fails to fallback to polling (while it did it in the previous versions). This is a bug introduced in 2017.2.1 and it will be fixed in 2017.2.2
As a workaround it's possible to add a internal property: teamcity.ui.websocket.enabled=false
Hi Heurazio,
We haven't seen this happen, could you try clearing the browser's cache and the like?
Hi Denis,
As you can see in the image, the marked parts don't update anymore. I need to refresh by hand. I already cleaned the cache and tried with multiple browsers but without success.
I get this HTTP errors in my browser's console
And I'm using this TeamCity server setting:
It's behind a reverse proxy (IIS10). Before the update, everything worked fine.
I have the same problem as well, the page doesn't refresh automatic any more. I'm using IIS 8 for reverse proxy
Hi Heurazio, thanks for detailing the issue and providing the screenshots. I've created an issue in our tracker: https://youtrack.jetbrains.com/issue/TW-53261. Please watch and vote to stay informed of its progress.
@Jacobsen: Could you confirm whether you're also using 2017.2.1? And whether the errors also appear on your console?
I'm using 2017.2.1
Hi Dmitry,
I adapted your proxy guild (https://confluence.jetbrains.com/pages/viewpage.action?pageId=74845225#HowTo...-SetUpTeamCitybehindaProxyServer ) for my IIS. Maybe you could give more detailed instruction for an IIS setup if it differs a lot from the ones you guided.
This is my reverse proxy rules. They didn't change between the versions of TC.
(Note that the outbound rule is disabled. I tested with and without and it doesn't change the result)
@Dmitry: The workaround is working for me.
@Heurazio could you please explain your setup? Do you have any other network software (proxies/firewall/antivirus) other than IIS?
Also could you please open https://websocketstest.com/ and attach the result here?
Only using Windows Firewall + Defender. No other proxies then IIS. I'm also running an Octopus Deploy and JIRA Board (same strategy with the IIS proxy).
Run your test on both systems (Dev + Server):
DEV:
Server:
Thanks, could you also try to access TeamCity without IIS? Will WebSocket work in this case?
If I connect directly from my server, either with localhost:8888 or domain (teamcity.xxx.com) it's working fine.
Ok, so it seems that the problem is in Windows Firewall, Defender or IIS.
Could you try to disable them one-by-one to find you the root cause of the issue? I mean try to access the server via IIS but with disabled firewall and so on
Tried as you suggested but without success.
Ok, thanks, so the problem is in IIS. We'll try to reproduce it