From b0d23f0f9daf2935de56646e599d40ff641cbbce Mon Sep 17 00:00:00 2001 From: David Luevano Alvarado Date: Sat, 17 Jul 2021 17:01:07 -0600 Subject: forgot to update repo --- blog/dst/a/xmpp_server_with_prosody.html | 9 +++++---- blog/dst/rss.xml | 12 ++++++------ blog/dst/sitemap.xml | 16 ++++++++-------- blog/src/.files | 2 +- blog/src/a/xmpp_server_with_prosody.md | 8 ++++---- 5 files changed, 24 insertions(+), 23 deletions(-) (limited to 'blog') diff --git a/blog/dst/a/xmpp_server_with_prosody.html b/blog/dst/a/xmpp_server_with_prosody.html index d25de3f..a2a09c2 100644 --- a/blog/dst/a/xmpp_server_with_prosody.html +++ b/blog/dst/a/xmpp_server_with_prosody.html @@ -416,7 +416,7 @@ Component "vjud.your.domain" "vjud"

You HAVE to read all of the configuration file, because there are a lot of things that you need to change to make it work with your server/domain. Test the configuration file with:

luac5.2 -p /etc/prosody/prosody.cfg.lua
-

Notice that by default prosody will look up certificates that look like sub.your.domain, but if you get the certificates as myself, you’ll have a single certificate for all subdomains, and by default it is in /etc/letsencrypt/live, which has some strict permissions. So, to import them you can run:

+

Notice that by default prosody will look up certificates that look like sub.your.domain, but if you get the certificates like I do, you’ll have a single certificate for all subdomains, and by default it is in /etc/letsencrypt/live, which has some strict permissions. So, to import it you can run:

prosodyctl --root cert import /etc/letsencrypt/live

Ignore the complaining about not finding the subdomain certificates and note that you will have to run that command on each certificate renewal, to automate this, add the --deploy-hook flag to your automated Certbot renewal system; for me it’s a systemd timer with the following certbot.service:

@@ -550,7 +550,7 @@ systemctl restart nginx.service 
pacman -S coturn

You can modify the configuration file (located at /etc/turnserver/turnserver.conf) as desired, but at least you need to make the following changes (uncomment or edit):

-
use-auth-secret
+
use-auth-secret
 realm=proxy.your.domain
 static-auth-secret=YOUR SUPER SECRET TURN PASSWORD
 

@@ -562,11 +562,11 @@ systemctl enable turnserver.service
 
You can test if your TURN server works at Trickle ICE. You may need to add a user in the turnserver.conf to test this.

 
Wrapping up

 
At this point you should have a working XMPP server, start/enable the prosody service now:

-
systemctl start prosody.service
+
systemctl start prosody.service
 systemctl enable prosody.service
 

 
And you can add your first user with the prosodyctl command (it will prompt you to add a password):

-
prosodyctl adduser user@your.domain
+
prosodyctl adduser user@your.domain
 

 
You may want to add a compliance user, so you can check if your server is set up correctly. To do so, go to XMPP Compliance Tester and enter the compliance user credentials. It should have similar compliance score to mine:

 

@@ -597,6 +597,7 @@ systemctl enable prosody.service
   

     
By David Luévano

     
Created: Wed, Jun 09, 2021 @ 05:24 UTC

+      
Modified: Thu, Jun 10, 2021 @ 04:42 UTC

     

   
Tags:
 english, server, tools, tutorial  

diff --git a/blog/dst/rss.xml b/blog/dst/rss.xml
index dd2556d..f796c37 100644
--- a/blog/dst/rss.xml
+++ b/blog/dst/rss.xml
@@ -13,8 +13,8 @@
     Copyright 2021 David Luévano Alvarado
     david@luevano.xyz (David Luévano Alvarado)
     david@luevano.xyz (David Luévano Alvarado)
-    Wed, 09 Jun 2021 05:24:56 GMT
-    Wed, 09 Jun 2021 05:24:56 GMT
+    Thu, 10 Jun 2021 04:42:19 GMT
+    Thu, 10 Jun 2021 04:42:19 GMT
     pyssg v0.5.9
     https://validator.w3.org/feed/docs/rss2.html
     30
@@ -371,7 +371,7 @@ Component "vjud.your.domain" "vjud"
 
You HAVE to read all of the configuration file, because there are a lot of things that you need to change to make it work with your server/domain. Test the configuration file with:

 
luac5.2 -p /etc/prosody/prosody.cfg.lua
 

-
Notice that by default prosody will look up certificates that look like sub.your.domain, but if you get the certificates as myself, you’ll have a single certificate for all subdomains, and by default it is in /etc/letsencrypt/live, which has some strict permissions. So, to import them you can run:

+
Notice that by default prosody will look up certificates that look like sub.your.domain, but if you get the certificates like I do, you’ll have a single certificate for all subdomains, and by default it is in /etc/letsencrypt/live, which has some strict permissions. So, to import it you can run:

 
prosodyctl --root cert import /etc/letsencrypt/live
 

 
Ignore the complaining about not finding the subdomain certificates and note that you will have to run that command on each certificate renewal, to automate this, add the --deploy-hook flag to your automated Certbot renewal system; for me it’s a systemd timer with the following certbot.service:

@@ -505,7 +505,7 @@ systemctl restart nginx.service
 
