Describe the bug
After setting up Large Media for repo, I am unable to work (push, pull, clone etc) with the remote repo if LFS items are added in the media folder.
Error in terminal from git pull after uploading an image via remote NetlifyCMS admin:
Downloading static/images/cms/kendal-james-1413779-unsplash.jpg (3.3 MB)
Error downloading object: static/images/cms/kendal-james-1413779-unsplash.jpg (35441d0): Smudge error: Error downloading static/images/cms/kendal-james-1413779-unsplash.jpg (35441d0b9617530a17efd169d2e32fcdc4d0de248aeff608b1f04911c6fcd185): batch response: Expected json type, got: "text/html"
Errors logged to /Users/ME/Sites/my-site/.git/lfs/logs/20190307T172529.144713.log
Use `git lfs logs last` to view the log.
error: external filter 'git-lfs filter-process' failed
fatal: static/images/cms/kendal-james-1413779-unsplash.jpg: smudge filter lfs failed
First, rewinding head to replay your work on top of it...
Downloading static/images/cms/kendal-james-1413779-unsplash.jpg (3.3 MB)
Error downloading object: static/images/cms/kendal-james-1413779-unsplash.jpg (35441d0): Smudge error: Error downloading static/images/cms/kendal-james-1413779-unsplash.jpg (35441d0b9617530a17efd169d2e32fcdc4d0de248aeff608b1f04911c6fcd185): batch response: Expected json type, got: "text/html"
Errors logged to /Users/ME/Sites/my-site/.git/lfs/logs/20190307T172530.067361.log
Use `git lfs logs last` to view the log.
error: external filter 'git-lfs filter-process' failed
To Reproduce
.netlify/state.json and .gitattributes) Applicable Versions:
CMS configuration
backend:
name: git-gateway
accept_roles: #optional - accepts all users if left out
- admin
- editor
media_folder: "static/images/cms"
public_folder: "/images/cms"
collections:
...
Additional Info:


I have narrowed down this issue is occurring due to the Netlify site having a global password. Is this a known limitation? The hope has been to be able to have a password protected staging version.
i encountered the same problem
Also ran into this. Removing the password fixes it but that seems like a problem for a project in pre-production still.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Most helpful comment
I have narrowed down this issue is occurring due to the Netlify site having a global password. Is this a known limitation? The hope has been to be able to have a password protected staging version.