Yes, but it might be more prudent to check the test file first. And when the test file works, try the certbot command.
1 Like
Hi. I have put:
RewriteEngine on
RewriteCond %{REQUEST_URI} !^/public/
RewriteCond %{REQUEST_URI} !^/.well-known/
RewriteRule ^(.*)$ /public/$1
and if you go here: http://live.streamingwebtv24.it/.well-known/acme-challenge/1234
now it plays.
So i run the command:
certbot run -a webroot -i apache -w /var/www/html -d live.streamingwebtv24.it -d www.live.streamingwebtv24.it
or only
certbot renew ?
Thank you.
I don't think the current .htaccess fix for the webroot problem is going to fix your apache plugin authenticator problem, but there is little harm in trying certbot renew just once to try it out.
If certbot renew still doesn't work, you'd have to run certbot like the second command you mentioned, to get the webroot info in the renewal configuration file. If that works, you can use certbot renew for future renewals.
1 Like
OMG!
Your existing certificate has been successfully renewed, and the new certificate
has been installed.
So later i have done to be sure:
certbot renew
and this is the result:
The following certs are not due for renewal yet:
/etc/letsencrypt/live/live.streamingwebtv24.it/fullchain.pem expires on 2019-05-29 (skipped)
No renewals were attempted.
Thank you so much!!!
Extra note: you realise your site http://live.streamingwebtv24.it doesn’t have a redirect to the secure HTTPS version, right?
Hi.
Yes i know that.
But if you go here: https://live.streamingwebtv24.it/
you can see it plays at the same.
For me it’s important that inside the streaming player code there is https.
Infact in the frame of streaming player i have this:
That had blocked your webroot.
1 Like
Yes i know.
But the platform installed need to have that block.
But using RewriteCond %{REQUEST_URI} !^/.well-known/
we have solved the issue. 
Thank you.
2 Likes
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.