|
|
@@ -209,7 +209,7 @@ ssh username@mydomainname -p 2222
|
|
209
|
209
|
sudo control
|
|
210
|
210
|
#+END_SRC
|
|
211
|
211
|
|
|
212
|
|
-Select *Security settings* then *Create a new Encrypt certificate*.
|
|
|
212
|
+Select *Security settings* then *Create a new Let's Encrypt certificate*.
|
|
213
|
213
|
|
|
214
|
214
|
One thing to be aware of is that Let's Encrypt doesn't support many dynamic DNS subdomains, such as those from freeDNS, so to run Hubzilla and GNU Social you will need to have your own official domains for those. There are many sites from which you can buy cheap domain names, and while this isn't ideal in terms of making you dependent upon another company it's the only option currently.
|
|
215
|
215
|
* How do I renew a Let's Encrypt certificate?
|
|
|
@@ -231,7 +231,7 @@ ssh username@mydomainname -p 2222
|
|
231
|
231
|
sudo control
|
|
232
|
232
|
#+END_SRC
|
|
233
|
233
|
|
|
234
|
|
-Select *Security settings* then *Create a new Encrypt certificate*.
|
|
|
234
|
+Select *Security settings* then *Create a new Let's Encrypt certificate*.
|
|
235
|
235
|
* Why use self-signed certificates?
|
|
236
|
236
|
Almost everywhere on the web you will read that self-signed certificates are worthless. They bring up /scary-scary looking/ browser warnings and gurus will advise you not to use them. Self-signed certificates are quite useful though. What the scary warnings mean - and it would be good if they explained this more clearly - is that you have an encrypted connection established but there is /no certainty about who that connection is with/.
|
|
237
|
237
|
|
Bob Mottram
9 年前