PiluleRouge.com website inaccessible - HTTS certificate has expired 2 hours ago

Bastian

The Living Force
Hello.

I've tried to access PiluleRouge.com website a few minutes ago, it was inaccessible due to its expired HTTPS certificate :
Firefox (same with Chrome) said:
pilulerouge.com utilise un certificat de sécurité invalide.
Le certificat a expiré le mercredi 28 décembre 2016 11:48. La date courante est mercredi 28 décembre 2016 13:55.
Code d’erreur : SEC_ERROR_EXPIRED_CERTIFICATE

Yours.
 
Bastian said:
Hello.

I've tried to access PiluleRouge.com website a few minutes ago, it was inaccessible due to its expired HTTPS certificate :
Firefox (same with Chrome) said:
pilulerouge.com utilise un certificat de sécurité invalide.
Le certificat a expiré le mercredi 28 décembre 2016 11:48. La date courante est mercredi 28 décembre 2016 13:55.
Code d’erreur : SEC_ERROR_EXPIRED_CERTIFICATE

Yours.

I've tried and it opens without any problem with Chrome. Maybe it was some glitch on the server at the time you tried.
 
Konstantin said:
Bastian said:
Hello.

I've tried to access PiluleRouge.com website a few minutes ago, it was inaccessible due to its expired HTTPS certificate :
Firefox (same with Chrome) said:
pilulerouge.com utilise un certificat de sécurité invalide.
Le certificat a expiré le mercredi 28 décembre 2016 11:48. La date courante est mercredi 28 décembre 2016 13:55.
Code d’erreur : SEC_ERROR_EXPIRED_CERTIFICATE

Yours.

I've tried and it opens without any problem with Chrome. Maybe it was some glitch on the server at the time you tried.

I've just tried to access PiluleRouge.com via three of my browsers (Yandex, Rambler and Amigo) and it works well in all three so far.
 
I don´t get problem either, and I´ve tried with Chrome and Firefox, both are working fine. Maybe it´s just a passing fancy of our inexplicable matrix.
 
"Happy" new year !

Thank you three for your answers.

Today if I type in the address field of my browsers (FireFox & Chrome) : pilulerouge.com
...with both it gets redirected to : https://pilulerouge.com
and it works again. :)

But if I try : www.pilulerouge.com
with Chrome it gets redirected to : https://www.pilulerouge.com
but it displays CassWiki ! :huh:

...and FireFox displays that message :
FireFox said:
404 Not Found
nginx/1.4.4
:(

So I looked at the DNS (same IP for both addresses) and the HTTPS certificates, which are different (it looks like a misconfiguration of the web server) :
HTTPS certif for PR.com said:
Common Name: pilulerouge.com
Issuer: Let's Encrypt Authority X3
Expires: 56 days
Valid From: 11/28/2016
Valid To: 2/26/2017
Serial: 03991FF99BF46A89C9D77A96950A5600CF69
Algorithm: sha256RSA
HTTPS certif for www.PR.com said:
Common Name: thecasswiki.net
Issuer: Let's Encrypt Authority X3
Expires: 56 days
Valid From: 11/28/2016
Valid To: 2/26/2017
Serial: 035A738AAFC864577028DC4A16ACDF7CAB7E
Algorithm: sha256RSA
 
Hello,
URL _https://www.pilulerouge.com/ in Firefox give me :
_www.pilulerouge.com uses an invalid security certificate. The certificate is only valid for thecasswiki.net Error code: SSL_ERROR_BAD_CERT_DOMAIN
This error is telling you that the identification sent to you by the site is actually for another site. While anything you send would be safe from eavesdroppers, the recipient may not be who you think it is.
A common situation is when the certificate is actually for a different part of the same site. For example, you may have visited https://example.com, but the certificate is for https://www.example.com. In this case, if you access https://www.example.com directly, you should not receive the warning.
Like Bastian, I think there is a misconfiguration of the web server.
My two cents.

Happy new year at all...
 
Thanks for the error reports, the problems are fixed now.

Bastian said:
But if I try : www.pilulerouge.com

The "www" subdomains are still often typed in by users because it was widely used in the early days of the internet, but it no longer has any use or special meaning. It is now much more common to simply omit it (for shorter URLs and less typing work), or put language names or application names instead.
 
Data said:
Thanks for the error reports, the problems are fixed now.
You're welcome !

The "www" subdomains are still often typed in by users because it was widely used in the early days of the internet, but it no longer has any use or special meaning. It is now much more common to simply omit it (for shorter URLs and less typing work), or put language names or application names instead.
Well, indeed. My first Inet access was in 1996, so I'm still used to the old habit. But I take in account your remark, thanks.
 
Back
Top Bottom