I have just setup a new installation of soft serve to handle a locally avaliable (in my server) storage for my repos, as backup (mostly), but two that use LFS to be the main/origin repos for our work.

I have tried with the default configuration for the LFS uploads and for some reason I can't understand, I get this kind of errors for, apparently, some of the files, not all of them:

Pushing to ssh://ts-srv-code:23231/componentes.git
Uploading LFS objects: 51% (2179/4300), 2.8 GB | 11 MB/s, done.
Authorization error: http://ts-srv-code:23232/componentes.git/info/lfs/objects/basic/verify
Check that you have proper access to the repository
batch response: Authorization error: http://ts-srv-code:23232/componentes.git/info/lfs/objects/batch
Check that you have proper access to the repository
batch response: Authorization error: http://ts-srv-code:23232/componentes.git/info/lfs/objects/batch
Check that you have proper access to the repository

In the soft serve window I can see this errors:

2025-12-29 17:08:12 ←[1;38;5;204mERRO←[m ←[1;2mhttp.lfs-basic:←[m error creating object ←[2mmethod←[m←[2m=←[mPUT ←[2mpath←[m←[2m=←[mcomponentes.git/info/lfs/objects/basic/c2d5be54de28c4e836cfbd5454a04aac9ea33d83cdc7bd564273c82e27a3a488 ←[2maddr←[m←[2m=←[m10.77.122.10:55120 ←[2moid←[m←[2m=←[mc2d5be54de28c4e836cfbd5454a04aac9ea33d83cdc7bd564273c82e27a3a488 ←[2merr←[m←[2m=←[m"database is locked (5) (SQLITE_BUSY)"
2025-12-29 17:08:12 ←[1;38;5;204mERRO←[m ←[1;2mhttp.lfs-basic:←[m error creating object ←[2mmethod←[m←[2m=←[mPUT ←[2mpath←[m←[2m=←[mcomponentes.git/info/lfs/objects/basic/481004766902f689916c7c5de4adf41046ffc6b84bedb361a997c9b839b8f52b ←[2maddr←[m←[2m=←[m10.77.122.10:55144 ←[2moid←[m←[2m=←[m481004766902f689916c7c5de4adf41046ffc6b84bedb361a997c9b839b8f52b ←[2merr←[m←[2m=←[m"database is locked (5) (SQLITE_BUSY)"
2025-12-29 17:08:15 ←[1;38;5;204mERRO←[m ←[1;2mhttp.lfs-basic:←[m error creating object ←[2mmethod←[m←[2m=←[mPUT ←[2mpath←[m←[2m=←[mcomponentes.git/info/lfs/objects/basic/088055fef8de9013a587d516e09667d688682205a2744da4fddbfea6403067ec ←[2maddr←[m←[2m=←[m10.77.122.10:55150 ←[2moid←[m←[2m=←[m088055fef8de9013a587d516e09667d688682205a2744da4fddbfea6403067ec ←[2merr←[m←[2m=←[m"database is locked (5) (SQLITE_BUSY)"
2025-12-29 17:08:18 ←[1;38;5;204mERRO←[m ←[1;2mhttp.lfs-basic:←[m error creating object ←[2mmethod←[m←[2m=←[mPUT ←[2mpath←[m←[2m=←[mcomponentes.git/info/lfs/objects/basic/417b1146eb0c4431f3b97efb6995b6004c23359bda5f9eb472263c56e38b9be9 ←[2maddr←[m←[2m=←[m10.77.122.10:55161 ←[2moid←[m←[2m=←[m417b1146eb0c4431f3b97efb6995b6004c23359bda5f9eb472263c56e38b9be9 ←[2merr←[m←[2m=←[m"database is locked (5) (SQLITE_BUSY)"

Which I assume is the origin of the error reported to the client. This when using the http transport.

If I enable the ssh transport for LFS then on the server I can see this kind of errors:

2025-12-29 17:17:03 ←[1;38;5;204mERRO←[m ←[1;2mlfs-transfer:←[m error renaming object: rename e:\Git-SoftServe-Data\lfs\2\incomplete\66cfce891e805c1e703e9dc1e3b59fba5ff2603bc23af4d78b0a28b274457f75e2f067d847ddef90d05204c1 e:\Git-SoftServe-Data\lfs\2\objects\66\cf\66cfce891e805c1e703e9dc1e3b59fba5ff2603bc23af4d78b0a28b274457f75: El proceso no tiene acceso al archivo porque está siendo utilizado por otro proceso.
2025-12-29 17:17:03 ←[1;38;5;204mERRO←[m ←[1;2mlfs-transfer:←[m error renaming object: rename e:\Git-SoftServe-Data\lfs\2\incomplete\686e6dc53a4952c3b802f154e65e2a9ba3a26bee04e80f785164c416c7f90c2bb9792bc20115ab8513cdb94b e:\Git-SoftServe-Data\lfs\2\objects\68\6e\686e6dc53a4952c3b802f154e65e2a9ba3a26bee04e80f785164c416c7f90c2b: El proceso no tiene acceso al archivo porque está siendo utilizado por otro proceso.
2025-12-29 17:17:04 ←[1;38;5;204mERRO←[m ←[1;2mlfs-transfer:←[m error renaming object: rename e:\Git-SoftServe-Data\lfs\2\incomplete\69a9086c3dbaa672fb7ed0b1360875effa58c60291eb72fcb7be2b14f11100c286fdf215ff04487d0ac9d89a e:\Git-SoftServe-Data\lfs\2\objects\69\a9\69a9086c3dbaa672fb7ed0b1360875effa58c60291eb72fcb7be2b14f11100c2: El proceso no tiene acceso al archivo porque está siendo utilizado por otro proceso.
2025-12-29 17:17:04 ←[1;38;5;204mERRO←[m ←[1;2mlfs-transfer:←[m error renaming object: rename e:\Git-SoftServe-Data\lfs\2\incomplete\69b8d1aeb934d0b92283db83be58eb622d9459838d21734c4f4709fc264d5ff568190166ae0dac3cf7fe26bf e:\Git-SoftServe-Data\lfs\2\objects\69\b8\69b8d1aeb934d0b92283db83be58eb622d9459838d21734c4f4709fc264d5ff5: El proceso no tiene acceso al archivo porque está siendo utilizado por otro proceso.
2025-12-29 17:17:05 ←[1;38;5;204mERRO←[m ←[1;2mlfs-transfer:←[m error renaming object: rename e:\Git-SoftServe-Data\lfs\2\incomplete\6db499a44ebada067871379f810b787a658f7d98ac84f3adc3f31853de2386e12fa7a931926d000be70638f6 e:\Git-SoftServe-Data\lfs\2\objects\6d\b4\6db499a44ebada067871379f810b787a658f7d98ac84f3adc3f31853de2386e1: El proceso no tiene acceso al archivo porque está siendo utilizado por otro proceso.
2025-12-29 17:17:06 ←[1;38;5;204mERRO←[m ←[1;2mlfs-transfer:←[m error renaming object: rename e:\Git-SoftServe-Data\lfs\2\incomplete\701d9d62b0093ee24f1e52ebb7b8bf17f98b0b454fa954c3ca415efe0a4262936813300eb4dfa34d4f503b46 e:\Git-SoftServe-Data\lfs\2\objects\70\1d\701d9d62b0093ee24f1e52ebb7b8bf17f98b0b454fa954c3ca415efe0a426293: El proceso no tiene acceso al archivo porque está siendo utilizado por otro proceso.

I am the only user connected to the server, so if there are some locking issues is not because of other users connecting or pushing changes to the server.

Is there anything I have to enable or change to succeed pushing my repo here? Or it's just retrying until it works?

Environment (please complete the following information):

• Server: Windows Server 2022, Version 21H2
• Client: I have tried with Fork and directly with git from the command line. Same behaviour. Both on Windows, with git 2.52.0.windows.1 and git-lfs 3.7.1