Failed authorization procedure (http-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response

I my have hit on something: every time I run Let'd encrypt it creates a directory/home/nilandtrading/home/nilandtrading/public_html/.well-known/acme-challenge with an .htaccess file.

Performing the following challenges:
http-01 challenge for
http-01 challenge for
Using the webroot path /home/nilandtrading/home/nilandtrading/public_html for all unmatched domains.
Waiting for verification...
Cleaning up challenges
Unable to clean up challenge directory /home/nilandtrading/home/nilandtrading/public_html/.well-known/acme-challenge
Failed authorization procedure. (http-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from

This seems to have started Sept. 20th as per the Let's Encrypt Logs:

2017-09-20 15:40:44,854:DEBUG:certbot.main:certbot version: 0.17.0
2017-09-20 15:40:44,854:DEBUG:certbot.main:Arguments: ['-a', 'webroot', '-d', '', '-d', '', '-d', '', '-d', '', '--webroot-path', '/home/nilandtrading/home/nilandtrading/public_html', '--duplicate', '--manual-public-ip-logging-ok', '--config', '/tmp/.webmin/590663_25148_1_letsencrypt.cgi', '--rsa-key-size', '2048']
2017-09-20 15:40:44,854:DEBUG:certbot.main:Discovered plugins: PluginsRegistry(PluginEntryPoint#apache,PluginEntryPoint#manual,PluginEntryPoint#null,PluginEntryPoint#standalone,PluginEntryPoint#webroot)
2017-09-20 15:40:44,882:DEBUG:certbot.log:Root logging level set at 20

Not sure why the command 2017-09-20 15:40:44,854:DEBUG:certbot.main:Arguments: ['-a', 'webroot', '-d', '', '-d', '', '-d', '', '-d', '', '--webroot-path', '/home/nilandtrading/home/nilandtrading/public_html', '--duplicate', '--manual-public-ip-logging-ok', '--config', '/tmp/.webmin/590663_25148_1_letsencrypt.cgi', '--rsa-key-size', '2048']

But what ever has happen with Let's Encrypt I can no longer start apache2, as I now get the error;

Failed to start apache :
* Starting web server apache2
(98)Address already in use: AH00072: make_sock: could not bind to address [::]:80
(98)Address already in use: AH00072: make_sock: could not bind to address
no listening sockets available, shutting down
AH00015: Unable to open logs
Action 'start' failed.
The Apache error log may have more information.
* The apache2 instance did not start within 20 seconds. Please read the log files to discover problems

and have not been able to find out why? the ports.conf only has one statement each for 80 and 443 and I have found nothing else in the /apache2 folder that would cause this. Rebooting does not work.

:~$ grep Listen /etc/apache2/ports.conf
Listen 80
Listen 443

The command

~$ fuser -n tcp 80 | ps aux | grep PID
sysop    17457  0.0  0.0  11768  2140 pts/4    S+   08:31   0:00 grep --color=auto PID

shows sysop that would by my login
not sure what

~$ ss -plnt sport eq :80
State      Recv-Q Send-Q                            Local Address:Port                              Peer Address:Port
LISTEN     0      128                                           *:80                                           *:*    
LISTEN     0      128                                          :::80                                          :::*

indicates? other then it is listening, but when I run the command Top I can't find the PID?

At this Point the only thing I can thing to do is run deja-dup and restore a backup before Sept 20 (the last backup as my 500GB drive ran out of room). I also Have "Time shift" so maybe I can compare with this application

20 days of frustration trying to get a Cert from Let's Encrypt!!!



Regarding getting Apache up and running again, what is the output of these commands:

ps auxw | grep apache
netstat -anlp | grep :80

Log search showed this was installed by Let's encrypt re-installation and was added to the boot-up

But Apache2 is now working and I still get the same errors