[Support Guide] Troubleshooting your Netlify Large Media Configuration

Support Support Guides
,
210

Thanks for the quick help Luke,

This happens in the native terminal (this is Mac btw) which is zsh, my preferred terminal Warp which is zsh, the terminal in VScode which is zsh, and also blocks pushing with github desktop (that just hangs since it’s waiting for input so it doesn’t do anything at all).

GIT_TRACE=true GIT_CURL_VERBOSE=true git lfs push --all origin
10:10:29.679927 git.c:750 trace: exec: git-lfs push --all origin
10:10:29.680485 run-command.c:655 trace: run_command: git-lfs push --all origin
10:10:29.688138 trace git-lfs: exec: git 'version'
10:10:29.693850 trace git-lfs: exec: git '-c' 'filter.lfs.smudge=' '-c' 'filter.lfs.clean=' '-c' 'filter.lfs.process=' '-c' 'filter.lfs.required=false' 'remote'
10:10:29.698680 trace git-lfs: exec: git '-c' 'filter.lfs.smudge=' '-c' 'filter.lfs.clean=' '-c' 'filter.lfs.process=' '-c' 'filter.lfs.required=false' 'rev-parse' 'HEAD' '--symbolic-full-name' 'HEAD'
10:10:29.702680 trace git-lfs: exec: git '-c' 'filter.lfs.smudge=' '-c' 'filter.lfs.clean=' '-c' 'filter.lfs.process=' '-c' 'filter.lfs.required=false' 'rev-parse' '--git-dir' '--show-toplevel'
10:10:29.706598 trace git-lfs: exec: git 'config' '--includes' '-l'
10:10:29.710145 trace git-lfs: exec: git 'rev-parse' '--is-bare-repository'
10:10:29.713659 trace git-lfs: exec: git 'config' '--includes' '-l' '-f' '/Users/claire/git/SolidPort/.lfsconfig'
10:10:29.717310 trace git-lfs: Upload refs [] to remote origin
10:10:29.717353 trace git-lfs: exec: git '-c' 'filter.lfs.smudge=' '-c' 'filter.lfs.clean=' '-c' 'filter.lfs.process=' '-c' 'filter.lfs.required=false' 'show-ref'
10:10:29.721889 trace git-lfs: exec: git '-c' 'filter.lfs.smudge=' '-c' 'filter.lfs.clean=' '-c' 'filter.lfs.process=' '-c' 'filter.lfs.required=false' 'show-ref'
10:10:29.725564 trace git-lfs: exec: git '-c' 'filter.lfs.smudge=' '-c' 'filter.lfs.clean=' '-c' 'filter.lfs.process=' '-c' 'filter.lfs.required=false' 'ls-remote' '--heads' '--tags' '-q' 'origin'
10:10:30.514514 trace git-lfs: tq: running as batched queue, batch size of 100
10:10:30.514859 trace git-lfs: run_command: git rev-list --objects --do-walk --stdin --
10:10:30.514872 trace git-lfs: exec: git '-c' 'filter.lfs.smudge=' '-c' 'filter.lfs.clean=' '-c' 'filter.lfs.process=' '-c' 'filter.lfs.required=false' 'rev-list' '--objects' '--do-walk' '--stdin' '--'
10:10:30.517428 trace git-lfs: exec: git '-c' 'filter.lfs.smudge=' '-c' 'filter.lfs.clean=' '-c' 'filter.lfs.process=' '-c' 'filter.lfs.required=false' 'cat-file' '--batch-check'
10:10:30.519232 trace git-lfs: exec: git '-c' 'filter.lfs.smudge=' '-c' 'filter.lfs.clean=' '-c' 'filter.lfs.process=' '-c' 'filter.lfs.required=false' 'rev-parse' '--git-common-dir'
10:10:30.555867 trace git-lfs: tq: sending batch of size 1
10:10:30.556014 trace git-lfs: api: batch 1 files
10:10:30.556120 trace git-lfs: creds: git credential fill ("https", "[bae50d02-4a92-4246-b9e5-60627261104d.netlify.app](http://bae50d02-4a92-4246-b9e5-60627261104d.netlify.app)", "")
10:10:30.556146 trace git-lfs: exec: git 'credential' 'fill'
Enter basic credentials for '[https://bae50d02-4a92-4246-b9e5-60627261104d.netlify.app/](https://bae50d02-4a92-4246-b9e5-60627261104d.netlify.app/)':
Username: ^C

