[Freedombox-discuss] Trying to add Lets Encrypt to FreedomBox
agropper at healthurl.com
Sun Jan 3 05:35:15 UTC 2016
I used the Debian instructions for apache. Had to log in as root from the
VM console and stop apache2. It asked about "no names were found..." which
I found a bit troubling but I accepted the default.
Here's what I did:
Get a Domain
Get a domain: https://ap.www.namecheap.com/ myas.xyz cost $1.18
Make an A-Record to 126.96.36.199 and a CNAME for host www to
Install Let’s Encrypt
sudo apt-get update
sudo apt-get install letsencrypt python-letsencrypt-apache
Login as root from the Digital Ocean console
Stop apache2: sudo service apache2 stop
/etc/letsencrypt$ ls now shows: accounts csr keys renewal
“No host names found…” Accept default
Test with: https://www.ssllabs.com/ssltest/analyze.html?d=myas.xyz
Debian is amazing and Let's Encrypt has done a really nice job and
FreedomBox rocks. Now if we could get the domain and cert right in plinth...
On Saturday, January 2, 2016, Sunil Mohan Adapa <sunil at medhas.org> wrote:
> On 01/03/2016 12:18 AM, Adrian Gropper wrote:
> > I'm running FreedomBox on a Digital Ocean VM at https://myas.xyz (ask me
> > directly if you want access)
> > I tried to follow the instructions at
> > https://letsencrypt.org/howitworks/ and it fails with:
> > fbx at MyAS:~/letsencrypt$ ./letsencrypt-auto --apache
> > Updating letsencrypt and virtual environment dependencies.....Command
> > "/home/fbx/.local/share/letsencrypt/bin/python2.7 -c "import setuptools,
> > 'open', open)(__file__).read().replace('\r\n', '\n'), __file__,
> > 'exec'))" install --record
> > /tmp/user/1001/pip-Fpnu4C-record/install-record.txt
> > --single-version-externally-managed --compile --install-headers
> > /home/fbx/.local/share/letsencrypt/include/site/python2.7/cryptography"
> > failed with error code 1 in /tmp/user/1001/pip-build-m794u0/cryptography
> > I've shared the complete terminal log here:
> > I'm reluctant to go directly to Let's Encrypt for help because I'm such
> > a newbie with the FreedomBox environment.
> > Can anyone suggest what to try next?
> Let's Encrypt is now available as Debian package in unstable and
> testing. Trying that might provide better results than installing from
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Freedombox-discuss