# 이메일 호스트명 인증서 불일치로 인한 Sidekiq 큐 과부하 및 심각한 사이트 불안정

**URL:** https://meta.discourse.org/t/email-hostname-certificate-mismatch-causing-sidekiq-queue-overload-severe-site-instability/225778
**Category:** Self-hosting
**Created:** [4월 30, 2022, 11:02오후 UTC](https://meta.discourse.org/t/email-hostname-certificate-mismatch-causing-sidekiq-queue-overload-severe-site-instability/225778 "2022-04-30T23:02:36Z")
**Posts on this page:** 1
**Showing post:** 66

<div class="post-metadata">

### Author: ![RBoy](https://avatars.discourse-cdn.com/v4/letter/r/2bfe46/32.png) [@RBoy](https://meta.discourse.org/u/RBoy)
#### Post date: [5월 26, 2022, 6:58오후 UTC](https://meta.discourse.org/t/email-hostname-certificate-mismatch-causing-sidekiq-queue-overload-severe-site-instability/225778/66 "2022-05-26T18:58:54Z")

</div>

> [@Stephen](#):
>
> 메일 서버에서 TLS를 활성화하세요

저는 처음부터 유효한 인증서와 호스트명이 일치하도록 TLS를 활성화해 두었습니다. 그런데 BETA 4 (461936f211) 업그레이드 이후에 문제가 발생했고, 아래 주제에 로그를 게시했습니다. 다른 사용자도 문제를 겪고 있다고 하며, 그에 따르면 그의 인증서도 정상 상태라고 합니다:

> [@Sidekiq 재시도 오류](https://meta.discourse.org/t/retry-error-in-sidekiq/224706/20?u=rboy):
>
> I didn’t run out of space, and this happens even when I select exactly one job to re-run so it doesn’t look like a race condition. There’s clearly more than one issue here, and what I’m seeing here is not related to that linked topic. (It turns out that I didn’t have a certificate problem after all; the server names were in the alternate server name. But I moved to using the hostname that matches the SN anyway, and it made no difference.) I’m successfully sending a tremendous number of mails, …

---

_[View the full topic](https://meta.discourse.org/t/email-hostname-certificate-mismatch-causing-sidekiq-queue-overload-severe-site-instability/225778)._