# My discourse has either been hacked or catfished?

**URL:** https://meta.discourse.org/t/my-discourse-has-either-been-hacked-or-catfished/43697
**Category:** Support
**Created:** [5월 5, 2016, 12:04오전 UTC](https://meta.discourse.org/t/my-discourse-has-either-been-hacked-or-catfished/43697 "2016-05-05T00:04:24Z")
**Posts on this page:** 11
**Page:** 1

<div class="post-metadata">

### Author: ![mrdiscourse](https://avatars.discourse-cdn.com/v4/letter/m/e68b1a/32.png) [@mrdiscourse](https://meta.discourse.org/u/mrdiscourse)
#### Post date: [5월 5, 2016, 12:04오전 UTC](https://meta.discourse.org/t/my-discourse-has-either-been-hacked-or-catfished/43697/1 "2016-05-05T00:04:24Z")

</div>

I noticed bing webmaster telling me I had a backlink from somewhere. I investigated to find to my surprise someone had stole my discourse based site!

I deactivated ‘allow same origin’ plugin but its still somehow appearing on this fake site.

My site is [http://www.aibuapp.com/](http://www.aibuapp.com/) and the catfish is [http://labthi.ng/](http://labthi.ng/)

Has my discourse been hacked?

---

<div class="post-metadata">

### Author: ![Rodelio\_Lagahit](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/rodelio_lagahit/32/121638_2.png) [@Rodelio\_Lagahit](https://meta.discourse.org/u/Rodelio_Lagahit)
#### Post date: [5월 5, 2016, 12:07오전 UTC](https://meta.discourse.org/t/my-discourse-has-either-been-hacked-or-catfished/43697/2 "2016-05-05T00:07:27Z")

</div>

have you checked your DNS?

kindly check your host/domain provider as well. They might be able to look into the config/settings why is your site pointing to another domain simultaneously.

---

<div class="post-metadata">

### Author: ![mrdiscourse](https://avatars.discourse-cdn.com/v4/letter/m/e68b1a/32.png) [@mrdiscourse](https://meta.discourse.org/u/mrdiscourse)
#### Post date: [5월 6, 2016, 12:59오전 UTC](https://meta.discourse.org/t/my-discourse-has-either-been-hacked-or-catfished/43697/3 "2016-05-06T00:59:12Z")

</div>

Yes I contacted them. They said this other person is pointing their domain to the server. Why would they even bother doing that?? What’s a foolproof and easy way to block traffic from their domain?

---

<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: [5월 6, 2016, 1:17오전 UTC](https://meta.discourse.org/t/my-discourse-has-either-been-hacked-or-catfished/43697/4 "2016-05-06T01:17:24Z")

</div>

I think this is a fix @sam needs to make so the site will only answer to the official domain and IP address.

---

<div class="post-metadata">

### Author: ![fefrei](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/fefrei/32/119538_2.png) [@fefrei](https://meta.discourse.org/u/fefrei)
#### Post date: [5월 6, 2016, 5:56오전 UTC](https://meta.discourse.org/t/my-discourse-has-either-been-hacked-or-catfished/43697/5 "2016-05-06T05:56:49Z")

</div>

We already had this case once here on Meta, but I cannot find the topic or remember the resolution ☹

---

<div class="post-metadata">

### Author: ![mpalmer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mpalmer/32/45740_2.png) [@mpalmer](https://meta.discourse.org/u/mpalmer)
#### Post date: [5월 6, 2016, 6:15오전 UTC](https://meta.discourse.org/t/my-discourse-has-either-been-hacked-or-catfished/43697/6 "2016-05-06T06:15:59Z")

</div>

I don’t have the topic reference to hand, but it was given to me to rummage around and try to munge the nginx config to setup a separate default site. Never quite got around to actually _doing_ it, though.

---

<div class="post-metadata">

### Author: ![fantasticfears](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/fantasticfears/32/119608_2.png) [@fantasticfears](https://meta.discourse.org/u/fantasticfears)
#### Post date: [5월 6, 2016, 8:51오전 UTC](https://meta.discourse.org/t/my-discourse-has-either-been-hacked-or-catfished/43697/7 "2016-05-06T08:51:50Z")

</div>

Sometime, it’s quite useful for helping reduce the redirection configuration, i.e. `www`

And I am pretty sure web ssl template will redirect the user to the actual domain.

```nginx
if ($http_host != $$ENV_DISCOURSE_HOSTNAME) {
    rewrite (.*) https://$$ENV_DISCOURSE_HOSTNAME$1 permanent;
}

```

ssl and letsencrypt templates would relieve you from all kinds of troubles.

EDIT: You don’t even need to issue any certs for domain where you want redirection comes from.

---

<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: [5월 6, 2016, 11:46오전 UTC](https://meta.discourse.org/t/my-discourse-has-either-been-hacked-or-catfished/43697/8 "2016-05-06T11:46:42Z")

</div>

Yes, I consider this solved, everyone should be using the lets encrypt template, it is free and solves this issue 100%

---

<div class="post-metadata">

### Author: ![mrdiscourse](https://avatars.discourse-cdn.com/v4/letter/m/e68b1a/32.png) [@mrdiscourse](https://meta.discourse.org/u/mrdiscourse)
#### Post date: [5월 13, 2016, 12:28오후 UTC](https://meta.discourse.org/t/my-discourse-has-either-been-hacked-or-catfished/43697/9 "2016-05-13T12:28:05Z")

</div>

Ok where do I find it and use it? Does this mean I need to install a certificate?

---

<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: [5월 13, 2016, 2:34오후 UTC](https://meta.discourse.org/t/my-discourse-has-either-been-hacked-or-catfished/43697/10 "2016-05-13T14:34:36Z")

</div>

The first search result for: “lets encrypt”

> [@Set up HTTPS support with Let's Encrypt](https://meta.discourse.org/t/setting-up-lets-encrypt-cert-with-discourse-docker/40709):
>
> bookmark This is a guide for enabling HTTPS on an existing Discourse installation using Let’s Encrypt. It assumes prior installation without HTTPS enabled. person_raising_hand Required user level: System Administrator exclamation This guide is only for existing installs where HTTPS is not enabled. Following the [official setup guide](https://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md) automatically enables HTTPS by default. So you’d like to add https to your Discourse absolutely free, courtesy of our friends at [Let’s Encrypt?](https://letsencrypt.org/)bell I…

---

<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: [10월 12, 2016, 12:30오전 UTC](https://meta.discourse.org/t/my-discourse-has-either-been-hacked-or-catfished/43697/11 "2016-10-12T00:30:12Z")

</div>


