# Avatars became default after 2.2 beta upgrade - due to regression in azure blob plugin

**URL:** <https://meta.discourse.org/t/avatars-became-default-after-2-2-beta-upgrade-due-to-regression-in-azure-blob-plugin/105875>\
**Category:** Product Support\
**Created:** [January 7, 2019, 5:08am UTC](https://meta.discourse.org/t/avatars-became-default-after-2-2-beta-upgrade-due-to-regression-in-azure-blob-plugin/105875 "2019-01-07T05:08:46Z")\
**Posts on this page:** 20\
**Page:** 1

## AI-generated summary

After upgrading to Discourse v2.2.0.beta7, users reported that custom avatars were replaced with default gray icons, though newly uploaded avatars displayed correctly. Initial suggestions included waiting 24 hours for image optimization or checking Sidekiq queues, but the issue persisted. Investigation revealed the problem was specific to the Azure Blob Storage plugin, which incorrectly handled S3 endpoint redirections — for example, URLs pointing to `eu-west-3` were failing, while `eu-west-2` worked. [vinothkannans](/t/-/105875/20) confirmed this via S3 error responses and submitted a [PR to fix the issue](https://github.com/discourse/discourse/pull/6871), adding new test coverage in the plugin. The regression was not caused by user configuration or S3 changes, but by a bug in how the plugin resolved storage endpoints. [schungx](/t/-/105875/1) and [Wildweasel](/t/-/105875/16) confirmed the behavior across different sites, and [sam](/t/-/105875/8) helped diagnose by requesting file system checks and URL examples. The fix is pending merge, and users affected by this regression should monitor the PR for updates.

<div class="post-metadata">

**Author:** ![schungx](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/schungx/32/70989_2.png) [@schungx](https://meta.discourse.org/u/schungx)\
**Post date:** [January 7, 2019, 5:08am UTC](https://meta.discourse.org/t/avatars-became-default-after-2-2-beta-upgrade-due-to-regression-in-azure-blob-plugin/105875/1 "2019-01-07T05:08:46Z")

</div>

Not sure what happened, but after upgrading to the latest beta, all custom user avatars are gone, replaced by a standard image of a light-gray user.

 ![image](https://global.discourse-cdn.com/meta/original/3X/6/4/640b918d90b0493c5fcd430bec14f230f0009b80.png)

The default-generated avatars for users with no custom avatar uploads are not affected.

The image links to those avatars are:

```plaintext
https://xxxxx.com/user_avatar/xxx.com/user/50/179_2.png

```

EDIT: Uploading a new avatar image will show up. Therefore, all the previously-uploaded avatar images are all lost.

---

<div class="post-metadata">

**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\
**Post date:** [January 7, 2019, 5:14am UTC](https://meta.discourse.org/t/avatars-became-default-after-2-2-beta-upgrade-due-to-regression-in-azure-blob-plugin/105875/2 "2019-01-07T05:14:14Z")

</div>

No, it just takes time for the images to re-optimize. See the other topic on this. Give it 24 hours.

---

<div class="post-metadata">

**Author:** ![schungx](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/schungx/32/70989_2.png) [@schungx](https://meta.discourse.org/u/schungx)\
**Post date:** [January 7, 2019, 5:23am UTC](https://meta.discourse.org/t/avatars-became-default-after-2-2-beta-upgrade-due-to-regression-in-azure-blob-plugin/105875/3 "2019-01-07T05:23:02Z")

</div>

I suppose you mean this one:

> [@User profile images loading slowly, failing to load](https://meta.discourse.org/t/user-profile-images-loading-slowly-failing-to-load/105595):
>
> Not sure if something you changed with the fuzzy image loading is being applied to user profile pictures, but I’ve noticed that after upgrading to 2.2.0.beta7 quite a few user images are either failing to load entirely (leaving just an empty white space) or are loading very, very slowly. As seen here: [https://share.otf.ca/](https://share.otf.ca/)

I’ll keep my fingers crossed for 24 more hours…

---

<div class="post-metadata">

**Author:** ![bletch](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/bletch/32/69088_2.png) [@bletch](https://meta.discourse.org/u/bletch)\
**Post date:** [January 7, 2019, 6:37am UTC](https://meta.discourse.org/t/avatars-became-default-after-2-2-beta-upgrade-due-to-regression-in-azure-blob-plugin/105875/4 "2019-01-07T06:37:51Z")

</div>

Yep, had the same issue after upgrade. 15 mins later the avatars were back.

---

<div class="post-metadata">

**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\
**Post date:** [January 7, 2019, 12:15pm UTC](https://meta.discourse.org/t/avatars-became-default-after-2-2-beta-upgrade-due-to-regression-in-azure-blob-plugin/105875/5 "2019-01-07T12:15:55Z")

</div>

Let us know if it is still an issue.

---

<div class="post-metadata">

**Author:** ![schungx](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/schungx/32/70989_2.png) [@schungx](https://meta.discourse.org/u/schungx)\
**Post date:** [January 7, 2019, 2:24pm UTC](https://meta.discourse.org/t/avatars-became-default-after-2-2-beta-upgrade-due-to-regression-in-azure-blob-plugin/105875/6 "2019-01-07T14:24:42Z")

</div>

Half a day now and still the default pics…

---

<div class="post-metadata">

**Author:** ![schungx](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/schungx/32/70989_2.png) [@schungx](https://meta.discourse.org/u/schungx)\
**Post date:** [January 8, 2019, 3:39am UTC](https://meta.discourse.org/t/avatars-became-default-after-2-2-beta-upgrade-due-to-regression-in-azure-blob-plugin/105875/7 "2019-01-08T03:39:43Z")

</div>

Nope. It doesn’t go back to normal. All the avatars are still the default pics.

Any command line to manually rebuild them?

---

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [January 8, 2019, 4:05am UTC](https://meta.discourse.org/t/avatars-became-default-after-2-2-beta-upgrade-due-to-regression-in-azure-blob-plugin/105875/8 "2019-01-08T04:05:35Z")

</div>

How is your sidekiq queue looking? Is it empty?

There is some nginx level caching if queue is empty go ahead and rebuild

---

<div class="post-metadata">

**Author:** ![schungx](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/schungx/32/70989_2.png) [@schungx](https://meta.discourse.org/u/schungx)\
**Post date:** [January 8, 2019, 4:09am UTC](https://meta.discourse.org/t/avatars-became-default-after-2-2-beta-upgrade-due-to-regression-in-azure-blob-plugin/105875/9 "2019-01-08T04:09:56Z")

</div>

![image](https://global.discourse-cdn.com/meta/original/3X/3/2/32ace6535566d4ba89e8446f1c02c5ed6d895a14.png)

Looks empty.

How should I rebuild? Do a “./launcher rebuild app”?

---

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [January 8, 2019, 9:12am UTC](https://meta.discourse.org/t/avatars-became-default-after-2-2-beta-upgrade-due-to-regression-in-azure-blob-plugin/105875/10 "2019-01-08T09:12:25Z")

</div>

Quote avatars becoming default is probably due to:

[https://review.discourse.org/t/fix-always-serve-new-avatar-for-previous-version/1002](https://review.discourse.org/t/fix-always-serve-new-avatar-for-previous-version/1002)

Added bonus, stuff will run faster as well. Let me know how it goes.

---

<div class="post-metadata">

**Author:** ![schungx](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/schungx/32/70989_2.png) [@schungx](https://meta.discourse.org/u/schungx)\
**Post date:** [January 8, 2019, 9:31am UTC](https://meta.discourse.org/t/avatars-became-default-after-2-2-beta-upgrade-due-to-regression-in-azure-blob-plugin/105875/11 "2019-01-08T09:31:22Z")

</div>

Well, unfortunately, I did a `./launcher rebuild app` and it is still showing the default pic.

So that’s not it.

Version is [v2.2.0.beta7 +60](https://github.com/discourse/discourse/compare/f947e3c6ccf307c5b3b778a1ccca3390825b14f3...tests-passed)

---

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [January 8, 2019, 10:10am UTC](https://meta.discourse.org/t/avatars-became-default-after-2-2-beta-upgrade-due-to-regression-in-azure-blob-plugin/105875/12 "2019-01-08T10:10:22Z")

</div>

what is an example URL of a broken avatar? I want you to try some things.

---

<div class="post-metadata">

**Author:** ![schungx](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/schungx/32/70989_2.png) [@schungx](https://meta.discourse.org/u/schungx)\
**Post date:** [January 8, 2019, 10:11am UTC](https://meta.discourse.org/t/avatars-became-default-after-2-2-beta-upgrade-due-to-regression-in-azure-blob-plugin/105875/13 "2019-01-08T10:11:32Z")

</div>

![](https://global.discourse-cdn.com/meta/original/3X/6/f/6f0da341a1e570dc973d7251ecd8b4bb3c17eb65.png)

---

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [January 8, 2019, 11:25am UTC](https://meta.discourse.org/t/avatars-became-default-after-2-2-beta-upgrade-due-to-regression-in-azure-blob-plugin/105875/14 "2019-01-08T11:25:53Z")

</div>

Sorry , I need the url on your site I want you to adjust numbers there to diagnose what is up

---

<div class="post-metadata">

**Author:** ![Wildweasel](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/wildweasel/32/128234_2.png) [@Wildweasel](https://meta.discourse.org/u/Wildweasel)\
**Post date:** [January 8, 2019, 10:23pm UTC](https://meta.discourse.org/t/avatars-became-default-after-2-2-beta-upgrade-due-to-regression-in-azure-blob-plugin/105875/16 "2019-01-08T22:23:12Z")

</div>

Hi,

If you need an example, I have the same problem on my site:  
[https://libertysim.net/t/perturbation-de-lhebergement-des-images/41402](https://libertysim.net/t/perturbation-de-lhebergement-des-images/41402)

By the way, I experience another problem with links of pictures from Imgur or Flickr. The display is broken after 15 minutes and replaced by an unreachable item icon.

The installed version is v2.2.0.beta7 +42

---

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [January 8, 2019, 11:28pm UTC](https://meta.discourse.org/t/avatars-became-default-after-2-2-beta-upgrade-due-to-regression-in-azure-blob-plugin/105875/17 "2019-01-08T23:28:31Z")

</div>

If you edit loliver4’s profile and open the avatar selection screen, do you see it there? Is it using a local avatar or a gravatar?

Can you run

```plaintext
./launcher enter app
rails c
Upload.find(3262)

```

Is the file it is referencing in your file system? What is the size of the file?

Something is not right here…

Also seeing a redirect here:

[http://libertysim.s3.dualstack.eu-west-3.amazonaws.com/original/2X/a/a5fce085968b65330ee85eec7ea8aac9aa2af9fa.jpeg](http://libertysim.s3.dualstack.eu-west-3.amazonaws.com/original/2X/a/a5fce085968b65330ee85eec7ea8aac9aa2af9fa.jpeg)

Did you move your S3 stuff around?

---

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [January 9, 2019, 10:15am UTC](https://meta.discourse.org/t/avatars-became-default-after-2-2-beta-upgrade-due-to-regression-in-azure-blob-plugin/105875/20 "2019-01-09T10:15:14Z")

</div>

This particular topic is a bug in azure blob storage plugin, @vinothkannans is looking at it.

---

<div class="post-metadata">

**Author:** ![gauthier](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/gauthier/32/59292_2.png) [@gauthier](https://meta.discourse.org/u/gauthier)\
**Post date:** [January 9, 2019, 10:32am UTC](https://meta.discourse.org/t/avatars-became-default-after-2-2-beta-upgrade-due-to-regression-in-azure-blob-plugin/105875/21 "2019-01-09T10:32:41Z")

</div>

Hi

```
[1] pry(main)> Upload.find(3262)
=> #<Upload:0x0000564ef0da8a00
 id: 3262,
 user_id: 2858,
 original_filename: "13962749_845715052226788_5249706654812763874_n.jpg",
 filesize: 60477,
 width: 360,
 height: 360,
 url: "//libertysim.s3.dualstack.eu-west-3.amazonaws.com/original/2X/7/71d87b34609aec9e248e7f9739daf0f970ac5a67.jpeg",
 created_at: Sun, 06 Jan 2019 05:30:22 UTC +00:00,
 updated_at: Sun, 06 Jan 2019 05:30:22 UTC +00:00,
 sha1: "71d87b34609aec9e248e7f9739daf0f970ac5a67",
 origin: nil,
 retain_hours: nil,
 extension: "jpeg",
 thumbnail_width: 360,
 thumbnail_height: 360,
 etag: "\"8cb513f4b9899fa26bb7de856c935c59\"">

```

No special change on S3 was done…

---

<div class="post-metadata">

**Author:** ![vinothkannans](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/vinothkannans/32/86465_2.png) [@vinothkannans](https://meta.discourse.org/u/vinothkannans)\
**Post date:** [January 9, 2019, 1:10pm UTC](https://meta.discourse.org/t/avatars-became-default-after-2-2-beta-upgrade-due-to-regression-in-azure-blob-plugin/105875/22 "2019-01-09T13:10:18Z")

</div>

> **S3 response**
>
> ```xml
> <Error>
> <Code>PermanentRedirect</Code>
> <Message>
> The bucket you are attempting to access must be addressed using the specified endpoint. Please send all future requests to this endpoint.
> </Message>
> <Endpoint>libertysim.s3.dualstack.eu-west-2.amazonaws.com</Endpoint>
> <Bucket>libertysim</Bucket>
> <RequestId>5353DFE7A14AB123</RequestId>
> <HostId>
> QDQ3mKgq95kH92AloN1gH+LwGIgP9FWq77ck5yHVKSoIXx14nqiGN3u5gjOwxegfd9zVb7nN0J4=
> </HostId>
> </Error>
> 
> ```

As per the above response from S3 if I change the hostname to `libertysim.s3.dualstack.eu-west-2.amazonaws.com` then the URL is working. I’m not sure how it’s messed up. But it doesn’t look like a problem from Discourse side.

[http://libertysim.s3.dualstack.eu-west-2.amazonaws.com/original/2X/a/a5fce085968b65330ee85eec7ea8aac9aa2af9fa.jpeg](http://libertysim.s3.dualstack.eu-west-2.amazonaws.com/original/2X/a/a5fce085968b65330ee85eec7ea8aac9aa2af9fa.jpeg)

---

<div class="post-metadata">

**Author:** ![vinothkannans](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/vinothkannans/32/86465_2.png) [@vinothkannans](https://meta.discourse.org/u/vinothkannans)\
**Post date:** [January 10, 2019, 2:10pm UTC](https://meta.discourse.org/t/avatars-became-default-after-2-2-beta-upgrade-due-to-regression-in-azure-blob-plugin/105875/23 "2019-01-10T14:10:53Z")

</div>

Created a new PR to fix this issue

[https://github.com/discourse/discourse/pull/6871](https://github.com/discourse/discourse/pull/6871)

This bug is reproducible using the new rspec method which I added in `discourse-azure-blog-storage` plugin.

[https://github.com/discourse/discourse-azure-blob-storage/commit/decad5d7dfcf516eacf07d18c83a116a6dc5af14](https://github.com/discourse/discourse-azure-blob-storage/commit/decad5d7dfcf516eacf07d18c83a116a6dc5af14)

[Next page](https://meta.discourse.org/t/avatars-became-default-after-2-2-beta-upgrade-due-to-regression-in-azure-blob-plugin/105875.md?page=2)
