Certificate expired on diasp.in
We can switch to letsencrypt.org. Can anyone volunteer?
@vik All domain verification mails will be sent to fosscommunity.in@disroot.org, which is a email list and atleast 4 of us are subscribed.
letsencrypt.org will be much easier and simple as it verifies the server, not the domain owner via email. I can volunteer, if no one is interested, but I am not sure my key is added to the server.
@manukrishnantv @praveenarimbrathod I am a bit tied up in hamara dev today, sorry I can't help. @manukrishnantv if you cannot get in with your key I will try and reach @saurabh to get that sorted out.
I will get time later tonight, I will do it if it is not done by then. @fayadfami @akshay @balasankarchelamat can you folks add @manukrishnantv 's key?
I don't even have my key added to diasp.in server. :D
@akshay @fayadfami help needed.
I will login in 15 mins. Will update.
@manukrishnantv You are in. Try now.
Added letsencrypt SSL and restarted nginx. Things should be fine. If stream is not getting updated, please restart diaspora too.
Thanks @manukrishnantv ! We should document things here https://gitlab.com/piratemovin/diasp.in-wiki/wikis/home Though I prefer just a single repo for homepage and wiki.
@fayadfami @akshay how about changing diasp.in-homepage to just diasp.in and using its wiki part for documentation?
Yes, that looks more organized.
@fayadfami I have started https://gitlab.com/piratemovin/diasp.in/wikis/home and you can delete the other repo.
@praveenarimbrathod I am still seeing the old certificate and the expiry warning when trying to use xmpp. Is the certificate for the xmpp service handled differently?
@vik yes, prosody configuration (/etc/prosody/prosody.cfg.lua) is still using the old certificates. /etc/nginx/sites-available/diasp.in has path for the new certificates. I'll update prosody now.
@vik I have made the changes, can you confirm?
Added prosody user to acl
sudo setfacl -m u:prosody:rx /etc/letsencrypt/live/
and
sudo setfacl -m u:prosody:rx /etc/letsencrypt/live/diasp.in
acl's were not enough as it was a symlink. I changed group of /etc/letsencrypt/live and /etc/letsencrypt/archive and subdirectories to ssl-cert which includes prosody. I also made chmod g+rx for these. @manukrishnantv can you make sure new certs generated by letsencrypt has root:ssl-cert ownership?
cool, xmpp is back up and running now
https://xmpp.net/result.php?domain=diasp.in&type=server shpws our certficate score as B for allowing SSLv3. I think we should disable it.
I have documented these details at https://gitlab.com/piratemovin/diasp.in/wikis/tls @manukrishnantv @fayadfami @vik add anything missing there.
@praveenarimbrathod i don't have the rights to delete repositories. Can you remove piratemovin/diasp.in-wiki.
Done.
@fayad You are now an owner. :D
@fayadfami @akshay can you fix the podupti.me listing for diasp.in? I think we got a negative score when certificate was expired and it was never retried.
Just opened an issue https://github.com/diasporg/Poduptime/issues/36
Gave a request to podupti.me for editing existing server details. And sent a message to David about it. @praveenarimbrathod
Edit. Diasp.in has been updated. But more to do before it takes effect. https://codema.in/d/CEBGMiT5/update-diaspora-to-0-5-6-3#comment-920037
@praveenarimbrathod @saurabh @manukrishnantv The SSL certificate has expired so users are getting an untrusted warning. Who currently controls the certificate?