Large Media is a service that we don’t recommend using. I wouldn’t be surprised to hear that it is incompatible with Edge Functions, which by default drive much of our nextjs-runtime (especially around image handling in IPX).
In the end, we’ll recommend you don’t use large media today with any framework, but we won’t be able to debug it; we can help you deactivate it instead if you’d like, though, and I expect things will work better with serving your site once you aren’t using it anymore.
I was actually thinking about reaching out to disable it anyway as it’s additional complexity I’m not sure I really need, even if it did work well. I didn’t realise at the time when I enabled it that the process wasn’t reversible without manual intervention.
If you can please proceed with disabling it for my application, that would be much appreciated. Is there anything more you need from me?
We have removed the Large Media add-on from the site now.
Would you please push the commit removing .lfsconfig to the upstream repository? This will trigger a new build.
Please keep in mind that you might want to run the command below after deleting the .lfsconfig file:
git lfs push --all origin
This will sync the local repo’s LFS objects with the Git LFS service at the original Git host. It pushes any new binary blobs to their LFS service which may have been added after you moved the LFS service to Large Media.
Please let us know if there are any issues with the new build or deployed site.