# Discourse Link previews through a proxy server?

**URL:** https://meta.discourse.org/t/discourse-link-previews-through-a-proxy-server/72720
**Category:** Self-hosting
**Created:** [October 25, 2017, 1:34am UTC](https://meta.discourse.org/t/discourse-link-previews-through-a-proxy-server/72720 "2017-10-25T01:34:34Z")
**Posts on this page:** 6
**Page:** 2

<div class="post-metadata">

### Author: ![supermathie](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/supermathie/32/507518_2.png) [@supermathie](https://meta.discourse.org/u/supermathie)
#### Post date: [October 26, 2017, 11:25pm UTC](https://meta.discourse.org/t/discourse-link-previews-through-a-proxy-server/72720/21 "2017-10-26T23:25:48Z")

</div>

> [@schungx](#):
>
> It is just a matter of running an IP scanner

Sure, but which of those 4 billion IPs is the right one if you can’t tell them apart?

With proper opsec (e.g. firewall rules to only allow Cloudflare in and whitelisted traffic out) means you will be pretty safe. Until you aren’t because you missed a leak 🙂

For example, better proxy all your DNS as well.

---

<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: [October 27, 2017, 2:04am UTC](https://meta.discourse.org/t/discourse-link-previews-through-a-proxy-server/72720/22 "2017-10-27T02:04:55Z")

</div>

Guess I’m lucky not to be hold any classified national military secrets! 😁

---

<div class="post-metadata">

### Author: ![nsuchy](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/nsuchy/32/166530_2.png) [@nsuchy](https://meta.discourse.org/u/nsuchy)
#### Post date: [November 3, 2017, 6:04pm UTC](https://meta.discourse.org/t/discourse-link-previews-through-a-proxy-server/72720/23 "2017-11-03T18:04:42Z")

</div>

Thanks everyone, I ended up switching to Frantech solutions who hooked me up with Voxalitys DDoS Filtering. Using a proxy is no longer needed 😁😁😁

---

<div class="post-metadata">

### Author: ![imaBASKET](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/imabasket/32/72987_2.png) [@imaBASKET](https://meta.discourse.org/u/imaBASKET)
#### Post date: [August 12, 2018, 5:19am UTC](https://meta.discourse.org/t/discourse-link-previews-through-a-proxy-server/72720/24 "2018-08-12T05:19:45Z")

</div>

Is it not possible to disable discourse’s parsing of these images/urls that cause the IP leak of the origin server?

Or at least make it so there is a whitelist of a certain set of domains that will be parsed?

---

<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: [March 15, 2021, 6:50pm UTC](https://meta.discourse.org/t/discourse-link-previews-through-a-proxy-server/72720/25 "2021-03-15T18:50:11Z")

</div>



---

<div class="post-metadata">

### Author: ![JammyDodger](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jammydodger/32/254611_2.png) [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [May 28, 2023, 7:07am UTC](https://meta.discourse.org/t/discourse-link-previews-through-a-proxy-server/72720/27 "2023-05-28T07:07:34Z")

</div>



[Previous page](https://meta.discourse.org/t/discourse-link-previews-through-a-proxy-server/72720.md?page=1)