Daemon Setup

Contents

Introduction

This section provides steps on securing your SingularityNet Daemon with Certbot from Let’s Encrypt. Let’s Encrypt is a nonprofit Certificate Authority (CA) that provides an easy way to obtain and install free TLS/SSL certificates, thereby enabling encrypted HTTPS on web servers. It simplifies the process by providing a software client, Certbot, that attempts to automate most (if not all) of the required steps. Currently, the entire process of obtaining and installing a certificate is fully automated. The Lets Encryptgetting started guide gives a detailed explanation on using Lets Encrypt.

Prerequisites

  • A fully registered domain name. This guide uses daemon_domain as an example throughout.

Step 1 — Installing Certbot

Install certbot using the guide here - Install certbot on the server that will host the certificate - For software, select “None of the Above”, and choose your OS to get detail install intructions. - If you are using Ubuntu 18.04 LTS you can go direct to: https://certbot.eff.org/lets-encrypt/ubuntubionic-other

Step 2 — Obtaining an SSL Certificate

We use the certbot authenticator to obtain an SSL Certificate. The certbot authenticator validates that you control the domain(s) you are requesting a certificate for, obtains a certificate for the specified domain(s), and places the certificate in the /etc/letsencrypt directory on your machine. The authenticator does not install the certificate (it does not edit any of your server’s configuration files to serve the obtained certificate). If you specify multiple domains to authenticate, they will all be listed in a single certificate. To obtain multiple separate certificates you will need to run Certbot multiple times.

Here is an example of the running the sudo certbot certonly command, for <daemon_domain>

$ sudo certbot certonly
Saving debug log to /var/log/letsencrypt/letsencrypt.log

How would you like to authenticate with the ACME CA?
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
1: Spin up a temporary webserver (standalone)
2: Place files in webroot directory (webroot)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Select the appropriate number [1-2] then [enter] (press 'c' to cancel): 1   
Plugins selected: Authenticator standalone, Installer None
Enter email address (used for urgent renewal and security notices) (Enter 'c' to
cancel): joe@daemon_domain.sh

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Please read the Terms of Service at
https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf. You must
agree in order to register with the ACME server at
https://acme-v02.api.letsencrypt.org/directory
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
(A)gree/(C)ancel: A

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Would you be willing to share your email address with the Electronic Frontier
Foundation, a founding partner of the Let's Encrypt project and the non-profit
organization that develops Certbot? We'd like to send you email about our work
encrypting the web, EFF news, campaigns, and ways to support digital freedom.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
(Y)es/(N)o: n
Please enter in your domain name(s) (comma and/or space separated)  (Enter 'c'
to cancel): <daemon_domain>
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for <daemon_domain>
Waiting for verification...
Cleaning up challenges

IMPORTANT NOTES:
 - Congratulations! Your certificate and chain have been saved at:
   /etc/letsencrypt/live/<daemon_domain>/fullchain.pem
   Your key file has been saved at:
   /etc/letsencrypt/live/<daemon_domain>/privkey.pem
   Your cert will expire on 2019-05-22. To obtain a new or tweaked
   version of this certificate in the future, simply run certbot
   again. To non-interactively renew *all* of your certificates, run
   "certbot renew"
 - Your account credentials have been saved in your Certbot
   configuration directory at /etc/letsencrypt. You should make a
   secure backup of this folder now. This configuration directory will
   also contain certificates and private keys obtained by Certbot so
   making regular backups of this folder is ideal.
 - If you like Certbot, please consider supporting our work by:

   Donating to ISRG / Let's Encrypt:   https://letsencrypt.org/donate
   Donating to EFF:                    https://eff.org/donate-le

Step 3 — Getting the certificate path

Get the certificate path and key using the command: sudo certbot certificates. This is needed for configuring the SingularityNet daemon

$ sudo certbot certificates
Saving debug log to /var/log/letsencrypt/letsencrypt.log

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Found the following certs:
  Certificate Name: <daemon_domain>
    Domains: <daemon_domain>
    Expiry Date: 2019-05-22 23:22:26+00:00 (VALID: 89 days)
    Certificate Path: /etc/letsencrypt/live/<daemon_domain>/fullchain.pem
    Private Key Path: /etc/letsencrypt/live/<daemon_domain>/privkey.pem
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Step 4 — Mount certificate path (Only required if the daemon is being run in a docker container)

Based on the certificate paths from above, mount the certificate dir as a volume in your docker container. Note that the certificates may be symbolic links, so you can’t just mount /etc/letsencrypt/live/<daemon_domain>/.

$ sudo ls -la /etc/letsencrypt/live/<daemon_domain>/
total 12
drwxr-xr-x 2 root root 4096 Feb 22 00:22 .
drwx------ 3 root root 4096 Feb 22 00:22 ..
lrwxrwxrwx 1 root root   42 Feb 22 00:22 cert.pem -> ../../archive/<daemon_domain>/cert1.pem
lrwxrwxrwx 1 root root   43 Feb 22 00:22 chain.pem -> ../../archive/<daemon_domain>/chain1.pem
lrwxrwxrwx 1 root root   47 Feb 22 00:22 fullchain.pem -> ../../archive/<daemon_domain>/fullchain1.pem
lrwxrwxrwx 1 root root   45 Feb 22 00:22 privkey.pem -> ../../archive/<daemon_domain>/privkey1.pem
-rw-r--r-- 1 root root  692 Feb 22 00:22 README

Directory listing shows us that the link is relative and jumps two directories above. This means we need to mount /etc/letsencrypt (or mount where it points, e.g. /etc/letsencrypt/archive/<daemon_domain>, but this could break if certbot changes how it stores certs and manages renewals)

$ docker run -v /etc/letsencrypt:/etc/letsencrypt [...]

Step 5 — Schedule renewal of certificates

Let’s Encrypt certificates are valid for 90 days and need to be renewed post that. Check cron or systemd timer is in place for renewal of certificates:

cat /etc/cron.d/certbot or systemctl show certbot.timer

(Ubuntu 18.04 uses systemd, so the latter command is the important one on that platform).

When the certificate updates, you’ll have to restart your services so that snet daemon uses the new certificate.

To do this, you can add a script to /etc/letsencrypt/renewal-hooks/deploy

$ sudo bash -c 'cat > /etc/letsencrypt/renewal-hooks/deploy/restart_services.sh'
#!/bin/bash
docker restart [SERVICE_CONTAINER_NAME]
^D
$ chmod u+x /etc/letsencrypt/renewal-hooks/deploy/restart_services.sh

Last modified on : 16-Jul-21

Sign up for developer updates

×