10:10:39.278246 trace git-lfs: credential fill error: `git credential fill` error: signal: interrupt
10:10:39.278233 trace git-lfs: filepathfilter: creating pattern ".git" of type gitignore
10:10:39.278391 trace git-lfs: api error: Git credentials for [https://bae50d02-4a92-4246-b9e5-60627261104d.netlify.app/.netlify/large-media](https://bae50d02-4a92-4246-b9e5-60627261104d.netlify.app/.netlify/large-media) not found:
credential fill errors:
`git credential fill` error: signal: interrupt
10:10:39.278445 trace git-lfs: filepathfilter: creating pattern "**/.git" of type gitignore
batch response: Git credentials for [https://bae50d02-4a92-4246-b9e5-60627261104d.netlify.app/.netlify/large-media](https://bae50d02-4a92-4246-b9e5-60627261104d.netlify.app/.netlify/large-media) not found:
credential fill errors:
`git credential fill` error: signal: interrupt
Uploading LFS objects: 0% (0/1), 0 B | 0 B/s, done.
10:10:39.278649 trace git-lfs: filepathfilter: accepting "tmp"

git config -l | grep netlify
include.path=/Users/name/Library/Preferences/netlify/helper/git-config
credential.helper=netlify
credential.[https://bae50d02-4a92-4246-b9e5-60627261104d.netlify.app.provider](https://bae50d02-4a92-4246-b9e5-60627261104d.netlify.app.provider)=generic
lfs.[https://bae50d02-4a92-4246-b9e5-60627261104d.netlify.app/.netlify/large-media.access=basic](https://bae50d02-4a92-4246-b9e5-60627261104d.netlify.app/.netlify/large-media.access=basic)
lfs.[https://bae50d02-4a92-4246-b9e5-60627261104d.netlify.app/.netlify/large-media.locksverify=false](https://bae50d02-4a92-4246-b9e5-60627261104d.netlify.app/.netlify/large-media.locksverify=false)
credential.helper=netlify

Here’s the output to that command and the relevant git config entries.

212

Hey there, @ekwoka :wave:

Thanks for your patience here-- we haven’t forgotten about you! We will follow up soon with more thoughts and next steps.

214

Hi, @ekwoka and sorry for the delay. While the git config -l | grep netlify contains some useful information, it is hiding other details. For example, I would need to see every credential.helper link to troubleshoot.

On MacOS there are usually three lines like so:

credential.helper=
credential.helper=netlify
credential.helper=osxkeychain

This might have preceding or following entries as well. Seeing all lines would be helpful.

Also, these links do not appear correct to me:

credential.[https://bae50d02-4a92-4246-b9e5-60627261104d.netlify.app.provider](https://bae50d02-4a92-4246-b9e5-60627261104d.netlify.app.provider)=generic
lfs.[https://bae50d02-4a92-4246-b9e5-60627261104d.netlify.app/.netlify/large-media.access=basic](https://bae50d02-4a92-4246-b9e5-60627261104d.netlify.app/.netlify/large-media.access=basic)
lfs.[https://bae50d02-4a92-4246-b9e5-60627261104d.netlify.app/.netlify/large-media.locksverify=false](https://bae50d02-4a92-4246-b9e5-60627261104d.netlify.app/.netlify/large-media.locksverify=false)

The URLs are in markdown format above. The should look like this instead:

lfs.https://bae50d02-4a92-4246-b9e5-60627261104d.netlify.app/.netlify/large-media.access=basic
lfs.https://bae50d02-4a92-4246-b9e5-60627261104d.netlify.app/.netlify/large-media.locksverify=false

I don’t know if your gitconfig actually looks like this or is the information was mangled by the forum software. If the raw text has the markdown version, that must be changed.

The logs have the same format:

batch response: Git credentials for [https://bae50d02-4a92-4246-b9e5-60627261104d.netlify.app/.netlify/large-media](https://bae50d02-4a92-4246-b9e5-60627261104d.netlify.app/.netlify/large-media) not found:

This makes me concerned the gitconfig itself contains this invalid format. If so, please convert it to the correct format.

Also, this line is unknown to me:

credential.[https://bae50d02-4a92-4246-b9e5-60627261104d.netlify.app.provider](https://bae50d02-4a92-4246-b9e5-60627261104d.netlify.app.provider)=generic

I’ve not see that entry before and I have no entries with generic for my Large Media test site:

$ git config -l | grep generic
$

If you could make the URL changes (from markdown to a normal URL) and send the unredacted/unfiltered git config -l output that will tell us more. (The URL changes alone might be all that is required to resolve this.)

215

@luke The markdown stuff just came from the reply by email conversion to forum post, since it saw the link it translated it awkwardly.

Here’s the credential list:

credential.helper=osxkeychain
credential.helper=
credential.helper=netlify
credential.helper=
credential.helper=/usr/local/share/gcm-core/git-credential-manager-core
credential.https://dev.azure.com.usehttppath=true
credential.https://bae50d02-4a92-4246-b9e5-60627261104d.netlify.app.provider=generic

I hunted down and deleted that =generic entry but the results are the same

I did check and remove the other helper= empty entry and now it’s working.

But upon pushing, it did then remake that =generic entry, not sure why I’ve never had that before and you’ve not had it…

216

Hi, @ekwoka. Sorry for the delay as I was out of office and thank you for letting us know it is working now.

The information above does reveal an issue and, most likely, what the root cause was. (I know you fixed it but I wanted to clarify for any future readers here.)

I first want to point out the behavior of the following lines which contain only and exactly this:

credential.helper=

The lines where the credential.helper is set to the empty string have the effect of resetting or erasing all precedingcredential.helper entries. It resets the list to empty anytime it occurs.

With that is mind, what follows is an explanation of what the entries do. I’m splitting up the file in the order lines appeared. Below section I’ll explain what the lines above do with a bullet point:

credential.helper=osxkeychain
  • adds the MacOS keychain app for handling authentication credentials
credential.helper=
credential.helper=netlify
  • erases the previous settings and only add Netlify’s Git credential helper
credential.helper=
credential.helper=/usr/local/share/gcm-core/git-credential-manager-core

credential.https://dev.azure.com.usehttppath=true
credential.https://bae50d02-4a92-4246-b9e5-60627261104d.netlify.app.provider=generic

This last section is syntax I’m not familiar with but which is almost certainly something specific to the git-credential-manager.

What it appears to me has happened is that the git-credential-manager has overwritten the Netlify Git credential helper settings.

The correct settings would be something similar to this:

credential.helper=
credential.helper=netlify
credential.helper=osxkeychain
credential.helper=/usr/local/share/gcm-core/git-credential-manager-core
credential.https://dev.azure.com.usehttppath=true
credential.https://bae50d02-4a92-4246-b9e5-60627261104d.netlify.app.provider=generic
lfs.https://bae50d02-4a92-4246-b9e5-60627261104d.netlify.app/.netlify/large-media.access=basic
lfs.https://bae50d02-4a92-4246-b9e5-60627261104d.netlify.app/.netlify/large-media.locksverify=false

When you say you removed the other helper= empty entry, I’m guessing it was the one in the middle. That would likely them make the entries similar (but not identical) to the example above.

Note, the credential.helper=osxkeychain entry may be redundant. My understanding is that it is not required if you only use HTTPS (and not SSH) for remote actions when git-credential-manager is being used. If you use both HTTPS and SSH, then both osxkeychain and git-credential-manager are required.

Thanks again for letting us know it is working now and if there are any other questions, please let us know.

217

Thanks for this great post. I’m still having trouble getting large media to work on my site. I ran git lfs ls-files and it returned all the files I wish to use LFS on. I have tried netlify lm:info and all looks good, I have also run git lfs push --all origin and the console says that all assets were uploaded. However, those images do not appear in the Netlify UI, nor can I access them on my live site. Any additional help? Happy to run additional cmds and send results via email. FWIW, files on github indicate that they are hosted by LFS.

218

Hi, @brycekunkel. I’m not sure which site this is about.

I did check the Netlify account associated with the same email address as used for this support team. That account only has one site and Large Media isn’t enabled for it.

Is there some other site? If so, would you please share the site’s API ID with us here?

You can post that information publicly or you can private message (PM) that to one of our support staff. I’ve confirmed that PMs are enabled for your forum login. Please keep in mind that only one person can see the PM and this will likely mean a slower reply than posting the information publicly. Please feel free to reply to however you prefer though.

If there is no other site, the Large Media feature was removed for the site I did find by a member of our support team at your request. If you want to use Large Media for that site, you will need to enable that feature again.

Please note, using Large Media isn’t a requirement when using Git LFS. You can use Git LFS without using the Large Media feature if you want to.

If using Git LFS by itself, please remember to set the GIT_LFS_ENABLED and GIT_LFS_FETCH_INCLUDE environment variables according to your requirements (more details at the end of the section here).

219

Hi, I have followed all the steps in the docs but when I do git push it asks me for a password and the netlify creds don`t work (my bitbucket creds as well). And I also have this error after running the netlify lm:info command:

image
image891×106 4.24 KB

I tried to install it using netlify lm:install/netlify lm:setup, but it doesnt work. I also tried to log out from netlify, but it also doesnt allow me to push. Could you please help me? Thanks

223

Hi, @AnnaR. I’ve escalated this to our developers as I’m also having issues getting this to work on Windows. We will post another follow-up here as soon as we have more information.

224

Hi @AnnaR ,

Thanks for your patience. Our developers recommend using either powershell or scoop as Git’s credential helper. Could you try installing either of those and let us know if that helps allow you to push? GitHub - netlify/netlify-credential-helper: Git credential helper to use Netlify's API as authentication backend