#letsencrypt

How To Renew A Let’s Encrypt Certificate #letsencrypt #ssl #https https://matechia.xyz/renew-letsencrypt-certificate/

matechia.xyz

Der @devtal Mailserver unterstützt jetzt (endlich) #letsencrypt

/dev/tal

<https: 912365021958672386="" gnuheidix="" status="" twitter.com=""> #LetsEncrypt #Hetzner</https:>

Ute Hauth

Sunday project: Huginn, Docker & Ansible

Some time ago I set up a #Twitter account posting #WWII "as it happened" events to #Socialhome (see here). This was accomplished using Zapier that reads the tweets and then POST's to the Socialhome API.

All that worked great and #Zapier is really nice. Except it's limited to 100 events per month on the free tier and this seems wasn't enough for the WWII tweets coming in. Zapier paid plans are from $20/mo which is way too much just to replicate some tweets.

At first I thought about making my own app to do all this but then I remembered running into Huginn, which I have been wanting to install anyway. It's basically a self-hosted #IFTT or Zapier, but allowing for even more complex stuff like unlimited chaining of events.

Docker + Ansible

I'm pretty new to #Docker but eventually I want to dockerize more of my apps. So of course I was happy to see #Huginn has a Docker image, allowing me to not have to muck about with any more #RoR apps. I use #Ansible for pretty much everything, so it made sense to build a playbook to deploy the app in a Docker container.

Luckily (or thanks to the fantastic Ansible team that is!), maintaining Docker containers with Ansible is as easy as doing anything else with it.

I chose to keep the web server out of the containers to use my standard #LetsEncrypt role for getting SSL on top. This made the role very simple, having only to 1) fetch SSL cert, 2) set up Apache to proxy and 3) push up a container.

The docker_container Ansible module call is basically just this:

 ---
 - docker_container:
   name: huginn
   image: huginn/huginn
   volumes:
     - "{{ huginn_db_volume_mount }}:/var/lib/mysql"
   env:
     APP_SECRET_TOKEN: "{{ huginn_secret }}"
     DOMAIN: "{{ huginn_domain }}"
     FORCE_SSL: "{{ huginn_https}}"
     INVITATION_CODE: "{{ huginn_invitation_code }}"
     MAIL_FROM_ADDRESS: "{{ huginn_mail_from }}"
     RAILS_ENV: production
     SMTP_DOMAIN: "{{ huginn_smtp_domain }}"
     SMTP_PASSWORD: "{{ huginn_smtp_password }}"
     SMTP_PORT: "{{ huginn_smtp_port }}"
     SMTP_SERVER: "{{ huginn_smtp_server }}"
     SMTP_USER_NAME: "{{ huginn_smtp_username }}"
     TWITTER_OAUTH_KEY: "{{ huginn_twitter_key }}"
     TWITTER_OAUTH_SECRET: "{{ huginn_twitter_secret }}"
   register: _docker_huginn

The container IP is then picked up from _docker_huginn by Apache to do the proxying.

The playbook itself, without any extra customization is pretty much here:

 ---
 - hosts: myhost
   become: yes
   become_user: root

   vars:
     letsencrypt_email: youremail@example.com
     huginn_domain: huginn.example.com
     huginn_invitation_code: changeme!
     huginn_secret: changeme!

   roles:
     - huginn

The result is the ansible-huginn role. Tested on #Ubuntu 14.04. Right now a bit limited in terms of configuration that can be passed in. Will expand as necessary.

Fun Huginn stuff

Some initial things I want to do is to use the chaining to make the tweet replicating not embed the tweet, but instead rip out the text + media and create a normal post instead. That should make for cleaner streams with less Twitter JS firing off.

Any tips on fun stuff to do with Huginn?

huginn/huginn
huginn - Create agents that monitor and act on your behalf. Your agents are standing by!

Jason Robinson

Getting Let’s Encrypt to app servers / firewalled networks

Does Let’s Encrypt (LE) support installation on servers with “random domain names”? The first impulse is to simply answer NO, you can’t do it, that’s the point of HTTPS, it makes sure you always talk to the right server. However, network configuration is a kind of magic.

[ #letsencrypt #server #network #domain #random #https ]

https://medium.com/enigma-shards/getting-lets-encrypt-to-app-servers-firewalled-networks-1a0b87772b1d

Getting Let’s Encrypt to app servers / firewalled networks
Does Let’s Encrypt (LE) support installation on servers with “random domain names”? The first impulse is to simply answer NO, you can’t do…

Erik

Let’s encrypt ejabberd

Back in May we announced that 2 ejabberd projects will participate in this year’s Google Summer of Code (GSoC) through the BEAM Community. The summer has ended and now it’s time to see the results!

[ #encryption #ejabberd #letsencrypt #xmpp #jabber ]

https://blog.process-one.net/lets-encrypt-ejabberd/

Let's encrypt ejabberd
Today we look at the first GSoC ejabberd project, aimed at implementing ejabberd support for "Let's Encrypt" ACME protocol.

Holger

hoy viernes a las 5 platiquemos con Noah Swartz

Viernes 1 de Septiembre a las 17:00

charlemos sobre letsencrypt, privacidad y metodologías para la autoprotección contra la vigilancia.

Boturini 61, esquina con Bolivar, Colonia Obrera, Ciudad Monstruo, MX

#eff #letsencrypt #mexico #ciudadmonstruo #autoprotección #privacidad

Rancho Electronico

https://twitter.com/letsencrypt/status/902949537374986240

#firefox #ssl #letsencrypt


Jason Robinson

#podmin #letsencrypt #apt-get #error

pod.dapor.net is online again - after error while renewing the lets encrypt certificates

#sorry for that #downtime

Frank

Certificate Transparency: Webanwendungen hacken, bevor sie installiert sind - Golem.de
<https: certificate-transparency-webanwendungen-hacken-bevor-sie-installiert-sind-1707-129116.html="" news="" www.golem.de="">
#SSL #Backdoor #Defcon #Drupal #Joomla #LetsEncrypt #Nextloud #Owncloud #Wordpress #Server</https:>

Golem (inoffiziell)

Does anyone use #letsencrypt certs with #prosody? Do you have an automated process to update the prosody certs?

Looks like something like this should work along with the renew-hook of certbot renew...

Jeremy Pope

Ausstellung und Verlängerung von SSL-Zertifikaten für deine Domain wird bei Febas vollautomatisch durchgeführt

Vielleicht für einen oder anderen Hubzilla-Knoten-Admin interessant

Let's Encrypt ist die Zertifizierungsstelle, welche Zertifikate kostenlos ausstellt. Diese Zertifikate werden von allen gängigen Browsern ohne Fehlermeldung akzeptiert. Die Ausstellung und Verlängerung wird beim Webspace-Provider Febas vollautomatisch durchgeführt. Zitiert von hier https://www.febas.de/support-zertifikat/

#letsencrypt #SSLZertifikate #SSLZertifikat #SSL #Webspace #WebspaceProvider #administrator

@{Deutschsprachige Nutzer+ ; deutsch@hubzilla.zottel.net} @{Hubzilla connected people. Workshop ; hucope@hubzilladev.homenet.org}

neue medienordnung plus