Skip to content

Commit 0dd713e

Browse files
jc21jc21
committed
more help docs
1 parent 972e53d commit 0dd713e

19 files changed

+203
-6
lines changed

‎frontend/src/locale/src/HelpDoc/de/AccessLists.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
# Access Lists Help
2+
3+
todo

‎frontend/src/locale/src/HelpDoc/de/CertificateAuthorities.md

Lines changed: 28 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,29 @@
1-
# Hilfe zu Zertifizierungsstellen
1+
# Certificate Authorities Help
22

3-
TODO
3+
## What is a Certificate Authority?
4+
5+
A **Certificate Authority (CA)**, also sometimes referred to as a
6+
**Certification Authority**, is a company or organization that acts to validate
7+
the identities of entities (such as websites, email addresses, companies, or
8+
individual persons) and bind them to cryptographic keys through the issuance of
9+
electronic documents known as digital certificates.
10+
11+
## Which CA should I use?
12+
13+
Not all CA's are created equal and you would be fine to use the default,
14+
ZeroSSL.
15+
16+
When using another CA it's worth considering the wildcard support and number of
17+
hosts-per-certificate that it supports.
18+
19+
## Can I use my own custom CA?
20+
21+
Yes, you can run your own CA software. You would only do this if you have a
22+
greater understanding of the SSL ecosystem.
23+
24+
When requesting SSL Certificates through your custom CA and while they will be
25+
successful, browsers will not automatically trust your CA and visiting hosts
26+
using certificates issued by that CA will show errors.
27+
28+
- [StepCA](https://smallstep.com/docs/step-ca)
29+
- [Pebble](https://github.com/letsencrypt/pebble)

‎frontend/src/locale/src/HelpDoc/de/Certificates.md

Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
# Certificates Help
2+
3+
## HTTP Certificate
4+
5+
A HTTP validated certificate means that the Certificate Authority (CA) will
6+
attempt to reach your domains over HTTP (not HTTPS!) and if successful, the CA
7+
will issue your certificate.
8+
9+
For this method, you will have to have a _Host_ created for your domains(s) that
10+
is accessible with HTTP. After a certificate has been given, you can modify the
11+
_Host_ to also use this certificate for HTTPS connections. However, the _Host_
12+
will still need to be configured for HTTP access in order for the certificate to
13+
renew.
14+
15+
## DNS Certificate
16+
17+
A DNS validated certificate requires you to create a DNS Provider. This DNS
18+
Provider will be used to create temporary records on your ___domain and then the CA
19+
will query those records to be sure you're the owner and if successful, the CA
20+
will issue your certificate.
21+
22+
You do not need a _Host_ to be created prior to requesting this type of
23+
certificate. Nor do you need to have your _Host_ configured for HTTP access.
24+
25+
## Custom Certificate
26+
27+
Use this option to upload your own SSL Certificate, as provided by your own
28+
Certificate Authority.
29+
30+
## MKCert Certificate
31+
32+
This option will create a self-signed Certificate for development use. When
33+
viewing a _Host_ that using a MKCert Certificate, the browser will show errors.
34+
35+
## Choosing a Certificate Authority
36+
37+
If you're not sure, use **ZeroSSL.**

‎frontend/src/locale/src/HelpDoc/de/DNSProviders.md

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
# DNS Providers Help
2+
3+
A DNS Provider is a service that hosts your ___domain(s) and this will be
4+
specifically used when requesting new _Certificates_ via DNS Validation.
5+
6+
It is preferred to use DNS Validation, so check if your ___domain is hosted with
7+
one of the supported Acme.sh providers:
8+
9+
- [DNS Page 1](https://github.com/acmesh-official/acme.sh/wiki/dnsapi)
10+
- [DNS Page 2](https://github.com/acmesh-official/acme.sh/wiki/dnsapi2)
11+
12+
Should your DNS Provider be supported by Acme.sh and not available in this
13+
project, please
14+
[open an issue on Github](https://github.com/NginxProxyManager/nginx-proxy-manager/issues/new/choose).

‎frontend/src/locale/src/HelpDoc/de/Hosts copy.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
# Hosts Help
2+
3+
todo

‎frontend/src/locale/src/HelpDoc/de/Hosts.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
# Hosts Help
2+
3+
todo

‎frontend/src/locale/src/HelpDoc/de/NginxTemplates.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
# Nginx Templates Help
2+
3+
todo

‎frontend/src/locale/src/HelpDoc/de/Upstreams.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
# Upstreams Help
2+
3+
todo

‎frontend/src/locale/src/HelpDoc/de/index.ts

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1 +1,7 @@
1+
export * as AccessLists from "./AccessLists.md";
2+
export * as Certificates from "./Certificates.md";
13
export * as CertificateAuthorities from "./CertificateAuthorities.md";
4+
export * as DNSProviders from "./DNSProviders.md";
5+
export * as Hosts from "./Hosts.md";
6+
export * as NginxTemplates from "./NginxTemplates.md";
7+
export * as Upstreams from "./Upstreams.md";

‎frontend/src/locale/src/HelpDoc/en/Certificates.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -24,11 +24,13 @@ certificate. Nor do you need to have your _Host_ configured for HTTP access.
2424

2525
## Custom Certificate
2626

27-
todo
27+
Use this option to upload your own SSL Certificate, as provided by your own
28+
Certificate Authority.
2829

2930
## MKCert Certificate
3031

31-
todo
32+
This option will create a self-signed Certificate for development use. When
33+
viewing a _Host_ that using a MKCert Certificate, the browser will show errors.
3234

3335
## Choosing a Certificate Authority
3436

0 commit comments

Comments
 (0)