# Wrong account avatar after upgrade
**URL:** https://meta.discourse.org/t/wrong-account-avatar-after-upgrade/74886
**Category:** Bug
**Created:** [2017年十一月27日 15:03 UTC](https://meta.discourse.org/t/wrong-account-avatar-after-upgrade/74886 "2017-11-27T15:03:55Z")
**Posts on this page:** 18
**Page:** 1
### Author:  [@Fouad\_Farah](https://meta.discourse.org/u/Fouad_Farah)
#### Post date: [2017年十一月27日 15:03 UTC](https://meta.discourse.org/t/wrong-account-avatar-after-upgrade/74886/1 "2017-11-27T15:03:55Z")
Hello,
I just upgraded to 1.9.0.beta14 (I had to rebuild app)
After upgrading I enabled https by editing the app.yaml and rebuilt app again (Let’s Encrypt)
Now I have this weird bug, one of the account’s avatar’s is showing that of another, constantly.
user A has the avatar of user B
user B however still has their correct avatar.
How to solve this?
---
### Author:  [@Yuun](https://meta.discourse.org/u/Yuun)
#### Post date: [2017年十一月27日 19:41 UTC](https://meta.discourse.org/t/wrong-account-avatar-after-upgrade/74886/2 "2017-11-27T19:41:40Z")
I am also seeing issues with this on my forum after upgrading to latest this morning, just noticed it a little bit ago.
It seems like I am seeing the correct avatar:
- Within a topic
- On user cards
- On individual profile pages
But I am seeing incorrect avatars:
- On /latest
- On admin/users
- On my profile button (top right corner of the screen)
I am also occasionally seeing a gray placeholder avatar thing, but I haven’t narrowed down when exactly it’s showing up…
I am also using https via Let’s Encrypt, and have been for a fair amount of time now (months? I dunno), in case that’s relevant.
I also have this error in /logs (42 times as of now), which I haven’t seen before:
> Failed to process hijacked response correctly undefined method ‘upcase’ for nil:NilClass
```plaintext
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/logster-1.2.8/lib/logster/logger.rb:93:in `add_with_opts'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/logster-1.2.8/lib/logster/logger.rb:50:in `add'
/usr/local/lib/ruby/2.4.0/logger.rb:534:in `warn'
/var/www/discourse/lib/hijack.rb:32:in `rescue in block in hijack'
/var/www/discourse/lib/hijack.rb:29:in `block in hijack'
/var/www/discourse/lib/scheduler/defer.rb:74:in `block in do_work'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rails_multisite-1.1.2/lib/rails_multisite/connection_management.rb:77:in `with_connection'
/var/www/discourse/lib/scheduler/defer.rb:72:in `do_work'
/var/www/discourse/lib/scheduler/defer.rb:61:in `block (2 levels) in start_thread'
```
---
### Author:  [@jomaxro](https://meta.discourse.org/u/jomaxro)
#### Post date: [2017年十一月27日 21:15 UTC](https://meta.discourse.org/t/wrong-account-avatar-after-upgrade/74886/3 "2017-11-27T21:15:33Z")
Hijack sounds like what @sam was working on…
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [2017年十一月27日 21:21 UTC](https://meta.discourse.org/t/wrong-account-avatar-after-upgrade/74886/4 "2017-11-27T21:21:12Z")
Do you have more of a stack trace there, try looking at all tabs, try visiting the error page
---
### Author:  [@Yuun](https://meta.discourse.org/u/Yuun)
#### Post date: [2017年十一月27日 21:29 UTC](https://meta.discourse.org/t/wrong-account-avatar-after-upgrade/74886/5 "2017-11-27T21:29:19Z")
The only additional info I didn’t include was from the env tab:
```plaintext
hostname sih-app
process_id [29461, 29445, 29367, 29351]
application_version [87ada55e677416713f24912487cde48221467b4d, c22f202e10dd70597f0e1afbd81b39f3b4f4e9c9]
```
Those 9 lines are all I see in the backtrace, though.
Can anonymous users see shared logs? Just in case, [link to the shared log on my forums](https://sih.onemadogre.com/logs/show/52b8069ad7615cafc064ea0c5361cb06). Nope, sure can’t.
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [2017年十一月27日 21:31 UTC](https://meta.discourse.org/t/wrong-account-avatar-after-upgrade/74886/6 "2017-11-27T21:31:49Z")
Actually … I just reproduced the issue … will get it fixed asap.
---
### Author:  [@jomaxro](https://meta.discourse.org/u/jomaxro)
#### Post date: [2017年十一月27日 21:33 UTC](https://meta.discourse.org/t/wrong-account-avatar-after-upgrade/74886/7 "2017-11-27T21:33:11Z")
> [@Yuun](#):
>
> Can anonymous users see shared logs?
To answer your question while Sam fixes the bug: no.
---
### Author:  [@Yuun](https://meta.discourse.org/u/Yuun)
#### Post date: [2017年十一月27日 21:36 UTC](https://meta.discourse.org/t/wrong-account-avatar-after-upgrade/74886/8 "2017-11-27T21:36:36Z")
Yeah I just did some stellar detective work (logged out of my forums and clicked the link) to find that out myself. 😊
Thanks for looking into this @sam!
---
### Author:  [@zogstrip](https://meta.discourse.org/u/zogstrip)
#### Post date: [2017年十一月27日 21:45 UTC](https://meta.discourse.org/t/wrong-account-avatar-after-upgrade/74886/9 "2017-11-27T21:45:33Z")
> [@Yuun](#):
>
> (logged out of my forums and clicked the link)
Alternatively, you could just open a new **incognito** window in your favorite browser 😉
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [2017年十一月27日 21:58 UTC](https://meta.discourse.org/t/wrong-account-avatar-after-upgrade/74886/10 "2017-11-27T21:58:09Z")
Ugh this is a nasty bug any eta on fix @sam?
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [2017年十一月27日 22:00 UTC](https://meta.discourse.org/t/wrong-account-avatar-after-upgrade/74886/11 "2017-11-27T22:00:46Z")
Will be fixed in 3 hours, probably sooner.
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [2017年十一月27日 22:29 UTC](https://meta.discourse.org/t/wrong-account-avatar-after-upgrade/74886/12 "2017-11-27T22:29:40Z")
This should fix it, but if anything is cached on the CDN in incorrectly … I can not flush that.
[https://github.com/discourse/discourse/commit/ca7af7b88f2207cd7a1700c2a086459f619e4d6c](https://github.com/discourse/discourse/commit/ca7af7b88f2207cd7a1700c2a086459f619e4d6c)
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [2017年十一月27日 23:26 UTC](https://meta.discourse.org/t/wrong-account-avatar-after-upgrade/74886/13 "2017-11-27T23:26:12Z")
Is it looking correct now @Yuun ?
---
### Author:  [@Yuun](https://meta.discourse.org/u/Yuun)
#### Post date: [2017年十一月27日 23:35 UTC](https://meta.discourse.org/t/wrong-account-avatar-after-upgrade/74886/14 "2017-11-27T23:35:11Z")
The avatars look correct on my current browser, but I’m getting a long list of `Failed to load resource: the server responded with a status of 500 ()` in my Chrome error log right now for each avatar it’s trying to load.
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [2017年十一月27日 23:35 UTC](https://meta.discourse.org/t/wrong-account-avatar-after-upgrade/74886/15 "2017-11-27T23:35:27Z")
Yeah I can see that, fixing.
Fixed per:
[https://github.com/discourse/discourse/commit/0caa335ef05b16af821012fa3b0bd4f5a5ac42d3](https://github.com/discourse/discourse/commit/0caa335ef05b16af821012fa3b0bd4f5a5ac42d3)
---
### Author:  [@Yuun](https://meta.discourse.org/u/Yuun)
#### Post date: [2017年十一月28日 00:55 UTC](https://meta.discourse.org/t/wrong-account-avatar-after-upgrade/74886/16 "2017-11-28T00:55:44Z")
Hm, still getting the 500 errors on avatar load after updating to this commit.
Nevermind, appears to have stopped now. Browser cache thing?
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [2017年十一月28日 01:03 UTC](https://meta.discourse.org/t/wrong-account-avatar-after-upgrade/74886/17 "2017-11-28T01:03:30Z")
Yeah was cached super aggressively.
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [2017年十一月29日 07:00 UTC](https://meta.discourse.org/t/wrong-account-avatar-after-upgrade/74886/18 "2017-11-29T07:00:05Z")
This topic was automatically closed after 29 hours. New replies are no longer allowed.