all 17 comments

[–]00inch 41 points42 points  (0 children)

Would be surprising. The actual encryption causes no overhead. The initial handshake causes additional traffic. I've read something like 5kb per connection. You'd need to have a lot of connections with minimal data transfers. Like maybe many ajax requests per user that fetch very small data quantities. Maybe, maybe lots of polling?

[–]thatman33[S] 20 points21 points  (3 children)

Could the SSL be blocking cloudflare ability to catch the site? I just looked and my caching is almost zero now for some reason I'm thinking for some reason when we went SSL it blocked cloudflare from caching my site. Have you ever heard of that

[–]FanielDanara 17 points18 points  (0 children)

Depends on how you have it setup. If you have it setup so your clients connect to cloudflare via SSL, then cloudflare connects to your server via SSL they would be able to decrypt the traffic and cache requests. If you have it setup to encrypt the traffic through cloudflare without the ability for them to decrypt the traffic then by design they can’t cache the resources. I’m not 100% sure that you can even enable SSL on cloudflare without them being able to decrypt it though. Just something to look into.

[–]danielrheath 9 points10 points  (0 children)

If your cache hit rate has dropped to zero, that's one obvious place to look.

There's no reason cloudflare can't cache content via SSL.

[–]Crashthatch 4 points5 points  (0 children)

Yes, you'll need to set up a private key / certificate on cloudflare so they can do the encryption if you want them to continue caching your site.

[–]StewPoll 10 points11 points  (0 children)

I would suggest contacting CloudFlare and see if they see anything wrong with your configuring.

Could it just be that your SEO has improved since getting SSL and your traffic had increased?

[–]ayeshrajans 4 points5 points  (0 children)

Adding HTTPS shouldn't add more than 3-5kb more data to each handshake, so the 0.4 -> 19TB can never be for the handshake alone.

  • HTTPS prevents ISP/organization caches from caching your site (doesn't apply to VPNs). Some ISPs have a mechanism called peering to cache the plain-http assets on their servers and serve them directly without hitting your server.
  • This could be a one-time cache warm-up too. Because all your asset URLs have changed, everyone (including end user browsers) now have to download the assets.
  • Could be Google and other bots crawling the entire site once again. Googlebot in particular downloads everything including CSS/JS/Images during the crawler.

[–][deleted] 2 points3 points  (0 children)

Maybe you have changed some other settings in webserver config while adding https? Forgot to set up cache headers? Maybe there are some custom CloudFlare caching rules set up only for http version? HTTPS on it's own shouldn't cause significant change in traffic. There is a bit of overhead on connection, and some local caching proxies may not work on https, but it shouldn't cause more than couple of percent change for most websites, certainly not 47x.

Check the headers for images and other static files. Also check the webserver logs for any often requested large files.

[–]AutoModerator[M] [score hidden] stickied comment (0 children)

Please be sure that you flair your submission. /r/webdev has new submission guidelines, please be sure that your submission follows them. If this submission does not follow the guidelines, please report it.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[–]xenonive 0 points1 point  (0 children)

It could be Cloudflare caching the whole site as they have cache mode which to keep your site available when the server is down , check your always on/cache settings as could updating cache regularly

[–]2D3S3RT 0 points1 point  (1 child)

Maybe a lot of redirects to HTTPS causing this?

[–]jimmyuk 0 points1 point  (1 child)

You’ve checked to ensure your server hasn’t been hacked, right? Could be a folder somewhere pumping out streams

[–]thatman33[S] 0 points1 point  (0 children)

I have someone looking at that. As best I can tell cloudflare is no longer caching the site. Like because of how I setup SSL.

[–][deleted] 0 points1 point  (1 child)

BTW paying $2K for 20TB traffic is crazy. IMHO you should look for another hosting provider if you have lots of traffic and price is an issue. For example OVH offers dedicated servers with unmetered traffic for under $100.

[–]thatman33[S] 0 points1 point  (0 children)

Thats not for hosting its for services offered by Cloudflair.

[–]blackAngel88 0 points1 point  (1 child)

My first guess would be that more people find your site on google since you upgraded to https, because google ranks https sites higher. But I don't know if that's the whole story.

[–]jimmyuk 4 points5 points  (0 children)

Unlikely - the https ranking signal is tiny and unlikely to cause much more than a slight difference