Slow discourse with broken avatars

Hi everyone,

I am facing this weird issue where my discourse has gone really slow and unusable. While looking at the logs I see below issues. I am not sure if that’s the problem with the network or openssl version or something. For longer threads it keeps on loading forever and avatars are broken:

Message (75 copies reported)

Failed to process hijacked response correctly : Net::OpenTimeout

Backtrace

/usr/local/lib/ruby/2.7.0/net/protocol.rb:41:in `ssl_socket_connect'
/usr/local/lib/ruby/2.7.0/net/http.rb:1009:in `connect'
/usr/local/lib/ruby/2.7.0/net/http.rb:943:in `do_start'
/usr/local/lib/ruby/2.7.0/net/http.rb:932:in `start'
/usr/local/lib/ruby/2.7.0/net/http.rb:606:in `start'
/var/www/discourse/lib/final_destination.rb:434:in `safe_session'
/var/www/discourse/lib/final_destination.rb:385:in `safe_get'
/var/www/discourse/lib/final_destination.rb:134:in `get'
/var/www/discourse/lib/file_helper.rb:55:in `download'
/var/www/discourse/app/controllers/user_avatars_controller.rb:158:in `proxy_avatar'

Env

HTTP HOSTS: 10.32.9.21

Also, please find the production.log file attached, which is giving errors connecting to redis

Is this a Discourse official Standard Installation?

Did something change recently?

Yes it’s a standard installation, i installed the latest version and then used backup from old instance to restore.

Also in production.log it’s giving error in connecting to redis.

Then that’s where you’re problem lies. I guess you’ve rebuilt recently? Have disk space and Ram?

This warning also appear on our forum sometimes. I think it maybe a cache or CDN issue or something like this :thinking: Sometimes when a new user use social login to to register it takes too long to fetch the avatar and this hijack warning appear in logs. If a long time no see user log in it also appear because I think their profile avatar is not in cache :thinking: But after few minutes or refresh the profile photo appear correctly.

There’s ample of space and RAM available. I am not sure what’s preventing to connect to redis.

This is happening for almost all the users.