pacman -S coturn
 

 
You can modify the configuration file (located at /etc/turnserver/turnserver.conf) as desired, but at least you need to make the following changes (uncomment or edit):

-
use-auth-secret
+
use-auth-secret
 realm=proxy.your.domain
 static-auth-secret=YOUR SUPER SECRET TURN PASSWORD
 

@@ -517,11 +517,11 @@ systemctl enable turnserver.service
 
You can test if your TURN server works at Trickle ICE. You may need to add a user in the turnserver.conf to test this.

 
Wrapping up

 
At this point you should have a working XMPP server, start/enable the prosody service now:

-
systemctl start prosody.service
+
systemctl start prosody.service
 systemctl enable prosody.service
 

 
And you can add your first user with the prosodyctl command (it will prompt you to add a password):

-
prosodyctl adduser user@your.domain
+
prosodyctl adduser user@your.domain
 

 
You may want to add a compliance user, so you can check if your server is set up correctly. To do so, go to XMPP Compliance Tester and enter the compliance user credentials. It should have similar compliance score to mine:

 

diff --git a/blog/dst/sitemap.xml b/blog/dst/sitemap.xml
index 13213e7..4707c03 100644
--- a/blog/dst/sitemap.xml
+++ b/blog/dst/sitemap.xml
@@ -4,7 +4,7 @@
    xsi:schemaLocation="http://www.sitemaps.org/schemas/sitemap/0.9 http://www.sitemaps.org/schemas/sitemap/0.9/sitemap.xsd">
     
       https://blog.luevano.xyz/a/xmpp_server_with_prosody.html
-      2021-06-09
+      2021-06-10
       weekly
       1.0
     
@@ -59,43 +59,43 @@
 
     
       https://blog.luevano.xyz/tag/@english.html
-      2021-06-09
+      2021-06-10
       daily
       0.5
     
     
       https://blog.luevano.xyz/tag/@server.html
-      2021-06-09
+      2021-06-10
       daily
       0.5
     
     
       https://blog.luevano.xyz/tag/@short.html
-      2021-06-09
+      2021-06-10
       daily
       0.5
     
     
       https://blog.luevano.xyz/tag/@spanish.html
-      2021-06-09
+      2021-06-10
       daily
       0.5
     
     
       https://blog.luevano.xyz/tag/@tools.html
-      2021-06-09
+      2021-06-10
       daily
       0.5
     
     
       https://blog.luevano.xyz/tag/@tutorial.html
-      2021-06-09
+      2021-06-10
       daily
       0.5
     
     
       https://blog.luevano.xyz/tag/@update.html
-      2021-06-09
+      2021-06-10
       daily
       0.5
     
diff --git a/blog/src/.files b/blog/src/.files
index 979a2f6..7d88a59 100644
--- a/blog/src/.files
+++ b/blog/src/.files
@@ -9,4 +9,4 @@ a/mail_server_with_postfix.md 1616299559.6570284 1623137344.8639452 english,serv
 a/new_blogging_system.md 1622172099.117893 1622173322.4337702 english,short,tools,update
 a/asi_nomas_esta_quedando.md 1622795043.0874712 0.0 short,spanish,update
 a/acomodada_la_pagina_de_arte.md 1623006369.6071973 1623006525.2665823 short,spanish,update
-a/xmpp_server_with_prosody.md 1623216270.0372887 0.0 english,server,tools,tutorial
+a/xmpp_server_with_prosody.md 1623216270.0372887 1623300135.5528305 english,server,tools,tutorial
diff --git a/blog/src/a/xmpp_server_with_prosody.md b/blog/src/a/xmpp_server_with_prosody.md
index be3d610..e5d9607 100644
--- a/blog/src/a/xmpp_server_with_prosody.md
+++ b/blog/src/a/xmpp_server_with_prosody.md
@@ -364,7 +364,7 @@ You ???HAVE??? to read all of the configuration file, because there are a lot of
 luac5.2 -p /etc/prosody/prosody.cfg.lua
 ```
 
-Notice that by default `prosody` will look up certificates that look like `sub.your.domain`, but if you get the certificates as myself, you'll have a single certificate for all subdomains, and by default it is in `/etc/letsencrypt/live`, which has some strict permissions. So, to import them you can run:
+Notice that by default `prosody` will look up certificates that look like `sub.your.domain`, but if you get the certificates like I do, you'll have a single certificate for all subdomains, and by default it is in `/etc/letsencrypt/live`, which has some strict permissions. So, to import it you can run:
 
 ```sh
 prosodyctl --root cert import /etc/letsencrypt/live
@@ -534,7 +534,7 @@ pacman -S coturn
 
 You can modify the configuration file (located at `/etc/turnserver/turnserver.conf`) as desired, but at least you need to make the following changes (uncomment or edit):
 
-```
+```ini
 use-auth-secret
 realm=proxy.your.domain
 static-auth-secret=YOUR SUPER SECRET TURN PASSWORD
@@ -555,14 +555,14 @@ You can test if your TURN server works at [Trickle ICE](https://webrtc.github.io
 
 At this point you should have a working XMPP server, start/enable the `prosody` service now:
 
-```
+```sh
 systemctl start prosody.service
 systemctl enable prosody.service
 ```
 
 And you can add your first user with the `prosodyctl` command (it will prompt you to add a password):
 
-```
+```sh
 prosodyctl adduser user@your.domain
 ```
 
-- 
cgit v1.2.3-70-g09d2