# Error code: sec\_error\_bad\_signature

**URL:** <https://community.letsencrypt.org/t/error-code-sec-error-bad-signature/17725>\
**Category:** Server\
**Created:** [July 8, 2016, 11:09am UTC](https://community.letsencrypt.org/t/error-code-sec-error-bad-signature/17725 "2016-07-08T11:09:30Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![smita.patil](https://avatars.discourse-cdn.com/v4/letter/s/45deac/32.png) [@smita.patil](https://community.letsencrypt.org/u/smita.patil)\
**Post date:** [July 8, 2016, 11:09am UTC](https://community.letsencrypt.org/t/error-code-sec-error-bad-signature/17725/1 "2016-07-08T11:09:30Z")

</div>

I am getting error: sec\_error\_bad\_signature randomly on any pages. Domain is [www.tiss.edu](http://www.tiss.edu).

There are some more errors when using link checker:

1. Error: SSLError: [Errno 1] \_ssl.c:510: error:0407006A:rsa routines:RSA\_padding\_check\_PKCS1\_type\_1:block type is not 01
2. Error: SSLError: [Errno 1] \_ssl.c:510: error:140773F2:SSL routines:SSL23\_GET\_SERVER\_HELLO:sslv3 alert unexpected message

---

<div class="post-metadata">

**Author:** ![pfg](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/pfg/32/1924_2.png) [@pfg](https://community.letsencrypt.org/u/pfg)\
**Post date:** [July 8, 2016, 11:16am UTC](https://community.letsencrypt.org/t/error-code-sec-error-bad-signature/17725/2 "2016-07-08T11:16:18Z")

</div>

[This](https://support.mozilla.org/en-US/questions/1076481) seems to indicate it might be related to broken AV software with MitM capabilities. It’s unlikely to be related to your certificate or server configuration.

---

<div class="post-metadata">

**Author:** ![smita.patil](https://avatars.discourse-cdn.com/v4/letter/s/45deac/32.png) [@smita.patil](https://community.letsencrypt.org/u/smita.patil)\
**Post date:** [July 11, 2016, 9:31am UTC](https://community.letsencrypt.org/t/error-code-sec-error-bad-signature/17725/3 "2016-07-11T09:31:27Z")

</div>

I am not using any AV software.

---

<div class="post-metadata">

**Author:** ![tialaramex](https://avatars.discourse-cdn.com/v4/letter/t/f08c70/32.png) [@tialaramex](https://community.letsencrypt.org/u/tialaramex)\
**Post date:** [July 11, 2016, 2:09pm UTC](https://community.letsencrypt.org/t/error-code-sec-error-bad-signature/17725/4 "2016-07-11T14:09:46Z")

</div>

Alas ISPs, and even nation states may try to conduct MitM attacks, with a variety of purposes. So this could still be the cause even if you’re not doing anything wrong.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [August 10, 2016, 2:10pm UTC](https://community.letsencrypt.org/t/error-code-sec-error-bad-signature/17725/5 "2016-08-10T14:10:09Z")

</div>

Closed on August 10, 2016, 2:10pm UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.