Thanks for the detailed report.
Fixed in c5bd24f to display that the profile is age restricted.
Have a nice day!
One solution would be to apply the authentication to URLs starting with /u/ and /p/. Then /imageproxy will go through without any problems.
Also consider if altering website_origin - which affects the domain name before /imageproxy in the RSS feed - could help you.
Are you selfhosting? What environment are you running this in?
Oh, thanks for the information in your report and how you formatted it. That was really helpful to me and helped me track down what was happening very quickly.
Nothing I can do.
For pages after the first page on the IGTV timeline, Instagram does not provide the video URL in the initial request. It does provide a lot of other data, like the thumbnail URL, caption, and video length, but not the URL to the video itself.
Bibliogram recognises that it has a video post without a video URL, and tries to self-update that post's data by requesting more data about the post from the post's page. This request almost always fails to being blocked by Instagram, since Instagram for whatever reason has differently implemented rate limits for posts than it does for timeline pages.
Bibliogram recognises that the self-update failed, but tries to continue anyway, in the hope that there may still be some useful information from the post's initial data that it can display to the user. In fact, there is some useful data, like the post's caption and publish date, which it does display. But it couldn't get the video URL, so that's stored as the
undefinedplaceholder in memory, so it uses
undefinedas the URL, so the video appears to not load, tada.
Hope this helps.