shift8

So you’re telling me that if my site uses 2TB of bandwidth in a month with the free plan the CDN service will continue to provide the service, right?

For now , yes. We are anticipating a policy change that may include an increase in the free bandwidth limit among other changes. At this point we are prioritizing ensuring everyone is happy with the service first and foremost while filtering out potential abusers of the service obviously.

BUT I will receive notification if my website will use a lot of bandwidth

Yes indeed!

also I see the free plan has “2 URL limit” what it means ? 2 websites ? or 2 url from 1 website?

With the free plan , you may have up to two websites (two urls) to use with the CDN. The assumption being that the two URLs are separate sites obviously.

Hope this helps!

Hello,

Can you please fully clear your browser cache and try again? Also try another browser and please confirm if the issue persists.

Thanks!

Hello!

This is a great question and please understand that our service is only 1 year old and we are working out a process to work with all of our users (free and paid).

The idea is to perhaps keep an eye on your bandwidth and determine if it makes sense to upgrade. Right now an automated function to auto-disable sites that exceed bandwidth is not in place. We see no abuse of our services currently so there is no urgency to change this policy.

The motivation, for us, is to get a notification if someone generates 50TB of traffic on a 1TB free plan. Obviously that level of bandwidth usage is unacceptable for us , providing a free service especially.

In the future we may provide an option to not necessarily upgrade to a $5/month plan but purchase a bandwidth limit increase only for a much lower cost. Also we’re open to suggestions, if you have any ideas!

Thanks

Alternatively you could switch the “off” switch for the Shift8 CDN settings page and add the CDN url to the CDN section of W3 Total cache. Since at this point there are multiple plugins handling asset rewriting on your site, it might be more efficient if W3 Total cache handles the rewrites to our CDN for now. This is an alternative solution if my previous message produces no feasible results.

Hello!

Besides, when I registered a 2nd “Pull Zone” for the “Test-01” site, a new CDN URL was issued (https://rmtz4odwfzo1.wpcdn.shift8cdn.com), but this new CDN route was not added anywhere in any .htaccess files.
So, I don’t know if it’s OK, and if so, I don’t know how the assets of this secondary site can find its route???

The rules at first glance look right either way. The rewriting that happens in our plugin is in the code actually where it is detecting and rewriting all the urls that match the file types specified (media,js,css,etc).

Finally, amongst all the site’s pages, there are not much media files that succeeded to be served by the Shift8 CDN, but over time, one thing that I observed is that the only files that succeeded have one thing in common: they all had “brotli” as “content-encoding“. Never saw other “content-encoding” formats. Besides, “.css” and “.js” files had other “content-encoding” formats, namely “gzip”, etc.

When a url actually goes through our CDN, it should have brotli compression enabled by default. This is likely why you are seeing that header.

Just looping back to the originally reported problem, you mentioned that one image would go through the CDN but then the remainder are not? Can you give me an example page where this is happening as well as the file names that it is working and not working?

Sylvain,

First of all thank you for the kind words!

Second of all thank you for doing the legwork of ruling out the simplest root causes for this issue.

The plugin rewrites all applicable media files in the rendered HTML in this case to go through our CDN. The media files should be including :

'jpg|jpeg|png|gif|bmp|pdf|mp3|m4a|ogg|wav|mp4|m4v|mov|wmv|avi|mpg|ogv|3gp|3g2|webp|svg'

So whats happening is some media files are not being routed through our CDN? This could mean that another plugin is interrupting or circumventing the above file extension rewrite to change yourdomain.com/wp-content/uploads/file.jpg to go through the CDN url.

If I had to guess, maybe a plugin like “Rename media files” could be the culprit?

Alternateively what I would do is lets zero in on one media file thats not being rewritten to go through the CDN. Focus on that one media file thats not working (so long as its in the above list of media files).

Then disable each plugin one by one and see if it ever starts working. To prioritize things, if I had to guess, you could start with these plugins to disable (hopefully to save time) :

1. Autooptimize
2. Enable media replace
3. Media file renamer
4. Network media library
5. Rename media files
6. WP Optimize

If none of those resolve the problem, then run through the rest of the plugins one-by-one. I would be sure to clean the cache of a cache based plugin prior to disabling just in case the deactivation of those plugins doesnt auto clean cache.

You can hopefully appreciate how difficult it is to avoid these types of conflicts with WordPress plugin development in general. If we do isolate a plugin that is causing it , please let me know here. I can give it a shot to see if there is any custom workaround that can be implemented for this particular scenario. If you dont need the plugin or its not integral, even better! Just leave it deactivated 🙂

Again I dont mind helping with this diagnosis , if you run into trouble just pass some admin credentials to the test site to the email above.

Hopefully we get this resolved for you!

• This reply was modified 5 years, 10 months ago by Yui.
• This reply was modified 5 years, 10 months ago by Yui. Reason: dont ask for login credentials

Hello!

It looks like you added and deleted the site. Based on the screenshot you are using the API key and the CDN prefix from the first time you set up the account.

I will email you the proper settings to set in your wordpress dashboard, or you can login to shift8cdn.com directly and re-confirm the setting.

Thanks!

Hello!

I am sorry that you are having problems. I am able to load the test URL for your CDN installation here :

https://4wco9ui7fqyw.wpcdn.shift8cdn.com/wp-content/plugins/shift8-cdn/test/test.png

Can you give me a specific example of a URL that is generating a 400 bad request error?

Thanks!