When enabling the WordPress plugin on our sites, I'm seeing the error below, accompanied with errors for all other files that are being served through the CDN.

When following the link, the file seems to be unavailable on the CDN. A few days ago the service was working fine. Did something change?

The resource from “https://cdn.statically.io/sites/noesteijver.nl/wp-includes/js/admin-bar.min.js?ver=5.3.2” was blocked due to MIME type (“text/html”) mismatch (X-Content-Type-Options: nosniff).

When I enter https://gitlab.com/scribus/scribus/-/jobs/227157068/artifacts/raw/Scribus-2f0ab15-x86_64.AppImage into the form on https://staticaly.com/ it does not give me a URL back.

Being able to use a CDN for GitLab CI artifacts would be especially useful, especially in case this would support HTTP Range Requests.

Some GitHub projects has their packages at the releases page, both binary and source tarballs can be allowed to appear (for example). If you add CDN services for GitHub Releases these packages would allowed to make use of your CDN service, and be more friendly to multi-threads download managers.

The original Github Gist link:

https://gist.githubusercontent.com/LeptoFlare/cd471d7b29902b5d36eb48e64e62d8d1/raw/style.css

The statically.io link:

https://cdn.statically.io/gist/LeptoFlare/cd471d7b29902b5d36eb48e64e62d8d1/raw/style.css

Adding image resizing feature information on this page. We can only found it in here

Example image: https://cdn.statically.io/img/solar-assistance.be/wp-content/uploads/2020/06/bg-hp-2195x1233-c-default.jpg?quality=70&f=auto&quality=70&f=auto

Response headers:

accept-ranges: bytes
access-control-allow-origin: *
access-control-expose-headers: *
age: 991
alt-svc: h3-27=":443"; ma=86400, h3-28=":443"; ma=86400, h3-29=":443"; ma=86400
cache-control: public, max-age=31536000, immutable
cf-bgj: imgq:100,h2pri,csam-hash
cf-cache-status: HIT
cf-polished: status=not_needed
cf-ray: 5d017aece9cefa18-AMS
cf-request-id: 0514cb280e0000fa18943dc200000001
content-length: 187430
content-type: image/jpeg
date: Wed, 09 Sep 2020 14:08:14 GMT
etag: "stlystlycf4oUxeVtyMMPPe1UcRTsMRg:3776d-5ac35b9c148b5"
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
link: https://solar-assistance.be/wp-content/uploads/2020/06/bg-hp-2195x1233-c-default.jpg; rel="canonical"
server: cloudflare
status: 200
strict-transport-security: max-age=31536000; includeSubDomains; preload
timing-allow-origin: *
vary: Accept, Accept-Encoding
x-cache: HIT
x-content-type-options: nosniff
x-served-by: cache-ams21064-AMS

Is this a temporary outage? I've been told Cloudflare in some cases decides to not serve webp images but all of them?

Thanks in advance.

Hello,
Can you fix this?

Depending on what's above the fold, a delay may be required for a screenshot to be valuable. Adding a delay query parameter for the number of milli/seconds to wait before taking the screenshot would accomplish this.

The CDN77 link in the privacy policy is outdated: https://www.cdn77.com/privacy

The new correct link is probably: https://www.cdn77.com/privacy-policy

Where:
https://statically.io/

What:
Need "p":

Unlimited otimization

URLs such as:

https://cdn.statically.io/gh/sesh/brntn-css-2/master/brntn2.css

Are resulting in a 451 and a message to talk to the owner.

When using statically.io for .gif images, they lose their animation data.

See:
https://cdn.statically.io/img/noesteijver.nl/f=auto,q=90/wp-content/uploads/2018/07/NoesteIJver-webanimaties-Content.gif

https://noesteijver.nl/wp-content/uploads/2018/07/NoesteIJver-webanimaties-Content.gif

404 error: https://cdn.statically.io/img/s.put.re/n5bfj8Qi.png?w=2000&quality=100

However removing query strings, it works fine: https://cdn.statically.io/img/s.put.re/n5bfj8Qi.png

Saya menggunakan Staticaly untuk gambar Blogger. Masalahnya hanya di firefox saja yang tidak support webp, jadi harus pakai picture dengan fallback. Jika bisa otomatis memilih sumber yang support firefox (berarti format sumber asli gambar), itu akan lebih baik, jadi tidak perlu repot menggunakan elemen picture dengan fallback.

502 Bad Gateway

https://cdn.staticaly.com/favicons/tokopedia.com
https://cdn.staticaly.com/favicons/lazada.co.id
https://cdn.staticaly.com/favicons/elevenia.co.id

I haven't added ?quality to the URL, but still, images seem to be compressed and lose quality.

Original: https://wpspeedmatters.com/wp-content/uploads/2019/08/flying-birds-1160x680.jpg
Statically: https://cdn.statically.io/img/wpspeedmatters.com/wp-content/uploads/2019/08/flying-birds-1160x680.jpg

Few days ago images from my site does not open

https://cdn.statically.io/img/img03.platesmania.com/171117/s/10676797.jpg

I gettin error 400.

Images from platesmania.com is worked, but not from subdomain...

Hello,
I get random 403 errors on some images taken from IMDB.
An image that appears.
https://cdn.statically.io/img/m.media-amazon.com/images/M/MV5BMzZiM2FhOTUtZTE4My00ZDNlLWEyZWItZDBiNDFjZDk2MWE1XkEyXkFqcGdeQXVyMTQxNzMzNDI@._V1_SX120.jpg

Images that do not appear.
https://cdn.statically.io/img/m.media-amazon.com/images/M/MV5BMjMyMTc5NTQzOV5BMl5BanBnXkFtZTgwMzk2MjgwMDE@._V1_SX120.jpg

The question is whether statically supports remote image or not?
A few days ago these errors did not exist.

Thanks.

Hello,
I'm getting 404 error from statically.
Exp: https://cdn.statically.io/favicons/statically.io
It show 404 Site favicons.marsble.com is not served on this interface

Thanks.

https://cdn.staticaly.com/img/random currently redirects to an image from unsplash.com rather than loading that image through cdn.staticaly.com

I have some images that were working fine, but recently they stopped working from the CDN. Here's an example:

CDN: https://cdn.statically.io/img/stegosource.com/wp-content/uploads/a11y-blog-cover.svg

Site: https://stegosource.com/wp-content/uploads/a11y-blog-cover.svg

Sample image: https://cdn.statically.io/img/wpspeedmatters.com/wp-content/uploads/2019/12/chat-bubbles-1160x680.jpg

The image is not delivered as WebP even if the browser supports it.

Here is more info:

Currently Statically can work with one-level GitLab repositories only, but GitLab allows project to be organized into groups hierarchies (with up to 20 levels):

https://gitlab.com/:user/:group/:subgroup/:subsubgroup/../:project

It would be great if Statically could support group hierarchies for GitLab repositories.

Hi @fransallen, it seems that new cached images are ignoring the Query Strings, so the image resolution isn't resized with ?fit=<w>,<h>, and ?resize=<w>,<h> query strings, even if I use w and h query strings in my URL.

Example:

• https://cdn.statically.io/gl/FarrelF/blog-images/89b76e04/cara-install-lamp-stack-di-ubuntu/Logging_in_phpMyAdmin.png?fit=720,374&quality=80
• https://cdn.statically.io/gl/FarrelF/blog-images/89b76e04/cara-install-lamp-stack-di-ubuntu/Error_TempDir_phpMyAdmin.png?fit=720,374&quality=80

If you already fixed that, can you purge these cache for https://cdn.statically.io/gl/FarrelF/blog-images/89b76e04/cara-install-lamp-stack-di-ubuntu/ or all entire cached images, because maybe this issue will affect another image that loaded using Statically?

@tovic @ardyfeb do you have an idea about [stats pages]? What data will we show? Can you help build the UI? I will provide an API from Marsble API Server if necessary.

Once i switched to CDN, my Content-Security-Policy is complaining about Google Fonts CSS trying to be loaded.

Confirmed trough the browser console while trying to display a single image:

Are these two other resources needed to be loaded also?

Will .svg be supported soon?

hello,
Image transformation doesn't work if I use Force webp.
Image URL: https://i.imgur.com/xjaMIKB.png
image URL with statically and width setting: https://cdn.statically.io/img/i.imgur.com/xjaMIKB.png?w=200
image URL with statically, width and force webp setting: https://cdn.statically.io/img/i.imgur.com/xjaMIKB.png?w=200&format=webp

This problem I got for more than a week. I thought it was a temporary error.

Thanks.

when i am trying to get my images from Statically CDN
most of the images are fine
except for images with hebrew letters in the filename
like - %D7%94%D7%95%D7%A8%D7%93%D7%94-5.svg
those come out with error 400

Thanks,
Shay

I've downloaded some fonts locally to my server and included them like this in a CSS file (fonts.css):

/* roboto-900italic - latin */
 @font-face {
   font-family: 'Roboto';
   font-style: italic;
   font-weight: 900;
   font-display: swap;
   src: url('../assets/fonts/roboto-v20-latin-900italic.eot'); /* IE9 Compat Modes */
   src: local('Roboto Black Italic'), local('Roboto-BlackItalic'),
        url('../assets/fonts/roboto-v20-latin-900italic.eot?#iefix') format('embedded-opentype'), /* IE6-IE8 */
        url('../assets/fonts/roboto-v20-latin-900italic.woff2') format('woff2'), /* Super Modern Browsers */
        url('../assets/fonts/roboto-v20-latin-900italic.woff') format('woff'), /* Modern Browsers */
        url('../assets/fonts/roboto-v20-latin-900italic.ttf') format('truetype'), /* Safari, Android, iOS */
        url('../assets/fonts/roboto-v20-latin-900italic.svg#Roboto') format('svg'); /* Legacy iOS */
 }

With the Statically.io WordPress plugin disabled, the fonts.css file and the font files are being loaded over HTTPS. With the plugin enabled, the fonts are suddenly being loaded over HTTP and therefore omitted by the browser. I'm not sure why this is happening, the CSS file is loaded but it's only happening with Statically enabled.

Debug data:

PHP version: 7.3.16
WordPress version: 5.4.1
url: https://cdn.statically.io/sites/schenkeveldadvocaten.nl
dirs: wp-content,wp-includes
excludes: .php
qs_excludes: no-statically
quality: 90
width: 0
height: 0
smartresize: 0
webp: 1
external_images: 
emoji: 1
favicon: 0
favicon_shape: rounded
favicon_bg: #000000
favicon_color: #ffffff
og: 0
og_theme: light
og_fontsize: medium
og_type: jpeg
wpadmin: 0
relative: 1
https: 1
query_strings: 0
wpcdn: 1
private: 0
Active Plugins: the-events-calendar/the-events-calendar.php,antispam-bee/antispam_bee.php,autocomplete-for-relevanssi/autocomplete-for-relevanssi.php,cf7-conditional-fields/contact-form-7-conditional-fields.php,cf7-post-fields/cf7-post-fields.php,classic-editor/classic-editor.php,contact-form-7-dynamic-text-extension/contact-form-7-dynamic-text-extension.php,contact-form-7-honeypot/honeypot.php,contact-form-7/wp-contact-form-7.php,cookie-notice/cookie-notice.php,cpt-onomies/cpt-onomies.php,duplicator-pro/duplicator-pro.php,flamingo/flamingo.php,github-updater/github-updater.php,google-analytics-for-wordpress/googleanalytics.php,relevanssi/relevanssi.php,simple-page-ordering/simple-page-ordering.php,statically/statically.php,unyson/unyson.php,wordpress-seo/wp-seo.php,wp-defender/wp-defender.php,wp-hummingbird/wp-hummingbird.php,wp-last-modified-info/wp-last-modified-info.php,wp-smush-pro/wp-smush.php,wpmudev-updates/update-notifications.php,yet-another-related-posts-plugin/yarpp.php,

Hey,

When one of my PNG images is loaded via Statically it gets weird blurring on it.

https://cdn.statically.io/img/www.samunderwood.co.uk/wp-content/uploads/deep-links.png
https://www.samunderwood.co.uk/wp-content/uploads/deep-links.png

You can see the blurred parts around the orange numbers on the third row.

This issue reported by Gregory Hammond via email.

The problem is when you get content from Bitbucket, Staticaly gives you a message You need to sign in or sign up before continuing.

Our team has checked this problem and fixed it, now the service is working normally.

On one of the devices images don't load and we have this error:

first byte timeout

Guru Mediation:
Details: cache-hhn4023-HHN 1568194703 226087308

Varnish cache server

Original file: https://res.cloudinary.com/curben/20190812/containers-webp.webp

I tried:

• https://cdn.statically.io/img/res.cloudinary.com/curben/20190812/containers-webp.webp
• https://cdn.statically.io/img/res.cloudinary.com/curben/20190812/containers-webp.webp?auto_format=false

Both links gave "HTTP 400 Bad Request".

Add @tovic and @ardyfeb as official project maintainers.

Details can be seen in the README file: https://github.com/marsble/staticaly/blob/master/README.md

Cheers 🥂

I'm trying to put a quick note onto my site that lets my teachers know it's not a games site so they don't block it before I can set up all of my web pages, the problem is that it won't update on Staticaly, even after clearing my cache, cookies, and browsing history.

Original image (already compressed): https://wpspeedmatters.com/wp-content/uploads/2019/08/flying-birds-1160x680.jpg (18.0KB)

Same file delivered from Statically without ?quality: https://cdn.statically.io/img/wpspeedmatters.com/wp-content/uploads/2019/08/flying-birds-1160x680.jpg (22.7KB)

With ?quality=100: https://cdn.statically.io/img/wpspeedmatters.com/wp-content/uploads/2019/08/flying-birds-1160x680.jpg?quality=100 (217KB)

With ?quality=90: https://cdn.statically.io/img/wpspeedmatters.com/wp-content/uploads/2019/08/flying-birds-1160x680.jpg?quality=90 (14.1KB)

I believe that JPG compression is set too high and we loose too much quality.
Is there any way to optimize this? Not all JPGs are affected, but some are unusable once in the CDN...

See https://cdn.statically.io/img/www.ekinops.com/images/banners/banner_web_product.jpg

No problems with PNG.

Hello
I recently have installed Statically plugin to my website and I enable cdn and https but when I visit my website I saw everything without styling when I try to visit cdn link I got an 404 error file not found

https://cdn.statically.io/hp/wp-content/themes/hrproperties/assets/css/all.css 404 error
all files give same error

Thank you

removed

Hi,

The page to request a purge is unavailable: https://statically.io/purge

When will it be available again?

Thanks.

This is regarding static files (JS and CSS)

Cache will not update, has been over 24 hours, adding ?env=dev query parameter does not bypass the cache.

How can I force statically to update the chached files?

This will be used as a roadmap, feature requests, and resources for Statically.

Help us make a nice service for fast & better static files!

Do you need a new feature on Statically? Let us know here!

Roadmap

• Support GitHub via our raw CDN
• Support GitLab via our raw CDN
• Support Bitbucket via our raw CDN
• Imgpx, image CDN via custom endpoints
• Use Cloudflare, CDN77, BunnyCDN, & Fastly as main CDNs
• Support WordPress SVN via our raw CDN
• Screenshot, capture web-pages from URL and then turn it into a PNG or JPG image
• Favicons, get favicon from a domain
• Libs, CDN for any web frameworks
• Flags, CDN for country flags
• Images from git repos via our Imgpx's image processing to support resizing, optimization, & enhance security from non-image files
• WordPress Plugins
• Open Graph Image as a Service
• Support ?env=dev to our raw CDN for 5 minutes Cache-Control
• Simple statistics page in main website, expect more detailed stats soon
• Use dedicated origin for Imgpx with dedicated IP subnet
• Use our own internal DNS to monitor queries and avoid abuse on the custom endpoint side
• New website, see https://github.com/marsble/statically-web
• Use NS1 as primary DNS

Accepted feature requests

• Support IPv6 for all resources
• Imgpx: enable auto_format=false to force original mime types delivery (by @curbengh)
• Imgpx: user agent detection for webp delivery (by @curbengh)
• Imgpx: more image transformations (by @curbengh)
• npm CDN (by @curbengh)
• Imgpx: enable format=webp to force webp format delivery
• Imgpx: automatically convert gif to (animated) webp

Technologies

• Cloudflare as main CDN
• CDN77 as main CDN
• BunnyCDN as main CDN
• Fastly as main CDN
• NS1 as primary DNS
• Uptime Robot as monitoring platform
• Netlify as main website hosting & CDN
• RunCloud to manage and deploy APIs & internal apps

Resources

The following are some good sources for knowing more about Statically:

• 8 Awesome Features Of Statically Free CDN by RunCloud
• New features of Statically: Libs and Flag Icons CDN by Frans Allen
• Feel free to add yours!

I would like to suggest a feature request for the screenshot feature. It works well but not for those pages which has CSS animations on the content/section. That ends up with incorrect screenshots. How about adding a delay timer parameter to take the screenshot? Or wait for the page to load fully before taking a screenshot?

Originally posted by @munirkamal in #30 (comment)

Halo, mas, ini sepertinya ada masalah Cache Control untuk branch gh-pages dan v4-dev. Karena ada beberapa repo yang menggunakan branch gh-pages dan menggunakan branch v4-dev untuk memperbarui Repo, selain branch master. Repo yang menggunakan branch gh-pages ini biasanya orang yang menggunakan layanan GitHub Pages.

Kali ini, contoh repo yang menggunakan branch gh-pages adalah Twitter Twemoji, sedangkan repo yang menggunakan Branch v4-dev adalah Bootstrap

Berikut di bawah ini merupakan Contoh File dari masing-masing repo dengan Branch yang berbeda:

Contoh File Emoji di dalam repo Twitter Twemoji (Branch: gh-pages) :

• Menyeringai : https://cdn.staticaly.com/gh/twitter/twemoji/gh-pages/2/svg/1f603.svg
• Senyum : https://cdn.staticaly.com/gh/twitter/twemoji/gh-pages/2/svg/1f642.svg
• Tertawa : https://cdn.staticaly.com/gh/twitter/twemoji/gh-pages/2/svg/1f604.svg

Contoh File di dalam Repo Bootstrap (Branch: v4-dev) :

• https://cdn.staticaly.com/gh/twbs/bootstrap/v4-dev/dist/css/bootstrap.css
• https://cdn.staticaly.com/gh/twbs/bootstrap/v4-dev/dist/css/bootstrap.min.css

Masalahnya adalah Durasi Cache-Control nya yang terlalu panjang, yakni sekitar 1 Tahun, sama seperti Branch, Commit atau Tag lain, sedangkan di dalam branch tersebut sering sekali menjadi tempat untuk pembaruan Repo, seperti branch master pada umumnya.

Saya pikir, alangkah baiknya, mungkin mas bisa 'perlakukan' kedua branch tersebut sama seperti branch master? Karena khawatirnya akan mengalami masalah seperti file nya yang tidak reflek terhadap perubahan, tampilan menjadi ancur-ancuran, dll. Setidaknya, ini akan meminimalisir masalah tersebut.

Terima kasih ^_^

Hi,

I made some changes in a .css file, updated a query-var with the version of the file from 1.0.0 to 1.0.1. However, Statically doesn't seem to pick this up and still serves the old .css file.

I'd think that a query var with the new version of the file would do the trick, but this doesn't seem to work. How can we force Statically to cache the new file?

From what I can tell when the width parameter is used the images aren't cached or aren't cached for very long.

I've noticed a large delay when visiting my site for the images to load in which is fine for the first load so Statically and cache the images. But then they don't seem to be cached on the Statically CDN for long (next day I get the same long delay).

From some testing, it seems to primarily happen for any image using the width parameter so it may be that.

Currently https://staticaly.com/ is still serving requests, but it isn’t being updated. Please redirect to new site https://statically.io/.