Error with changed password

...and, now it's working again (no change to password field)

Hi,

the git-upload-pack not permitted error doesn't mean exclusively an error on authorization. We would need to know the full stacktrace for it, which is probably located in the teamcity-server.log, or teamcity-vcs.log from either the server or agent, depending on where it's failing.  Which version of TeamCity are you using?

Is the issue happening during the server connection to the repo, or is it on the agent during builds? It might be that the credentials have been cached by the agents and aren't working properly until renewed.

If you can't find the root of the issue, please collect the logs mentioned above and send them to us for review, either using the "Submit a request" button on top, or using any upload service you consider appropriate. We have the option to upload it here: https://confluence.jetbrains.com/display/TCD18/Reporting+Issues#ReportingIssues-UploadingLargeDataArchives

Stack trace:

jetbrains.buildServer.vcs.VcsRootVcsException: List remote refs failed: org.eclipse.jgit.errors.TransportException: https://bitbucket.org/...: git-upload-pack not permitted
at jetbrains.buildServer.vcs.impl.VcsChangesStatesCollector.createRootException(VcsChangesStatesCollector.java:99)
at jetbrains.buildServer.vcs.impl.VcsChangesStatesCollector.getCurrentState(VcsChangesStatesCollector.java:63)
at jetbrains.buildServer.vcs.impl.VcsChangesStatesCollector.lambda$null$1(VcsChangesStatesCollector.java:53)
at jetbrains.buildServer.util.NamedThreadFactory.executeWithNewThreadName(NamedThreadFactory.java:76)
at jetbrains.buildServer.vcs.impl.VcsChangesStatesCollector.lambda$getCollectStatesTasks$2(VcsChangesStatesCollector.java:108)
at jetbrains.buildServer.vcs.impl.ImmediateFutureExecService$2.call(ImmediateFutureExecService.java:4)
at jetbrains.buildServer.serverSide.impl.ImmediateFuture.get(ImmediateFuture.java:59)
at jetbrains.buildServer.serverSide.impl.ImmediateFuture.get(ImmediateFuture.java:68)
at jetbrains.buildServer.vcs.impl.VcsChangesStatesCollector.collectStatesForAllRoots(VcsChangesStatesCollector.java:6)
at jetbrains.buildServer.vcs.impl.VcsChangesStatesCollector.getCurrentStateSnapshot(VcsChangesStatesCollector.java:90)
at jetbrains.buildServer.vcs.impl.VcsChangesFetcher.getStateAndCreateChangesCollectingTasks(VcsChangesFetcher.java:26)
at jetbrains.buildServer.vcs.impl.VcsChangesLoader.doLoadChanges(VcsChangesLoader.java:68)
at jetbrains.buildServer.vcs.impl.VcsChangesLoader.tryLoadChanges(VcsChangesLoader.java:67)
at jetbrains.buildServer.serverSide.impl.VcsModificationChecker$CollectChangesAction$1.run(VcsModificationChecker.java:20)
at jetbrains.buildServer.util.NamedThreadFactory.executeWithNewThreadName(NamedThreadFactory.java:76)
at jetbrains.buildServer.serverSide.impl.VcsModificationChecker$CollectChangesAction.run(VcsModificationChecker.java:3)
at java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1626)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: jetbrains.buildServer.vcs.VcsException: List remote refs failed: org.eclipse.jgit.errors.TransportException: https://bitbucket.org/...: git-upload-pack not permitted
at jetbrains.buildServer.buildTriggers.vcs.git.OperationContext.wrapException(OperationContext.java:185)
at jetbrains.buildServer.buildTriggers.vcs.git.GitVcsSupport.getRemoteRefs(GitVcsSupport.java:475)
at jetbrains.buildServer.buildTriggers.vcs.git.GitVcsSupport.lambda$getCurrentState$0(GitVcsSupport.java:180)
at jetbrains.buildServer.buildTriggers.vcs.git.RepositoryManagerImpl.runWithDisabledRemove(RepositoryManagerImpl.java:256)
at jetbrains.buildServer.buildTriggers.vcs.git.GitVcsSupport.getCurrentState(GitVcsSupport.java:176)
at jetbrains.buildServer.buildTriggers.vcs.git.GitVcsSupport.getCurrentState(GitVcsSupport.java:171)
at jetbrains.buildServer.buildTriggers.vcs.git.GitCollectChangesPolicy.getCurrentState(GitCollectChangesPolicy.java:113)
at jetbrains.vcs.api.services.impl.RepositoryStateServiceProvider$1.getCurrentState(RepositoryStateServiceProvider.java:6)
at jetbrains.buildServer.vcs.impl.VcsRootInstanceImpl.lambda$null$0(VcsRootInstanceImpl.java:114)
at jetbrains.buildServer.serverSide.impl.BaseAccessChecker.runWithDisabledCheck(BaseAccessChecker.java:62)
at jetbrains.buildServer.serverSide.impl.SecondaryNodeSecurityManager.runSafeNetworkOperation(SecondaryNodeSecurityManager.java:34)
at jetbrains.buildServer.serverSide.ReadOnlyRestrictor.doReadOnlyNetworkOperation(ReadOnlyRestrictor.java:4)
at jetbrains.buildServer.vcs.impl.VcsRootInstanceImpl.lambda$getCurrentState$1(VcsRootInstanceImpl.java:135)
at jetbrains.buildServer.serverSide.impl.BaseAccessChecker.runWithDisabledCheck(BaseAccessChecker.java:62)
at jetbrains.buildServer.serverSide.impl.SecondaryNodeSecurityManager.executeSafeCommandLine(SecondaryNodeSecurityManager.java:7)
at jetbrains.buildServer.serverSide.ReadOnlyRestrictor.doReadOnlyCommandLine(ReadOnlyRestrictor.java:6)
at jetbrains.buildServer.vcs.impl.VcsRootInstanceImpl.getCurrentState(VcsRootInstanceImpl.java:58)
at jetbrains.buildServer.vcs.impl.VcsChangesStatesCollector$CurrentStateOperation.call(VcsChangesStatesCollector.java:2)
at jetbrains.buildServer.vcs.impl.VcsChangesStatesCollector$CurrentStateOperation.call(VcsChangesStatesCollector.java:1)
at jetbrains.buildServer.vcs.VcsOperationProgressProviderImpl.runWithProgress(VcsOperationProgressProviderImpl.java:27)
at jetbrains.buildServer.vcs.impl.VcsChangesStatesCollector.getCurrentState(VcsChangesStatesCollector.java:103)
... 18 more
Caused by: org.eclipse.jgit.errors.TransportException: https://bitbucket.org/...: git-upload-pack not permitted
at org.eclipse.jgit.transport.TransportHttp.connect(TransportHttp.java:517)
at org.eclipse.jgit.transport.TransportHttp.openFetch(TransportHttp.java:315)
at jetbrains.buildServer.buildTriggers.vcs.git.GitVcsSupport.getRemoteRefs(GitVcsSupport.java:493)
at jetbrains.buildServer.buildTriggers.vcs.git.GitVcsSupport.getRemoteRefs(GitVcsSupport.java:470)
... 37 more
jetbrains.buildServer.vcs.VcsException: List remote refs failed: org.eclipse.jgit.errors.TransportException: https://bitbucket.org/...: git-upload-pack not permitted
at jetbrains.buildServer.buildTriggers.vcs.git.OperationContext.wrapException(OperationContext.java:185)
at jetbrains.buildServer.buildTriggers.vcs.git.GitVcsSupport.getRemoteRefs(GitVcsSupport.java:475)
at jetbrains.buildServer.buildTriggers.vcs.git.GitVcsSupport.lambda$getCurrentState$0(GitVcsSupport.java:180)
at jetbrains.buildServer.buildTriggers.vcs.git.RepositoryManagerImpl.runWithDisabledRemove(RepositoryManagerImpl.java:256)
at jetbrains.buildServer.buildTriggers.vcs.git.GitVcsSupport.getCurrentState(GitVcsSupport.java:176)
at jetbrains.buildServer.buildTriggers.vcs.git.GitVcsSupport.getCurrentState(GitVcsSupport.java:171)
at jetbrains.buildServer.buildTriggers.vcs.git.GitCollectChangesPolicy.getCurrentState(GitCollectChangesPolicy.java:113)
at jetbrains.vcs.api.services.impl.RepositoryStateServiceProvider$1.getCurrentState(RepositoryStateServiceProvider.java:6)
at jetbrains.buildServer.vcs.impl.VcsRootInstanceImpl.lambda$null$0(VcsRootInstanceImpl.java:114)
at jetbrains.buildServer.serverSide.impl.BaseAccessChecker.runWithDisabledCheck(BaseAccessChecker.java:62)
at jetbrains.buildServer.serverSide.impl.SecondaryNodeSecurityManager.runSafeNetworkOperation(SecondaryNodeSecurityManager.java:34)
at jetbrains.buildServer.serverSide.ReadOnlyRestrictor.doReadOnlyNetworkOperation(ReadOnlyRestrictor.java:4)
at jetbrains.buildServer.vcs.impl.VcsRootInstanceImpl.lambda$getCurrentState$1(VcsRootInstanceImpl.java:135)
at jetbrains.buildServer.serverSide.impl.BaseAccessChecker.runWithDisabledCheck(BaseAccessChecker.java:62)
at jetbrains.buildServer.serverSide.impl.SecondaryNodeSecurityManager.executeSafeCommandLine(SecondaryNodeSecurityManager.java:7)
at jetbrains.buildServer.serverSide.ReadOnlyRestrictor.doReadOnlyCommandLine(ReadOnlyRestrictor.java:6)
at jetbrains.buildServer.vcs.impl.VcsRootInstanceImpl.getCurrentState(VcsRootInstanceImpl.java:58)
at jetbrains.buildServer.vcs.impl.VcsChangesStatesCollector$CurrentStateOperation.call(VcsChangesStatesCollector.java:2)
at jetbrains.buildServer.vcs.impl.VcsChangesStatesCollector$CurrentStateOperation.call(VcsChangesStatesCollector.java:1)
at jetbrains.buildServer.vcs.VcsOperationProgressProviderImpl.runWithProgress(VcsOperationProgressProviderImpl.java:27)
at jetbrains.buildServer.vcs.impl.VcsChangesStatesCollector.getCurrentState(VcsChangesStatesCollector.java:103)
at jetbrains.buildServer.vcs.impl.VcsChangesStatesCollector.lambda$null$1(VcsChangesStatesCollector.java:53)
at jetbrains.buildServer.util.NamedThreadFactory.executeWithNewThreadName(NamedThreadFactory.java:76)
at jetbrains.buildServer.vcs.impl.VcsChangesStatesCollector.lambda$getCollectStatesTasks$2(VcsChangesStatesCollector.java:108)
at jetbrains.buildServer.vcs.impl.ImmediateFutureExecService$2.call(ImmediateFutureExecService.java:4)
at jetbrains.buildServer.serverSide.impl.ImmediateFuture.get(ImmediateFuture.java:59)
at jetbrains.buildServer.serverSide.impl.ImmediateFuture.get(ImmediateFuture.java:68)
at jetbrains.buildServer.vcs.impl.VcsChangesStatesCollector.collectStatesForAllRoots(VcsChangesStatesCollector.java:6)
at jetbrains.buildServer.vcs.impl.VcsChangesStatesCollector.getCurrentStateSnapshot(VcsChangesStatesCollector.java:90)
at jetbrains.buildServer.vcs.impl.VcsChangesFetcher.getStateAndCreateChangesCollectingTasks(VcsChangesFetcher.java:26)
at jetbrains.buildServer.vcs.impl.VcsChangesLoader.doLoadChanges(VcsChangesLoader.java:68)
at jetbrains.buildServer.vcs.impl.VcsChangesLoader.tryLoadChanges(VcsChangesLoader.java:67)
at jetbrains.buildServer.serverSide.impl.VcsModificationChecker$CollectChangesAction$1.run(VcsModificationChecker.java:20)
at jetbrains.buildServer.util.NamedThreadFactory.executeWithNewThreadName(NamedThreadFactory.java:76)
at jetbrains.buildServer.serverSide.impl.VcsModificationChecker$CollectChangesAction.run(VcsModificationChecker.java:3)
at java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1626)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: org.eclipse.jgit.errors.TransportException: https://bitbucket.org/...: git-upload-pack not permitted
at org.eclipse.jgit.transport.TransportHttp.connect(TransportHttp.java:517)
at org.eclipse.jgit.transport.TransportHttp.openFetch(TransportHttp.java:315)
at jetbrains.buildServer.buildTriggers.vcs.git.GitVcsSupport.getRemoteRefs(GitVcsSupport.java:493)
at jetbrains.buildServer.buildTriggers.vcs.git.GitVcsSupport.getRemoteRefs(GitVcsSupport.java:470)
... 37 more
org.eclipse.jgit.errors.TransportException: https://bitbucket.org/...: git-upload-pack not permitted
at org.eclipse.jgit.transport.TransportHttp.connect(TransportHttp.java:517)
at org.eclipse.jgit.transport.TransportHttp.openFetch(TransportHttp.java:315)
at jetbrains.buildServer.buildTriggers.vcs.git.GitVcsSupport.getRemoteRefs(GitVcsSupport.java:493)
at jetbrains.buildServer.buildTriggers.vcs.git.GitVcsSupport.getRemoteRefs(GitVcsSupport.java:470)
at jetbrains.buildServer.buildTriggers.vcs.git.GitVcsSupport.lambda$getCurrentState$0(GitVcsSupport.java:180)
at jetbrains.buildServer.buildTriggers.vcs.git.RepositoryManagerImpl.runWithDisabledRemove(RepositoryManagerImpl.java:256)
at jetbrains.buildServer.buildTriggers.vcs.git.GitVcsSupport.getCurrentState(GitVcsSupport.java:176)
at jetbrains.buildServer.buildTriggers.vcs.git.GitVcsSupport.getCurrentState(GitVcsSupport.java:171)
at jetbrains.buildServer.buildTriggers.vcs.git.GitCollectChangesPolicy.getCurrentState(GitCollectChangesPolicy.java:113)
at jetbrains.vcs.api.services.impl.RepositoryStateServiceProvider$1.getCurrentState(RepositoryStateServiceProvider.java:6)
at jetbrains.buildServer.vcs.impl.VcsRootInstanceImpl.lambda$null$0(VcsRootInstanceImpl.java:114)
at jetbrains.buildServer.serverSide.impl.BaseAccessChecker.runWithDisabledCheck(BaseAccessChecker.java:62)
at jetbrains.buildServer.serverSide.impl.SecondaryNodeSecurityManager.runSafeNetworkOperation(SecondaryNodeSecurityManager.java:34)
at jetbrains.buildServer.serverSide.ReadOnlyRestrictor.doReadOnlyNetworkOperation(ReadOnlyRestrictor.java:4)
at jetbrains.buildServer.vcs.impl.VcsRootInstanceImpl.lambda$getCurrentState$1(VcsRootInstanceImpl.java:135)
at jetbrains.buildServer.serverSide.impl.BaseAccessChecker.runWithDisabledCheck(BaseAccessChecker.java:62)
at jetbrains.buildServer.serverSide.impl.SecondaryNodeSecurityManager.executeSafeCommandLine(SecondaryNodeSecurityManager.java:7)
at jetbrains.buildServer.serverSide.ReadOnlyRestrictor.doReadOnlyCommandLine(ReadOnlyRestrictor.java:6)
at jetbrains.buildServer.vcs.impl.VcsRootInstanceImpl.getCurrentState(VcsRootInstanceImpl.java:58)
at jetbrains.buildServer.vcs.impl.VcsChangesStatesCollector$CurrentStateOperation.call(VcsChangesStatesCollector.java:2)
at jetbrains.buildServer.vcs.impl.VcsChangesStatesCollector$CurrentStateOperation.call(VcsChangesStatesCollector.java:1)
at jetbrains.buildServer.vcs.VcsOperationProgressProviderImpl.runWithProgress(VcsOperationProgressProviderImpl.java:27)
at jetbrains.buildServer.vcs.impl.VcsChangesStatesCollector.getCurrentState(VcsChangesStatesCollector.java:103)
at jetbrains.buildServer.vcs.impl.VcsChangesStatesCollector.lambda$null$1(VcsChangesStatesCollector.java:53)
at jetbrains.buildServer.util.NamedThreadFactory.executeWithNewThreadName(NamedThreadFactory.java:76)
at jetbrains.buildServer.vcs.impl.VcsChangesStatesCollector.lambda$getCollectStatesTasks$2(VcsChangesStatesCollector.java:108)
at jetbrains.buildServer.vcs.impl.ImmediateFutureExecService$2.call(ImmediateFutureExecService.java:4)
at jetbrains.buildServer.serverSide.impl.ImmediateFuture.get(ImmediateFuture.java:59)
at jetbrains.buildServer.serverSide.impl.ImmediateFuture.get(ImmediateFuture.java:68)
at jetbrains.buildServer.vcs.impl.VcsChangesStatesCollector.collectStatesForAllRoots(VcsChangesStatesCollector.java:6)
at jetbrains.buildServer.vcs.impl.VcsChangesStatesCollector.getCurrentStateSnapshot(VcsChangesStatesCollector.java:90)
at jetbrains.buildServer.vcs.impl.VcsChangesFetcher.getStateAndCreateChangesCollectingTasks(VcsChangesFetcher.java:26)
at jetbrains.buildServer.vcs.impl.VcsChangesLoader.doLoadChanges(VcsChangesLoader.java:68)
at jetbrains.buildServer.vcs.impl.VcsChangesLoader.tryLoadChanges(VcsChangesLoader.java:67)
at jetbrains.buildServer.serverSide.impl.VcsModificationChecker$CollectChangesAction$1.run(VcsModificationChecker.java:20)
at jetbrains.buildServer.util.NamedThreadFactory.executeWithNewThreadName(NamedThreadFactory.java:76)
at jetbrains.buildServer.serverSide.impl.VcsModificationChecker$CollectChangesAction.run(VcsModificationChecker.java:3)
at java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1626)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)

