# Avatar images broken behind proxy

**URL:** https://meta.discourse.org/t/avatar-images-broken-behind-proxy/228459
**Category:** Support
**Created:** [May 30, 2022, 4:39pm UTC](https://meta.discourse.org/t/avatar-images-broken-behind-proxy/228459 "2022-05-30T16:39:23Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![rbos](https://avatars.discourse-cdn.com/v4/letter/r/b3f665/32.png) [@rbos](https://meta.discourse.org/u/rbos)
#### Post date: [May 30, 2022, 4:39pm UTC](https://meta.discourse.org/t/avatar-images-broken-behind-proxy/228459/1 "2022-05-30T16:39:23Z")

</div>

Hello,

We recently had a firewall rule imposed on our servers such that all outbound HTTP/S requests had to be whitelisted to go outbound, either through a proxy or with a direct rule. Since then, some images have failed to load, in particular, avatars generate a 500 error, eg, `[url]/letter_avatar_proxy/v4/letter/d/8edcca/45.png`

edit before posting: The forum software understandably complains about links in posts by new users, so please substitute “$URL\_GRAVATAR” = “[www.gravatar.com](http://www.gravatar.com)”

My best guess is that it’s trying to access $URL\_GRAVATAR from within the container. I had our firewall guy set up an exception so that $URL\_GRAVATAR gets a direct rule, and set "no\_proxy=‘$URL\_GRAVATAR’ and rebuilt the container.

Within the container, I verify that no\_proxy is set, and I can curl directly to the URL:

```plaintext
no_proxy='$URL_GRAVATAR,[etc],127.0.0.0/8'

# curl -Ik https://$URL_GRAVATAR
HTTP/2 302 
server: nginx

```

But, images still appear to be broken. Is there something I’m missing? I don’t have access to external logs to show what exactly it’s failing to access.

edit: the 302 redirect there is possibly the problem, it redirects to another address that I perhaps need to whitelist. If I do `curl -IL $URL_GRAVATAR` it gives me a proxy failure.

---

<div class="post-metadata">

### Author: ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [May 30, 2022, 5:23pm UTC](https://meta.discourse.org/t/avatar-images-broken-behind-proxy/228459/2 "2022-05-30T17:23:37Z")

</div>

> [@rbos](#):
>
> [url]/letter\_avatar\_proxy/v4/letter/d/8edcca/45.png

You need to allow [https://avatars.discourse-cdn.com/](https://avatars.discourse-cdn.com/) to fix the letter avatar.

---

<div class="post-metadata">

### Author: ![rbos](https://avatars.discourse-cdn.com/v4/letter/r/b3f665/32.png) [@rbos](https://meta.discourse.org/u/rbos)
#### Post date: [May 30, 2022, 6:52pm UTC](https://meta.discourse.org/t/avatar-images-broken-behind-proxy/228459/3 "2022-05-30T18:52:44Z")

</div>

Thanks, I’ll try that! Just gotta schedule a half hour downtime for the Discourse rebuild. 🙂

Super frustrating trying to guess the access that stuff needs without access to the outgoing proxy logs. 😕

---

<div class="post-metadata">

### Author: ![rbos](https://avatars.discourse-cdn.com/v4/letter/r/b3f665/32.png) [@rbos](https://meta.discourse.org/u/rbos)
#### Post date: [June 5, 2022, 9:25pm UTC](https://meta.discourse.org/t/avatar-images-broken-behind-proxy/228459/4 "2022-06-05T21:25:56Z")

</div>

Confirmed working, by the way. Thanks!

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [July 5, 2022, 9:26pm UTC](https://meta.discourse.org/t/avatar-images-broken-behind-proxy/228459/5 "2022-07-05T21:26:24Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.