Hi Andrei,
many thanks!!! That was a great hint however it doesn't seem to be a solution yet. I quickly googled those lines and came up with this solution:
Remove of NameVirtualHost
In the file
/opt/bitnami/apps/aadictation/conf/httpd-vhosts.conf
I discovered two lines:
NameVirtualHost: *80
and
NameVirtualhost: *443
and removed them. Then I started the dry run command, as seen in my original post, again and the log file now it looks like this:
2017-09-29 10:31:54,468:DEBUG:certbot.renewal:Dry run: skipping updating lineage at /etc/letsencrypt/live/www.myhomepage.com
2017-09-29 10:31:54,469:DEBUG:certbot.renewal:no renewal failures
2017-09-29 10:31:54,469:INFO:certbot.hooks:Running post-hook command: sudo /opt/bitnami/ctlscript.sh start
Then I thought let's do it with verbose -v or -vv as rg305 suggested. When I startet this about 15 minutes later from a second shell it answered me:
Another instance of Certbot is already running.
So still the issue remains, that I never see my prompt anymore when running certbot.
UPDATE
Now I just discovered, if I restart my server from the second shell I do get a reaction from the first shell (which is still in progress with certbot). Before I restart the server from the second shell the first shell looks like this:
new certificate deployed without reload, fullchain is
/etc/letsencrypt/live/www.myhomepage.com/fullchain.pem
** DRY RUN: simulating 'certbot renew' close to cert expiry
** (The test certificates below have not been saved.)
Congratulations, all renewals succeeded. The following certs have been renewed:
/etc/letsencrypt/live/www.myhomepage.com/fullchain.pem (success)
** DRY RUN: simulating 'certbot renew' close to cert expiry
** (The test certificates above have not been saved.)
no renewal failures
Running post-hook command: sudo /opt/bitnami/ctlscript.sh start
.
With the cursor waiting below the last line.
But after I restarted the server from the second shell, the first shell looks like this:
new certificate deployed without reload, fullchain is
/etc/letsencrypt/live/www.myhomepage.com/fullchain.pem
** DRY RUN: simulating 'certbot renew' close to cert expiry
** (The test certificates below have not been saved.)
Congratulations, all renewals succeeded. The following certs have been renewed:
/etc/letsencrypt/live/www.myhomepage.com/fullchain.pem (success)
** DRY RUN: simulating 'certbot renew' close to cert expiry
** (The test certificates above have not been saved.)
no renewal failures
Running post-hook command: sudo /opt/bitnami/ctlscript.sh start
Output from sudo:
2017-09-29T11:01:21.270890Z mysqld_safe Logging to '/opt/bitnami/mysql/data/mysqld.log'.
2017-09-29T11:01:21.287518Z mysqld_safe Starting mysqld.bin daemon with databases from /opt/bitnami/mysql/data
/opt/bitnami/mysql/scripts/ctl.sh : mysql started at port 3306
/opt/bitnami/php/scripts/ctl.sh : php-fpm started
/opt/bitnami/apache2/scripts/ctl.sh : httpd started at port 80
2017-09-29T11:05:32.913037Z mysqld_safe mysqld from pid file /opt/bitnami/mysql/data/mysqld.pid ended
Error output from sudo:
Syntax OK
The last two lines Error output from sudo: and Syntax OK are written in red color.
Any help still very welcome.
I guess I have to solve this problem prior to creating a cron job for this?
Many thanks!