Hi,

thanks for the stacktrace. It indicates clearly that the issue is happening server side, and not on the clients, so we can focus on locating the problem on the server. There would seem to be a few possibilities:

-The server hasn't properly updated its object instances with the new data and is being reused at some point. You could probably restart the teamcity server and it should fix the issue.

-The server has cached some of the data and is used an old cache on some instances. This should also be fixed with a restart.

-You created a copy of the VCS Root when changing the parameters and didn't upgrade the other instances of the VCS Root with the new data. This is weird because then it shouldn't fail or work, but might happen on some situations.

-The remote server is misbehaving with the connection.

In this case I'd recommend first checking that you have properly updated the password on every instance of the VCS Root and not just on some of them. Then, restarting the server, if you haven't done it already, as it could clear a few of the possible issues. If that also doesn't help, clearing the related caches in the <data directory>/system/caches folder could help.

If that still doesn't help, I'd recommend creating a new VCS Root with the appropriate data pointing at the same server and checking whether that one fails as well. If it still fails, it's very likely an error in the remote server. I'd recommend checking with the server's logs to ensure that everything is working correctly.

Restarted the server (a few times) still seeing the same issue
My projects are all using the one VCS Root.  This is the one I have edited.  Is it worth recreating this?

Will recheck everything on the Git server, but this has only happened when I changed the password and is not affecting anything else

