# Connection Timeout/Security Issue

**URL:** https://meta.discourse.org/t/connection-timeout-security-issue/209652
**Category:** Self-hosting
**Created:** [November 19, 2021, 4:33pm UTC](https://meta.discourse.org/t/connection-timeout-security-issue/209652 "2021-11-19T16:33:24Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [November 19, 2021, 6:22pm UTC](https://meta.discourse.org/t/connection-timeout-security-issue/209652/2 "2021-11-19T18:22:30Z")

</div>

You need to set that first record for `www`, not `www.skuvault.social`. If you use a DNS tester you’ll see that there’s no DNS record for `www.skuvault.social`, but there is one for `www.skuvault.social.skuvault.social`.

If you’ve run a bunch of rebuilds, your next issue will be that you hit let’s encrypt’s rate limit and your key is invalid. You’ll need to wait a week or follow [Setting up Let’s Encrypt with Multiple Domains](https://meta.discourse.org/t/setting-up-let-s-encrypt-with-multiple-domains/56685), which is a bit tricky.

---

_[View the full topic](https://meta.discourse.org/t/connection-timeout-security-issue/209652)._