# EC2 Origin Exposed By Google Web Crawler With Discourse & CloudFlare

**URL:** <https://meta.discourse.org/t/ec2-origin-exposed-by-google-web-crawler-with-discourse-cloudflare/104521>\
**Category:** Self-hosting\
**Created:** [18 בדצמבר,‏ 2018,‏ 5:32am UTC](https://meta.discourse.org/t/ec2-origin-exposed-by-google-web-crawler-with-discourse-cloudflare/104521 "2018-12-18T05:32:56Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![TempusOwl](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tempusowl/32/125537_2.png) [@TempusOwl](https://meta.discourse.org/u/TempusOwl)\
**Post date:** [18 בדצמבר,‏ 2018,‏ 7:30pm UTC](https://meta.discourse.org/t/ec2-origin-exposed-by-google-web-crawler-with-discourse-cloudflare/104521/6 "2018-12-18T19:30:28Z")

</div>

I am using SSL and it is working, when I got to the public DNS it spews SSL errors (as you would imagine). Google still seems to crawl it despite the SSL mismatch. I did not change anything in way I handled SSL since the site was installed so I am surprised Google is still crawling the page despite the SSL errors. It is even still being updated on the search engine which is quite odd. The weird thing is I do not know why because I have not pointed anything to public DNS unless discourse did something with a mind of its own during install. I have a second site running on this server that is unaffected by this problem.

---

_[View the full topic](https://meta.discourse.org/t/ec2-origin-exposed-by-google-web-crawler-with-discourse-cloudflare/104521)._