Now seeing the following

Cannot run git garbage collection using git at path 'git'. It is recommended to perform garbage collection in git repositories periodically to improve performance of changes collection. 
Please install git client on the TeamCity server machine and specify a path to it in the teamcity.server.git.executable.path internal property . 

Error details: 'git version' command failed. exception: Cannot run program "git" (in directory "C:\ProgramData\JetBrains\TeamCity\system\caches\git"): CreateProcess error=2, The system cannot find the file specified exit code: -1 

Hi,

first of all, I'd recommend addressing the problem in the message using the solution it proposes. It seems like TeamCity is using its internal library instead of a local installation of git. While the internal library is meant to cover most use cases, it cannot run git garbage collection yet, so you would need to install git onto the server for it. Setting the property will also make teamcity use the git executable for most git operations. It would also be useful if you would try afterwards whether the credentials-issue still happens.

Did that.  Now it fails at the first step:

Failed to perform checkout on agent: '"C:\Program Files\Git\bin\git.exe" -c core.askpass=C:\temp\buildTmp\pass5170668754657682569.bat -c credential.helper= -c credential.helper=C:/temp/buildTmp/credHelper5844141521566351758.bat checkout -q -f develop' command failed.
exit code: 128
stderr: fatal: cannot create directory at 'node_modules/gulp-foreach/node_modules/gulp-util/node_modules/dateformat/node_modules/meow/node_modules/normalize-package-data/node_modules/validate-npm-package-license/node_modules/spdx-correct/node_modules/spdx-license-ids': Filename too long 

