search

zedeus / nitter

Alternative Twitter front-end
https://nitter.net
GNU Affero General Public License v3.0
9.95k stars 529 forks source link

Images sometimes not loading, and returns “tweet not found” or 404, even though they exists #709

Closed ArchivingToolsForWBM closed 1 year ago

ArchivingToolsForWBM commented 1 year ago

This seems to happen at random, on any tweet on twitter that have images on them and have occurred on my chrome browser on my iphone SE, on 9am EST.

When archiving to the WBM, this happens extremely often.

zedeus commented 1 year ago

What instance? nitter.net does have some issues, I'd recommend using another one.

ArchivingToolsForWBM commented 1 year ago

It’s hard to reproduce. I didn’t get the message “Instance have been rate limited”.

ghost commented 1 year ago

I get the exact same issue. Even if just viewing on nitter.net.

ArchivingToolsForWBM commented 1 year ago

Sample: https://nitter.net/yyy_m_z image Example tweet: https://nitter.net/yyy_m_z/status/1549961498617085952#m image I had to keep refreshing to get the images to load properly. Annoying.

ArchivingToolsForWBM commented 1 year ago

image URL in question: https://nitter.net/pic/orig/media%2FFMRo458aIAACf8S.jpg

zedeus commented 1 year ago

Please use another instance, nitter.net is unstable at the moment.

owovin commented 1 year ago

I've had this problem on a custom self-hosted instance, images just will not load anymore, no matter what. the rest works just fine, and twitter.com for the rest of my network does not fail. Is there any way i can troubleshoot or figure out a fix for the problem? I can provide logs if needed

IceCereal commented 1 year ago

Please use another instance, nitter.net is unstable at the moment.

@zedeus Is there some kind of (semi-live) way to know this online instead of going through Github issues or joining the matrix channel? Maybe something like nitter.net/status which reports activities.

Thanks!

owovin commented 1 year ago

Update: the instance fixed itself when i disabled ipv6 on the server (i lack ipv6 on the ISP side, lack of blocks). seems unrelated. good luck though!

anshumankmr commented 1 year ago

I had found the same issue myself, For example, this tweet: On Nitter.net: https://nitter.net/GrizzliesPR/status/1608153238292897796 Nitter.net

On Nitter.CZ https://nitter.cz/GrizzliesPR/status/1608153238292897796 nitter.cz

Original Tweet: https://twitter.com/GrizzliesPR/status/1608153238292897796 image

zedeus commented 1 year ago

nitter.net is very unstable due to odd recurring rate limits.