LetsEncrypt fail

I'm a Linux n00b that took over for a departed dev, trying to activate LetsEncrypt in Laravel Forge on a server with PHP 7.1.8-2+ubuntu16.04.1+deb.sury.org+4 (cli).

When I activated LetsEncrypt with my Route53 keys, it failed with a series of errors that I'm not sure how to address (below). Any hints?

Thanks, John

===========================================================

--2018-08-18 14:17:20-- https://forge-certificates.laravel.com/le/396854/386548?env=production

Resolving forge-certificates.laravel.com (forge-certificates.laravel.com)... 104.25.8.32, 104.25.9.32, 2400:cb00:2048:1::6819:820, ...

Connecting to forge-certificates.laravel.com (forge-certificates.laravel.com)|104.25.8.32|:443... connected.

HTTP request sent, awaiting response... 200 OK

Length: unspecified [text/html]

Saving to: ‘letsencrypt_script1534601840’

0K .... 68.1M=0s

2018-08-18 14:17:21 (68.1 MB/s) - ‘letsencrypt_script1534601840’ saved [4162]

debconf: unable to initialize frontend: Dialog

debconf: (TERM is not set, so the dialog frontend is not usable.)

debconf: falling back to frontend: Readline

debconf: unable to initialize frontend: Readline

debconf: (This frontend requires a controlling tty.)

debconf: falling back to frontend: Teletype

dpkg-preconfigure: unable to re-open stdin:

Cloning into 'letsencrypt1534601841'...

Traceback (most recent call last):

File "/usr/bin/pip", line 9, in <module>

from pip import main

ImportError: cannot import name main_

Tried again and it returned a somewhat different (Python) error:

===============================================================================

--2018-08-18 15:43:54-- https://forge-certificates.laravel.com/le/396870/386548?env=production

Resolving forge-certificates.laravel.com (forge-certificates.laravel.com)... 104.25.9.32, 104.25.8.32, 2400:cb00:2048:1::6819:820, ...

Connecting to forge-certificates.laravel.com (forge certificates.laravel.com)|104.25.9.32|:443... connected.

HTTP request sent, awaiting response... 200 OK

Length: unspecified [text/html]

Saving to: ‘letsencrypt_script1534607034’

0K .... 72.6M=0s

2018-08-18 15:43:55 (72.6 MB/s) - ‘letsencrypt_script1534607034’ saved [4162]

debconf: unable to initialize frontend: Dialog

debconf: (TERM is not set, so the dialog frontend is not usable.)

debconf: falling back to frontend: Readline

debconf: unable to initialize frontend: Readline

debconf: (This frontend requires a controlling tty.)

debconf: falling back to frontend: Teletype

dpkg-preconfigure: unable to re-open stdin:

Cloning into 'letsencrypt1534607035'...

Traceback (most recent call last):

File "/usr/local/bin/lexicon", line 11, in <module>

sys.exit(main())

File "/usr/local/lib/python2.7/dist-packages/lexicon/main.py", line 124, in main

parsed_args = MainParser().parse_args()

File "/usr/local/lib/python2.7/dist-packages/lexicon/main.py", line 59, in MainParser

provider_module = importlib.import_module('lexicon.providers.' + provider)

File "/usr/lib/python2.7/importlib/init.py", line 37, in import_module

import(name)

File "/usr/local/lib/python2.7/dist-packages/lexicon/providers/googleclouddns.py", line 9, in <module>

from cryptography.hazmat.backends import default_backend

ImportError: No module named cryptography.hazmat.backends

You have a missing python module try

sudo pip install cryptography --force-reinstall

So Laravel Forge apparently did something on their end that fixed the Python issues...but now I have a new issue. Trying to install LetsEncrypt SSL now results in this error:

--2018-11-19 18:42:14--  https://forge-certificates.laravel.com/le/445001/386548?env=production
Resolving forge-certificates.laravel.com (forge-certificates.laravel.com)... failed: Temporary failure in name resolution.
wget: unable to resolve host address ‘forge-certificates.laravel.com’

That "temporary failure" has been going on all day, so I suspect that it's not truly temporary.

Same here. The "temporary failure" has been going on all day... showbox