Trying solution from here
https://stackoverflow.com/questions/38087824/unable-to-add-node-module-folder-to-git

$  git config --global core.autocrlf false

Hi,

just a quick comment on the solution from stack overflow. Please pay attention that roughly everybody is saying that they shouldn't be adding "node_modules" to git. The error you are getting is obviously because the path is way too long, and the OS cannot support such a long path. Removing node_modules and leaving package.json on the repo instead should get rid of that error without having to modify the autocrlf.

Yeah, unfortunately I've inherited this codebase.  fixing this is on the list, however it's not the cause of the issues I'm seeing here.

-The remote server is misbehaving with the connection.

Have tried with different log-in credentials.  No issue.  Looks like it might be something on the account settings.  Investigating the Bitbucket end of stuff

Thanks

Similar issue. It seems it sometimes appears, sometimes disappears. It started happening after a server restart.

Following restarts of the server and TC services didn't help. Tried changing the username and password used to access repositories - same thing.

Tried deleting cache dir as proposed - no results.

TC 2018.2.4

Part of the stack trace:

jetbrains.buildServer.VCS - Error occurred in test connection: jetbrains.buildServer.vcs.VcsException: List remote refs failed: org.eclipse.jgit.errors.TransportException: http://**********/*****/web-front-end.git: git-upload-pack not permitted
at jetbrains.buildServer.buildTriggers.vcs.git.OperationContext.wrapException(OperationContext.java:185)
at jetbrains.buildServer.buildTriggers.vcs.git.GitVcsSupport.getRemoteRefs(GitVcsSupport.java:475)
at jetbrains.buildServer.buildTriggers.vcs.git.GitVcsSupport.lambda$getCurrentState$0(GitVcsSupport.java:180)
at jetbrains.buildServer.buildTriggers.vcs.git.RepositoryManagerImpl.runWithDisabledRemove(RepositoryManagerImpl.java:256)
at jetbrains.buildServer.buildTriggers.vcs.git.GitVcsSupport.getCurrentState(GitVcsSupport.java:176)
at jetbrains.buildServer.buildTriggers.vcs.git.TestConnectionCommand.checkFetchConnection(TestConnectionCommand.java:95)
at jetbrains.buildServer.buildTriggers.vcs.git.TestConnectionCommand.testConnection(TestConnectionCommand.java:68)
at jetbrains.buildServer.buildTriggers.vcs.git.GitVcsSupport.lambda$testConnection$2(GitVcsSupport.java:318)
at jetbrains.buildServer.buildTriggers.vcs.git.RepositoryManagerImpl.runWithDisabledRemove(RepositoryManagerImpl.java:256)
at jetbrains.buildServer.buildTriggers.vcs.git.GitVcsSupport.testConnection(GitVcsSupport.java:315)
at jetbrains.vcs.api.services.impl.TestConnectionServiceProvider$1.testConnection(TestConnectionServiceProvider.java:2)

