Hi Folks i succesfully installed Cerbot certificate on my Website, but still if i try to open the website in a browser it shows a warning, which reads :“the website you’re trying to reach isn’t safe…reason: uknown certificate.” ? I installed cerbot via ssh and the automated installation process, has anybody an idea where i made a mistake?
My domain is: www.tobiaswichmann.com
I ran this command:
sudo certbot --apache
It produced this output:
“the website you’re trying to reach isn’t safe…reason: uknown certificate.”
My web server is (include version):
The operating system my web server runs on is (include version):
windows
My hosting provider, if applicable, is:
ovh
I can login to a root shell on my machine (yes or no, or I don’t know):
yes
I’m using a control panel to manage my site (no, or provide the name and version of the control panel):
Putty
Hello Juergen, unfortunetly i can’t find the vHosts configuration file, what i have in my apache 2 folder are the following: apache2.conf conf-enabled magic mods-enabled sites-available ssl
conf-available envvars mods-available ports.conf sites-enabled ssl.conf
is it located in one of those ? thanks again for the help
Hi Jürgen sorry for the late answer i think i finally found the vhost config file under sites enabled:
<VirtualHost *:443>
# The ServerName directive sets the request scheme, hostname and port that
# the server uses to identify itself. This is used when creating
# redirection URLs. In the context of virtual hosts, the ServerName
# specifies what hostname must appear in the request’s Host: header to
# match this virtual host. For the default virtual host (this file) this
# value is not decisive as it is used as a last resort host regardless.
# However, you must set it for any further virtual host explicitly. #ServerNamewww.example.com
ServerAdmin webmaster@localhost
DocumentRoot /var/www/html
# Available loglevels: trace8, ..., trace1, debug, info, notice, warn,
# error, crit, alert, emerg.
# It is also possible to configure the loglevel for particular
# modules, e.g.
#LogLevel info ssl:warn
Redirect "/" "https://tobiaswichmann.com/"
ErrorLog ${APACHE_LOG_DIR}/error.log
CustomLog ${APACHE_LOG_DIR}/access.log combined
# For most configuration files from conf-available/, which are
# enabled or disabled at a global level, it is possible to
# include a line for only one particular virtual host. For example the
# following line enables the CGI configuration for this host only
# after it has been globally disabled with "a2disconf".
#Include conf-available/serve-cgi-bin.conf
ServerName www.tobiaswichmann.com
Include /etc/letsencrypt/options-ssl-apache.conf
SSLCertificateFile /etc/letsencrypt/live/www.tobiaswichmann.com/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/www.tobiaswichmann.com/privkey.pem
From the <VirtualHost *:443> block, yes, just erase it completely. If you have a similar redirect in a <VirtualHost *:80> block you can leave that there.
Looks like you have yet another redirect somewhere. The one that’s kicking in now has an additional error, it’s removing the slash from the end of the domain name (e.g. try requesting https://www.tobiaswichmann.com/test and you get redirected to https://www.tobiaswichmann.comtest - that didn’t happen before, I think). So look through the rest of your Apache configuration including any .htaccess files for another redirect or rewrite rule that might be causing this.
