Hello every one
I use letencrypt to generate keys.
I get “A” on test https://www.ssllabs.com/ssltest/analyze.html?d=www.move-my-bag.ovh
my website: https://move-my-bag.ovh
Apache2 -v : Server version: Apache/2.4.7 (Ubuntu) Server built: Apr 3 2019 18:04:25
This si my configuration:
vim move-my-bag.ovh-le-ssl.conf
<IfModule mod_ssl.c>
<VirtualHost *:443>
ServerAdmin tchawima@yahoo.fr
DocumentRoot /var/www
<Directory /var/www>
Options Indexes FollowSymLinks MultiViews
AllowOverride All
Require all granted
Order allow,deny
allow from all
</Directory>
ServerName www.move-my-bag.ovh
ErrorLog ${APACHE_LOG_DIR}/error.log
CustomLog ${APACHE_LOG_DIR}/access.log combined
#debug, info, notice, warn, error, crit,alert, emerg.
LogLevel debug
RewriteEngine on
Include /etc/letsencrypt/options-ssl-apache.conf
SSLCertificateFile /etc/letsencrypt/live/www.move-my-bag.ovh/cert.pem
SSLCertificateKeyFile /etc/letsencrypt/live/www.move-my-bag.ovh/privkey.pem
SSLCertificateChainFile /etc/letsencrypt/live/www.move-my-bag.ovh/chain.pem
</VirtualHost>
vim move-my-bag.ovh.conf
<VirtualHost *:80>
ServerAdmin tchawima@yahoo.fr
DocumentRoot /var/www
<Directory /var/www>
Options Indexes FollowSymLinks MultiViews
AllowOverride All
Require all granted
</Directory>
ServerName move-my-bag.ovh
ErrorLog ${APACHE_LOG_DIR}/error.log
CustomLog ${APACHE_LOG_DIR}/access.log combined
RewriteEngine on
RewriteCond %{SERVER_NAME} =move-my-bag.ovh
RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent]
RewriteCond %{SERVER_NAME} =www.move-my-bag.ovh
RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent]
</VirtualHost>
Please help me
Hi @tchawima
I don’t see that error.
Instead, your configuration is ok ( https://check-your-website.server-daten.de/?q=move-my-bag.ovh ):
Your certificate has both domain names
CN=www.move-my-bag.ovh
03.06.2019
01.09.2019
expires in 89 days
move-my-bag.ovh, www.move-my-bag.ovh - 2 entries
so both connections are secure.
Your address
https://move-my-bag.ovh/bootstrap.min.css.map
sends html code, so this isn’t parseable.
Hello @JuergenAuer Thanks for your prompt reply.
How can I resolve my problem on Chrom? Because on Mozilla FireFox it works fine
https://move-my-bag.ovh/search
Capture on Chrom
It's a caching problem, not a real problem.
Real problem -> I would see it.
Clear your cache.
Oh, what’s that?
You should show the complete output.
Looks like your Chrome loads content via your ip address.
That’s always wrong, Letsencrypt certificates use only the domain name.
But your Chrome tries to load something, my Chrome doesn’t do that.
Why? I have no idea.
PS: It’s the port 8443.
PPS: Is this a Plesk port? Or an Apache Tomcat SSL?
https://move-my-bag.ovh:8443/ answers, but there is a self signed certificate.
No idea why Chrome checks that port.
Hello @JuergenAuer try this link on Chrom
https://move-my-bag.ovh/search
Withich cache will I reset?
It work well on Mozilla but not on Chrome.
I use Angular on front en Spring Data on back and I send the request https to my backend. So it’s nomal to have https://move-my-bag.ovh:8443/
I test this link on other pc but I got same error
There is the ip address used. That's wrong. You don't use this url:
I don’t understand what did you say. Could you please explain more?
Did you try this link https://move-my-bag.ovh/search on Chrome and Mozilla?
Which different did you get?
It's the same screenshot you have already shared:
There you see the ip address, not the domain name.
Yes of course. I have changed but same error.
This problem is on Chrome I think
It's not a Chrome problem, your port 8443 is wrong.
As written:
Checked directly - https://check-your-website.server-daten.de/?q=move-my-bag.ovh%3A8443
there is a self signed certificate:
CN=Unknown, OU=Unknown,
O=Unknown, L=Unknown, S=Unknown, C=Unknown
17.05.2019
14.05.2029
expires in 3631 days
1 Like
Hello @JuergenAuer
Thanks for your prompt reply.
Who do you explain that on Mozilla it work fine but on Chrome it does not work?
Check your code to find the difference.
system
Closed
July 7, 2019, 2:23pm
19
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.