ReSharper + TeamCity - "Remote Run (Local changes)" return "A connection that was expected to be kept alive was closed by the server"


We using TeamCity on our own server. In March 2020 we moved office and as result changed network infrastructure. We have 2 teams. One team (local) has no issues, but second team (connected remotely via Cisco VPN) having issues when they try to execute "Remote Run (Local changes)". They can access TeamCity WebUI via browser (on port 8111), but when they try to execute "Remote Run (Local changes)" they receive "A connection that was expected to be kept alive was closed by the server" error.

Port 8111 is open on firewall (as I wrote they are able to access WebUI).

We capture network traffic on both (successful and failing) cases, but found no clue there.

Latest released versions of TeamCity and ReSharper (Visual Studio 2019) installed.

Are there any other port need to be open on firewall?

Or any other suggestions how to investigate/resolve the issue?


1 comment
Comment actions Permalink



Sorry for the delay in responding.

Could you please perform the following steps and provide us some info so we could troubleshoot the problem:

1. Change logging preset on TeamCity intance to  debug-general as described in the following article

2. Enable debug output in InspectCode options -

3. Perform "Remote Run" via VPN and wait until the error occurs.

4. Change logging preset back

5. Send us  teamcity-server.log and dotnet-tools-inspectcode.log. You can do it privately via "Submit a request" form at the top of the page.

Thank you.


Please sign in to leave a comment.