Slow image loading

[DUOLabs333]

I noticed that loading images are very slow on my personal instance. This does not appear on nitter.net or nitter.kavin.rocks, so it may be a personal configuration issue.

[zedeus]

Is this still an issue?

[DUOLabs333]

Yes

[zedeus]

Please post some details about your setup (OS, nginx/apache/caddy/etc) and configuration

[DUOLabs333]

Running on Arch ARM, problem appears on both Arch/Firefox, MacOS/Chrome, and Android/Chrome.

nitter.conf:

[Server]
address = "127.0.0.1"
port = 2017
https = false  # disable to enable cookies when not using https
httpMaxConnections = 100
staticDir = "./public"
title = "nitter"
hostname = "nitter.test"

[Cache]
listMinutes = 240  # how long to cache list info (not the tweets, so keep it high)
rssMinutes = 10  # how long to cache rss queries
redisHost = "localhost"
redisPort = 6379
redisConnections = 20 # connection pool size
redisMaxConnections = 30
redisPassword = ""
# max, new connections are opened when none are available, but if the pool size
# goes above this, they're closed when released. don't worry about this unless
# you receive tons of requests per second

[Config]
hmacKey = "secretkey" # random key for cryptographic signing of video urls
base64Media = false # use base64 encoding for proxied media urls
tokenCount = 100
# minimum amount of usable tokens. tokens are used to authorize API requests,
# but they expire after ~1 hour, and have a limit of 187 requests.
# the limit gets reset every 15 minutes, and the pool is filled up so there's
# always at least $tokenCount usable tokens. again, only increase this if
# you receive major bursts all the time

# Change default preferences here, see src/prefs_impl.nim for a complete list
[Preferences]
theme = "Nitter"
replaceTwitter = "nitter.test"
replaceYouTube = "piped.kavin.rocks"
replaceInstagram = ""
proxyVideos = false
hlsPlayback = true
infiniteScroll = false

[zedeus]

Is it running behind a reverse proxy (e.g. nginx) or are you accessing it directly?

[DUOLabs333]

Accessing it directly, though using nginx shows the same issue.

[t3pfaffe]

Having same problems. Behind my proxy they 504 but when accessing directly, images are taking upwards of 2 minutes to load in.

[DUOLabs333]

It's much faster now. Maybe something got fixed in an update?