Has LL just started to use Cloudflare?

[bjornk]

I've just got a DNS resolution error for LL and then CloudFlare error page (522) showed up. LL's IP address and the SSL certificate is different now. Has anyone else noticed?

[spoonsinger]

I've just got a DNS resolution error for LL and then CloudFlare error page (522) showed up. LL's IP address and the SSL certificate is different now. Has anyone else noticed?

 

Nope. (obviously to the "Has anyone else noticed?" bit - because I haven't noticed any change).

 

[bjornk]

What do you mean? Is the IP address and the certificate still the same for you?

 

On my end, https://www.loverslab.com/ now uses a certificate issued to CloudFlare and issued by Comodo, IIRC it was a RapidSSL certificate before. The two IP addresses for LL now both belong to CloudFlare. 

[Slammer64]

Same here bjornk, it's changed back to Cloudflare again.

[Cynical Misanthrope]

LL was a little bit wonky for me yesterday. That's when I noticed it uses Cloudflare as well.

[Caffeine Addict]

I am getting a lot of errors in the last couple of days, not sure if it is since cloudflare is involved, telling me that the site is offline?

 

[Guest]

LoversLab is not on CloudFlare.

It uses a different provider for the server that hosts the actual site (the application IPB.)

 

But the provider that is used by LoversLab uses CloudFlare as network infrastructure to reach all the locations of this World.

 

CloudFlare has a "shadow" mechanism. If a site is down, it uses a cached version to still give access. This is wonderful if you "read only" the site, you will not notice any difference.

But for sites with "interactions" (Posting, Log-in, Uploads, etc.) then CloudFlare cannot really use the "Cached" version of the site, and reports some types of errors (like "host is down".)

 

 

 

You => Your Internet Provider => [maybe intermediate network] => CloudFlare => LL Hosting provider => LL Server (the Host)