mirror of
https://github.com/Sonarr/Sonarr
synced 2024-12-22 15:56:58 +00:00
Updated SSL (markdown)
parent
1c4231346a
commit
6209c7dc05
1 changed files with 1 additions and 1 deletions
2
SSL.md
2
SSL.md
|
@ -27,7 +27,7 @@ There are two issues with mono and SSL:
|
||||||
1. New ciphers aren't supported so some browsers block the connections by default (chrome and FF both do this)
|
1. New ciphers aren't supported so some browsers block the connections by default (chrome and FF both do this)
|
||||||
Mono doesn't support intermediate certificates, which results in a broken chain and the browsers end up requesting a client certificate
|
Mono doesn't support intermediate certificates, which results in a broken chain and the browsers end up requesting a client certificate
|
||||||
|
|
||||||
2. The second issue can be mitigated by using a certificate chain that doesn't have an intermediate certificate, but most CAs use an intermediate certificate (at least the trusted public ones), which means it leaves you to a self signed certificate. The easiest solution for the time being is a reverse proxy with nginx or apache.
|
2. The [second issue](https://github.com/Sonarr/Sonarr/issues/4682) can be mitigated by using a certificate chain that doesn't have an intermediate certificate, but most CAs use an intermediate certificate (at least the trusted public ones), which means it leaves you to a self signed certificate. The easiest solution for the time being is a reverse proxy with nginx or apache.
|
||||||
|
|
||||||
### Prerequisites
|
### Prerequisites
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue