# Avatar Proxy and CDN Hot-Link Protection

**URL:** <https://meta.discourse.org/t/avatar-proxy-and-cdn-hot-link-protection/350525>\
**Category:** Product Support\
**Created:** [February 4, 2025, 10:18pm UTC](https://meta.discourse.org/t/avatar-proxy-and-cdn-hot-link-protection/350525 "2025-02-04T22:18:57Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![LotusJeff](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/lotusjeff/32/477888_2.png) [@LotusJeff](https://meta.discourse.org/u/LotusJeff)\
**Post date:** [February 5, 2025, 7:17pm UTC](https://meta.discourse.org/t/avatar-proxy-and-cdn-hot-link-protection/350525/7 "2025-02-05T19:17:27Z")

</div>

I appreciate your help. After many decades of working in IT development and support, vague questions and responses create more work than necessary. Based on your experience, I think you would agree.

The CDN is only set up for the S3 bucket.

I did check the CDN logs for the Discourse IP related to the 403 errors before submitting the original topic. It was not in the log files.

Based on your comments, I went back and reanalyzed the logs. After reviewing the largest IP offenders, I found that the top couple are gateways for the hosting company.

The challenge is that I do not want to keep track of the Digital Ocean’s gateway IP addresses so my Discourse server can display images correctly.

Thank you for the assist.

---

_[View the full topic](https://meta.discourse.org/t/avatar-proxy-and-cdn-hot-link-protection/350525)._