Updating letsencrypt and virtual environment dependencies…
Running with virtualenv: /root/.local/share/letsencrypt/bin/letsencrypt --apache
The apache plugin is not working; there may be problems with your existing configuration.
The error was: PluginError(‘Unable to parse runtime variables’,)
VirtualHost configuration:
wildcard NameVirtualHosts and default servers: default:443 your_domain.com (/etc/apache2/sites-enabled/default-ssl.conf:2)
*:80 is a NameVirtualHost
default server vps-7809.fhnet.fr (/etc/apache2/sites-enabled/000-default:1)
port 80 namevhost vps-7809.fhnet.fr (/etc/apache2/sites-enabled/000-default:1)
Syntax OK
ok… but clearly: do you know what command should I type in ?
(I guess many people still use apache2.2): that would be great to just have the command for apache2.2 instead of trying to make tests, search, posts in forums…
Updating letsencrypt and virtual environment dependencies.......
Running with virtualenv: /root/.local/share/letsencrypt/bin/letsencrypt certonly --standalone -d nextechanisme.com -d www.nextechangisme.com
Failed authorization procedure. nextechanisme.com (http-01): urn:acme:error:connection :: The server could not connect to the client for DV :: Server failure at resolver
Do you own nextechangisme.com? if so you need to point the domain to your server, as it’s currently hosted elsewhere.
LE is checking that you own the domain before it issues a certificate, hence it expects the domain to be on the server you are asking for an SSL certificate for.
for the method you are using ( default) it needs to place code within a specific place on your webserver ( in .well-known/acme-challenge folder ) that it then checks - so confirm that you have control on that domain.
ok, any idea why it just does not work ?
I am on the nextechangisme.com server with SSH, type in the right command and … nothing.
Still did not find the solution to my problem.
I am fighting for 2 hours to make it work on apache2.2
I guess many people are using apache2.2 so… why not to publish a step/step guide for apache2.2 ?
As you are doing a non-automatic configuration, you should edit the Apache configuration file of your HTTPS (virtual)host yourself. You should set the following settings: