Frans Allen

Hi Alfred,

The error is Unsafe attempt to load URL <URL> from frame with URL <URL>. Domains, protocols and ports must match., this should be seen in your browser console (Ctrl+Shift+I or F12).

This one can be solved by adding /gutenbooster/assets/img/feather-sprite.svg to the Exclude list. Based on your theme, that file must be loaded with the same domain as the origin. Please contact the theme author for theme related issues (can start with text that you cannot use CDN on the icon).

Let me know if this helps.

Best,
Frans

Hi @alfredg,

Thanks for reaching out!

So that I can identify this problem, can you provide me with error messages from the browser console when Statically active?

Best,
Frans

Hi @ranaharoon322,

Thanks for the rating, very glad you liked it!

Statically Free is sponsored by these excellent services to support the idea of fast and better static files. You can learn it here.

We will keep it up-to-date. The upcoming v0.5 has many improvements and is ready to test, you can download it from our GitHub repo.

Best,
Frans

Hi Tithia,

Unfortunately, there is no support for origin pull via HTTP at this time. But if the problem is some assets don’t work on HTTPS, I suggest making an exclusion.

Let me know if you need further assistance.

Best,
Frans

Hi Tithia,

Statically fetch to the origin with an HTTPS connection, you must have this in your origin for the CDN to work.

Best,
Frans

Hi Tithia,

Would you provide me with the link? I’ll be more than happy to check.

Best,
Frans

Hi there,

I assume that you entered the CDN URL with https://cdn.statically.io/sites/:domain? Note that :domain is an URL format, you need to change it to your website’s domain i.e example.com, so the CDN URL will look like this https://cdn.statically.io/sites/example.com.

When the plugin is first activated, usually the CDN URL is generated automatically, you can choose not to change this. But I believe the tips above should make it work now, but let me know if you need further assistance.

Best,
Frans

Hi @abidsoomro,

I have checked your page. The image does not appear because the image cannot be loaded from the origin or a 404 page, please ensure that the image exists.

Best,
Frans

Hi @abidsoomro,

Thanks for reaching out.

That can happen because of an image multi-level compression. Since Statically runs its own compression, it is not needed to compress the master image, because it can hold us optimally optimizing images. However, CDN will only deliver a compressed version of an image to end-users.

But, if compression at the origin level is required, this should still work (not recommended), keeping in mind that the image must not be corrupted.

For best practice: if the CDN returns with an error message, try to check the image at the origin. If we see this image https://gagbee.com/wp-content/uploads/2019/12/Joker.png, it looks like there is damage to the file, and our compression is unable to process. My suggestion is to make sure images are complete/non-corrupt files and not a 404 page, then CDN should work well here.

Let me know if this helps.

Best,
Frans

Hi @pxnjl,

Glad to hear that. So this is not an issue related to Statically.

I will mark this as resolved. Feel free to re-open if you find anything related.

Thanks,
Frans

Hi there @pxnjl,

Thanks for reaching out.

Would you mind sending me a screenshot, errors, any details, so I can dig into the problem?

Best,
Frans

• This reply was modified 4 years, 11 months ago by Frans Allen.

Hi @lydenyardley

Thanks for contacting us.

Currently, the plugin does nothing but rewrite local URLs to the CDN, however I will look into this and try to provide it if really necessary.

Some cache plugins may provide this functionality, you can use it for a solution.

Let me know if you have other questions about this.

Best,
Frans

Hi @lydenyardley,

Thanks for contacting us.

It seems that the javascript file from the SVG Support plugin is rewritten on the wrong CDN path, that’s why this happens.

Try entering svgs-inline-min.js in the exclusion list for a temporary solution.

However, I will publish a patch to fix this overall. You might want to try the development version of the plugin on GitHub, this version should solve the issue.

Best,
Frans

Hi @abidsoomro,

Thanks for contacting us.

Can you provide more info about this issue?
What do you mean by “not showing images”, does the CDN provide an error page or the image is swept in HTML?

I suggest updating the plugin, it might help to resolve this issue.

Best,
Frans

Hi @master412160,

Thank you for contacting us.

It is still possible for some assets not to be rewritten into the CDN URL due to plugin conflicts, but should work for most and list in the Included dirs.

What I suggest is try to add files/folders that are not on the CDN into Included Directories option.

If you use a cache plugin that also rewrites the asset URL, try to deactivate it temporarily to see whether the asset is rewritten into the CDN URL.

Let me know if this helps.

Best,
Frans