CDN77 Help - Setting up the CDN

[MattW]

Something I've been working on

 

[p4guru]

nice !

 

[speedway]

Yes please!

 

[MattW]

Yes please!

http://xenforo.com/community/resources/cdn77-com-stats.1823/

 

[speedway]

You da man! Thanks Matt!

 

[speedway]

All done - brilliant addon!

 

[MattW]

Fantastic. I'm going to try and get it updated over the weekend to store the data in the DataRegistry and grab it via a cron so it doesn't need to call the API each time you access the ACP home page.

 

[MattW]

Updated: http://xenforo.com/community/resources/cdn77-com-stats.1823/updates

 

[Mouth]

I've had lots of problems using CDN77 servers with https - just a heads-up.

My site is https, hence why I want CDN resources to load via https. BUT, the CDN77 servers only connect to your site via http (not https) to download/cache and thus if your site is https then they fail and server errors and timeouts is given to your site users.

 

[MattW]

I've had lots of problems using CDN77 servers with https - just a heads-up.

My site is https, hence why I want CDN resources to load via https. BUT, the CDN77 servers only connect to your site via http (not https) to download/cache and thus if your site is https then they fail and server errors and timeouts is given to your site users.

Have you set up the CDN using their shared SSL offering?

 

[Mouth]

Have you set up the CDN using their shared SSL offering?

Yes, or more accurately my hosting provider did whom partner with them for the CDN service they offer to customers.

 

[MattW]

Hmm, I'll try setting one up later on and see if I can get it working.

 

[Mouth]

Hmm, I'll try setting one up later on and see if I can get it working.

I doubt you will - the information I gave is a direct response from CDN77 engineer after my hosting provider escalated my support ticket of lots of issues and timeouts with https CDN. Here's the cut n paste ...

Engineers got back to me and the problem is the caching mechanism that pulls content from your site is done through HTTP only and since the site forces everything to be HTTPS it's causing the problem:

From the engineer -
When the edge servers pull content from the origin, it always pull from "http". We noticed that the origin is forced to serve from https, this is not supported in our system.

As for the 504 you saw, we found the following in our log. It seems nginx was trying to access the origin to grab for content, but failed to connect:

"May 15 06:56:08 127772854 2013/05/15 06:56:08 [error] 3898#0: *854090 upstream timed out (110: Connection timed out) while connecting to upstream, client: 203.11.81.236, server: netrider.r.worldssl.net, request: "GET /data/avatars/s/41/41229.jpg?1365981353 HTTP/1.1", upstream: "http://110.34.169.212:80/data/avatars/s/41/41229.jpg?1365981353", host: "netrider.r.worldssl.net", referrer: "https://www.netrider.net.au/forum/"

Also appears they are accessing your server (upstream/origin) via IP address and not host name, so if you have multiple hosts on your webserver and your site is not the default for the IP address it will also fail due to a second point of failure for CDN77

 

[MattW]

Oh, that's not very good then!

 

[Mouth]

Yeah. I was quite disappointed. Was even looking at 'upgrading' my 'free' CDN via them and becoming a direct customer for the additional stats etc. but with this there is no point. I cannot even use CDN with them, let alone become a direct customer.

 

[MattW]

Also appears they are accessing your server (upstream/origin) via IP address and not host name, so if you have multiple hosts on your webserver and your site is not the default for the IP address it will also fail due to a second point of failure for CDN77

I do have them working on my second VPS for my dev site. There are multiple sites on there sharing the same IP address, and the pull zone CDN works fine.

 

[Mouth]

I do have them working on my second VPS for my dev site. There are multiple sites on there sharing the same IP address, and the pull zone CDN works fine.

Good news, maybe it's only HTTPS origins that it accessing via return IP address

 

[AlexT]

I've had lots of problems using CDN77 servers with https - just a heads-up.

My site is https, hence why I want CDN resources to load via https. BUT, the CDN77 servers only connect to your site via http (not https) to download/cache and thus.

CDN for https, if offered, can be quite expensive. My CDN is Edgecast. They offer https, but it costs you several hundred $ extra per month, and even much much more so if you want to have a custom certificate (for vanity CDN URLs).

 

[Mouth]

CDN for https, if offered, can be quite expensive. My CDN is Edgecast. They offer https, but it costs you several hundred $ extra per month

Amazon's CDN is only approx 20% more for https requests (traffic is the same, regardless)!