• How to resolve - Invalid SSL certificate: Error code 526

  "Invalid SSL certificate" or "Error code 526" mean that FlyingCDN is unable to make a secure connection with your server. This usually happens when SSL certificate is not installed on your server or the installed one is self-signed (not singed by a certificate authority. Installing a free SSL certificate like Letsencrypt will resolve this issue. You can read more about it in the Cloudflare docs - Error 526: invalid SSL certificate (https://developers.cloudflare.com/support/troubleshooting/cloSome readers

• How to resolve - Error 1000: DNS points to prohibited IP

  When you point DNS records to FlyingCDN, Cloudflare conducts background checks on these records for verification purposes. During this verification period, the error message "Error 1000 - DNS points to prohibited IP" may appear. This issue is typically resolved automatically within a short timeframe, usually a few seconds. Other possible reasons: Pending invoices in your Cloudflare account - Login to your Cloudflare account -Account -Billing and clear any pending invoices. Then deleteFew readers

• Is FlyingPress compatible with my hosting

  FlyingPress is compatible with all hosting providers, regardless of the web server, server provider, or configurations. Additionally, FlyingPress offers automatic server-side/edge cache purging integrations with the following hosting providers, listed alphabetically: Cloudways (Varnish and Cloudflare) GridPane Kinsta Rocket.net RunCloud SiteGround SpinupWP WP EngineFew readers

• How to resolve 'Unable to Communicate via Rest API' error

  FlyingPress utilizes WordPress Rest API for operations like saving settings, purging, and preloading within its dashboard. If you encounter an error stating "Unable to communicate via Rest API," consider these potential causes: 1. Blocked Rest API by plugins or security layers Ensure no plugin, particularly those related to performance or security, blocks Rest API access. Verify Rest API functionality by visiting https://your-site.com/wp-json/. Disable anFew readers

• Why FlyingCDN doesn't always deliver images in WebP

  FlyingCDN may choose not to convert images to WebP for various reasons, often related to optimization efficiency, image characteristics, or technical limitations. The Cf-Polished response header provides insights into the image processing and optimization attempts by FlyingCDN. inputtoolarge: The input image exceeds the recommended size or complexity, requiring a reduFew readers

• Why is my cart count not updating

  FlyingPress serves cached pages to visitors even if items are added to the cart. For most of the WooCommerce sites, this is not an issue since most themes update the cart count using AJAX (updated in the background using JavaScript). If you're facing this issue, your theme might not support it. In that case, add woocommerceitemsincart to FlyingPress -Advanced Settings -Bypass cookies. So whenever an item is in the cart, we'll stop serving cached pages to those visitors.Few readers

• Why am I still getting Browser cache TTL warnings

  FlyingPress automatically adds browser cache TTL to all static files, allowing them to be cached in the browser for a long time. You'll see this in Google PageSpeed Insights as "Serve static assets with an efficient cache policy." However, we can only add these browser cache TTL headers if your web server is Apache, LiteSpeed, or OpenLiteSpeed. If your web server is Nginx, you'll have to contact your hosting provider or manually edit the config file.Few readers

• Why is my cached pages count increasing and not stopping

  When you click "Preload cache" or save settings, FlyingPress generates cache for all the pages on your site. However, you might have noticed that the cached pages count keeps increasing, and it's significantly higher than the number of pages/posts on your site. The reason is, for the same URL/page, FlyingPress may generate serveral cached pages. This includes Cache for logged in users (along with each role) Cache for pages with query strings (?abc=xyz) Cache for mobile devices In short,Few readers

• Are there any coupons or discount codes?

  Many customers reach out to us looking for a discount or promo code for the FlyingPress plugin. We don't provide any coupon codes or discounts, including during Black Friday or Cyber Monday. If you encounter offers on third-party voucher websites, please note that they're not genuine because FlyingPress is only sold at full price. Here are our best tips on how you can maximize value with FlyingPress: Risk-free trial for 14 days: FlyingPress includes a 14-day money-back guarantee with noFew readers

• How to force trailing slash in URLs

  Force trailing slash in URLs Apache: Nginx:Few readers

• Why is my disk usage so high

  Once FlyingPress begins caching pages, it generates static HTML files for each of your pages within the /wp-content/flying-press/ folder. The actual size of this folder may vary depending on factors such as the size of your site, the number of pages, and the optimizations you have enabled. On average, a cached HTML file tends to be around 200KB in size. Therefore, to provide a better perspective: 100 cached pages will occupy approximately 20MB of storage. 1,000 cached pages will consumFew readers

• How to force HTTPS in URLs

  Most web servers already force HTTP to HTTPS redirection automatically if you've installed SSL certificate. However, if your web server is not forcing HTTPS, add the following code to .htaccess file:Few readers

• Why some JavaScript files are not minified

  In some instances, certain JavaScript files may not be minified even when JavaScript minify is enabled in FlyingPress. This is generally due to one of the following reasons: The file size reduction post-minification is less than 2KB. The file size reduction post-minification is less than 10% of the original size. The file is already minified, as indicated by a .min.js suffix. These criteria are based on the official recommendations by Google Lighthouse or PageSpeed (https://pagespeed.weFew readers

• How to check WebP delivery on FlyingCDN

  FlyingCDN dynamically converts images to the WebP format on-the-fly, utilizing the CDN. Importantly, the original file extensions of your images, such as .jpeg, .png, or .gif, remain unchanged even after conversion. To verify if an image is being served in WebP format, you can use the browser's network tab. Here's how: Open the network tab in your browser's developer tools. This is typically accessible by right-clicking on the webpage and selecting "Inspect" or "Inspect Element", then navigFew readers

• Why is FlyingCDN stuck at 'Pending validation'

  Once you've added a new site in FlyingCDN, we continuously monitor your DNS records and check for the "acme-challenge" CNAME record. Its value should be your-domain.com.ffb7310192aab5b6.dcv.cloudflare.com. Until this record is added, the status will remain 'Pending validation'. If you've added the record correctly, 'Pending validation' will change to 'Active' within a minute. If you're stuck at 'Pending validation', here are some common issues we've encountered: Disable proxy for thFew readers

• Why am I getting mixed content or non-https errors

  Mixed content issues arise when a secure HTTPS request loads a web page with both HTTPS and HTTP content. For instance, if your HTTPS site at https://example.com/ requests a file from a non-HTTPS URL like http://example.com/style.css. This error often occurs when your database contains HTTP URLs instead of HTTPS. To fix this: Install Better Search Replace plugin Search for "http://your-site.com" and replace with "https://your-siteFew readers

• How SSL renewals work with FlyingCDN

  Two types of SSL renewals There are two main types of SSL renewal processes: DNS-01 challenge and HTTP-01 challenge. DNS-01 challenge The DNS-01 challenge proves your ownership of a domain by creating a specific DNS TXT record, often named "acme-challenge". HTTP-01 challenge The HTTP-01 challenge involves placing a specific file on your web server that can be accessed via HTTP. The URL will look like: http://yourdomain.com/.well-known/acme-challenge/<token> Let's EncrFew readers

• How to purge FlyingCDN cache?

  If you’ve set up the FlyingCDN API key in FlyingPress, purging the cache in FlyingPress will automatically clear the corresponding cache in FlyingCDN. Purging pages in FlyingPress only clears those pages from the FlyingCDN cache. Purging everything clears the entire cache in FlyingCDN. Make sure you’ve entered the correct API key from cockpit.flyingcdn.com. Note that deleting and re-adding the same site will generate a new API key, which you'll need to updaFew readers