Hi,

While the "git-upload-pack not permitted" is common to the issue at hand here, saying that this is the same issue is difficult, as that is a rather generic error that can come from a wide array of causes, from issues on the local server, on the cache, on the remote server, etc.

If it's a server issue and removing the cache and restarting didn't help, that makes it even more strange. I'd test connecting with a different user, I'd check the nested errors in the stacktrace for further info on what is going on, although often it's not much more helpful. I can also recommend trying to set the git executable path internal property: https://www.jetbrains.com/help/teamcity/git.html#Git-InternalProperties

If setting this parameter (and restarting) the issue persists, I would make sure that the remote repository is working properly and that the error doesn't come from the content of the repository (such as the error mentioned above, where one of the issues was that the filename was way too long)

All of these steps, including internal properties, have been tried.  The user worked until the password was changed.  Changing the user works

The filename length error was unrelated to this

Hi Tony,

thanks for following up. If the same user would change again their password, would it work again? Does the password have special characters? If it's clear that with another user it works, it clearly seems to be tied with either the user on the remote server, or with how teamcity manages the credentials. Maybe an issue with encoding while storing it could produce this issue.

No special characters.  But, worth a try.  Let's see what happens

Nope.  Still the same

If modifying the user's password doesn't work but it works for different users, it looks like a configuration issue for the user on the remote server.

Could you try creating a new VCS Root for the same repository (do not remove the old one) and assign the same user and see whether that one works? The only option I have left for TeamCity is that it somehow stored some intermediate cache for the credentials and that it's being misused due to some other issue.

Just hit the same problem.   In our case we had multiple VCS roots using the same git repo and user, but had set the new pssword on only some of the VCS roots, and some still had the old password.  Since TC checks the repo fairly frequently it was using the old password often enough to cause the git repo to lockout the Teamcity server's IP address.  Changing the password on ALL of the VCS roots with this username, and resetting the git IP ban fixed it.   I think some git implementations might lock out an individual user that has too many password failures.  This lockout can reset after 30 mins or so, so you might get the intermittent effect reported above??