@Janko1000,
I am very familiar with CDNs and also with the OVH CDN, that is very troublesome (in general and compared to other CDNs).
In fact, your (OVH) CDN is either delivering content directly (as a CDN should) OR delivering content indirectly with content from the Plesk server (as set up with Nginx/Apache), in which (latter) case
- the (OVH) CDN barely adds functionality, and
- visitor´s information (of various kinds) can and/or will be obscured (i.e. not visible or non-traceable)
In general, a CDN should be used to deliver (all) content (of a specific page or website) directly, otherwise the CDN does not have augmented value.
If the (OVH) CDN serves content directly, it should result in corresponding logs in the CDN and will
not result in significant log entries in the httpd/apache logs.
In short, it seems to be the case that you deliver CDN content indirectly, with content from the Plesk server.
Note that you are using the cloudflare apache module to serve (OVH) CDN content, implying that no problems result from that.
The cloudflare apache module works fine with or without nginx.
Also note that Plesk server with nginx/apache can perfectly work with cloudflare, implying that no problems should result from using a CDN with Plesk and nginx/apache.
The usage of cloudflare maybe slow(er), but it works fine with Plesk and provides all the relevant information you are stating to miss.
In short, you have to conclude that an undesirable setting is included in the (OVH) CDN and/or that the (OVH) CDN is not properly functioning (this occurs often).
You could consider the following options
a) get rid of the (OVH) CDN and serve content by means of Nginx/Apache AND, if and only if you need to serve reliable content throughout the world (the main target of a CDN), to add another Nginx/Apache server in a datacenter close to the customers using the content,
Note: this is, simply stated, creating a (cheaper) alternative, that inherently functions (almost) identical to a CDN
b) use Cloudflare, if you really need a CDN (that is reliable),
Note: Cloudflare offers (paid) packages, in which performance significantly increases. Performance should not be an issue, the budget for a CDN is.
c) (only) use Plesk with proper Nginx and Apache settings
Again, it should be noted that a CDN only has a function if (all) content is delivered directly AND, in addition, it should be noted that a CDN is only intended to reduce response times for customers abroad (i.e. not close to the datacenter in which you are hosting), by serving content from a datacenter nearby those customers abroad.
In general, internet is currently fast enough to deliver content across the whole world, certainly if that content only concerns a couple of MBs.
This is also the reason why most of the commercial CDN networks have been providing fail-over services, given the fact that the demand for a CDN will decrease in time and the existing infrastructure for a CDN allows for an easy fail-over of services.
In your case, you could investigate whether you really need a CDN and if you do, try to host a cheap Apache/Nginx server abroad, close to your customers.
I personally cannot imagine that you need a CDN, let alone the OVH CDN (not being a proper CDN).
As a personal and well-meant advice: try to make use of the cloud, host some VMs in various datacenters across the world and implement an automated load-balancer, that will assign traffic to the VM most nearby (this solution is so much easier: no or barely maitenance and/or configuration, low costs, very fast, reliable, no complex configs etc.)
Kind regards....
Facebook
Twitter
