Frequently Asked Questions

Q: What is a CDN and why do I need it?

A: A CDN (Content Delivery Network) is a network of servers distributed globally that serve your website's static files (images, CSS, JS, videos) from locations closer to your visitors. This reduces latency and speeds up page load times.

Benefits:

• Faster page load times
• Reduced server load
• Better user experience
• Improved SEO rankings
• Handle traffic spikes better

Q: Do I need to use all 5 CDN types?

A: No! You can use just one CDN for everything (Frontend URL), or configure separate CDNs for different file types. The flexibility is there if you need it.

Common setups:

• Simple: Just enable Frontend URL (one CDN for everything)
• Recommended: Image CDN + Static CDN (separate domains for images and CSS/JS)
• Advanced: All 5 CDN types with different domains

Q: Will this work with any CDN provider?

A: Yes! The plugin works with any CDN that can pull content from your origin server, including:

• Cloudflare (with optional direct integration)
• Amazon CloudFront
• StackPath
• KeyCDN
• BunnyCDN
• Custom CDN solutions
• Even just subdomains pointing to your server

Q: Do I need to upload files to the CDN?

A: No! The plugin uses "pull" method - your CDN automatically fetches files from your origin server when requested. No manual file uploads needed.

Q: Is this free?

A: Yes, the plugin is completely free. However, you may need to pay for CDN services from providers like Cloudflare, Amazon, etc. Many CDN providers offer free tiers.

Q: Can I just use subdomains instead of a real CDN?

A: Yes! Many users create subdomains like cdn.example.com or img.example.com that point to the same server. This still provides benefits like:

• Parallel downloads (browsers can download more files simultaneously)
• Cookie-less domains (faster)
• Organization and future migration to real CDN is easier

Q: What's the difference between http:// and https:// in CDN URLs?

A: Always use https:// if your site is on HTTPS. Mixing HTTP and HTTPS causes "mixed content" warnings and browsers may block resources.

Q: Should I include trailing slashes in CDN URLs?

A: No. Always enter CDN URLs without trailing slashes:

• ✅ Correct: https://cdn.example.com
• ❌ Wrong: https://cdn.example.com/

Q: Do I need to migrate database content?

A: No! The plugin replaces URLs dynamically on-the-fly. Database migration is optional and only needed for specific use cases. Most users don't need it.

Q: What if I change CDN providers?

A: Just update the CDN URLs in plugin settings. If you didn't do database migration, it's instant. If you did migrate, you'll need to migrate again with new URLs.

Q: What is versioning and do I need it?

A: Versioning adds a parameter like ?1cdnver=1.5 to CDN URLs. This forces browsers and CDNs to fetch fresh copies when you update files.

Use it when:

• You update CSS/JS files and want users to see changes immediately
• You replace images with updated versions
• You're launching a site redesign

Q: How do I force browsers to refresh cached files?

A: Change the version string in Advanced settings. For example, change from 1.0 to 1.1. This creates new URLs that bypass cache.

Q: Why do I see ?_=1 instead of ?1cdnver=X.X on my URLs?

A: This means versioning is not enabled for that asset type. Go to Settings → Advanced tab and enable versioning for the specific CDN type (Images, Media, Fonts, CSS, or JS).

Q: Can I use different version numbers for different asset types?

A: Yes! Each CDN type (Image, Media, Fonts, CSS, JS) can have its own version string. This gives you granular control over cache busting.

Q: Images/videos are not loading from CDN

A: Check these in order:

1. Is the CDN type enabled? (Settings → CDN Settings)
2. Is the CDN URL correct? (No trailing slash, proper protocol)
3. Clear all caches (WordPress, CDN, browser)
4. Run Tools → CDN Connection Test
5. Check browser console for errors (F12)

Q: Getting CORS errors for fonts

A: Fonts require CORS headers. Add these to your CDN configuration:

Access-Control-Allow-Origin: * Access-Control-Allow-Methods: GET, HEAD

For Cloudflare, this is automatic. For other CDNs, check their documentation.

Q: Videos are going to Image CDN instead of Media CDN

A: This was a bug in earlier versions. Update to v2.3.1+ which fixes media routing priority. If Media CDN is not configured, videos will use Frontend URL (which might be set to your Image CDN domain).

Q: Some files load from CDN, others don't

A: Possible causes:

• Hardcoded URLs in theme/plugins
• Aggressive caching plugin interfering
• Page builder storing old URLs
• Solution: Clear all caches, regenerate page builder content

Q: CDN works on some pages but not others

A: Likely a caching issue. Clear:

1. WordPress page cache
2. Plugin cache (Tools → Clear Cache)
3. CDN cache (Cloudflare purge)
4. Browser cache (Ctrl+Shift+R)

Q: Will this make my site faster?

A: Yes, typically 20-50% faster page loads, especially for:

• Visitors far from your server
• Image-heavy sites
• Sites with lots of CSS/JS files

Q: Should I use 5 different CDN domains?

A: Not necessarily. More domains = more DNS lookups. For most sites, 1-2 CDN domains is optimal:

• Best: 1 domain for everything
• Good: 2 domains (images + static assets)
• Overkill: 5 separate domains (only for huge sites)

Q: Does this work with WP Rocket / W3 Total Cache?

A: Yes, but configure caching plugins to exclude CDN domains from optimization to avoid conflicts.

Q: Can I use this with WooCommerce?

A: Yes! Works perfectly with WooCommerce. Product images, galleries, and downloadable files can all be served via CDN.

Q: What's the difference between using Cloudflare directly vs this plugin?

A: Cloudflare proxy automatically CDNs all content. This plugin adds:

• Ability to use separate subdomains for different asset types
• Cache purging from WordPress admin
• Developer mode toggle
• Versioning/cache busting control

Q: Do I need the Cloudflare integration feature?

A: No, it's optional. The main CDN features work without it. The integration just adds convenience features like cache purging from WordPress admin.

Q: Can I use this with Cloudflare APO (Automatic Platform Optimization)?

A: Yes, they work together. APO caches HTML pages, while this plugin optimizes asset delivery.

Q: What WordPress version is required?

A: WordPress 5.0 or higher. Tested up to WordPress 6.8.

Q: What PHP version is required?

A: PHP 7.4 or higher. PHP 8.0+ recommended.

Q: Does this work with multisite?

A: Yes! Each site in the network can have its own CDN configuration.

Q: Compatible with page builders?

A: Yes, works with:

• Elementor
• Divi
• Beaver Builder
• WPBakery
• Gutenberg

Q: Works with multilingual plugins?

A: Yes, compatible with WPML, Polylang, TranslatePress, and Weglot.

Q: Can I exclude specific pages/posts from CDN?

A: Currently not built-in, but you can add custom code to check page ID and skip replacement. Contact support for code snippet.

Q: Can I use different CDN for mobile vs desktop?

A: Not built-in, but possible with custom code. Use wp_is_mobile() to conditionally change CDN URLs.

Q: Does this modify my original files?

A: No! Files stay on your server unchanged. The plugin only changes URLs in HTML output (unless you run database migration).

Q: Can I use this with a reverse proxy?

A: Yes, works with Nginx reverse proxy, Varnish, and other caching layers.

Q: Is there a programmatic API?

A: Yes, the plugin provides WordPress filters and actions for custom integrations. Contact support for developer documentation.

Q: What is Pro Solution?

A: Pro Solution is a menu in 1 CDN Manager (v2.3.1+) that provides information about Utility Server's three AI-powered modules: SPIDER, MARLIN, and RHINO. These are premium modules that work alongside 1 CDN Manager for enterprise-grade performance optimization.

Q: What's the difference between SPIDER, MARLIN, and RHINO?

A:

• SPIDER: AI-powered prerenderer for JavaScript-heavy sites. Makes your site SEO-friendly by serving fully-rendered HTML to search engines.
• MARLIN: Intelligent image optimizer that reduces CDN costs by up to 40% with AI-powered compression and modern format conversion (WebP, AVIF).
• RHINO: Edge accelerator that caches fully-rendered HTML at the edge for ultra-fast page loads and reduced server load.

Learn more: Pro Solution Documentation

Q: Are these modules free?

A: No, SPIDER, MARLIN, and RHINO are premium modules that require a subscription from DNS Stack (India) or Techtonic Systems (US). The Pro Solution page in 1 CDN Manager is free and provides information to help you decide if these modules are right for your needs.

Q: Can I use these modules with 1 CDN Manager?

A: Yes! These modules are designed to complement 1 CDN Manager. They work alongside your existing CDN setup to provide additional optimization. Contact DNS Stack or Techtonic Systems for integration details.

Q: Which provider should I choose - DNS Stack or Techtonic Systems?

A: Both providers offer identical modules with the same features and performance. Choose based on:

• DNS Stack: Ideal for businesses in India, regional support, local payment options
• Techtonic Systems: Perfect for US-based businesses, AWS Marketplace integration, American infrastructure

Q: How do I get support?

A: Multiple options:

• Documentation: Check this documentation first
• Troubleshooting Guide: Common solutions in Troubleshooting page
• Email: support@techtonic.systems
• Website: https://wp-cdn-manager.1cdn.us

Q: How often is the plugin updated?

A: Regular updates for WordPress compatibility, bug fixes, and new features. Check changelog for update history.

Q: Can I request a feature?

A: Yes! Send feature requests to support@techtonic.systems. We review all suggestions.

Q: Is there a pro version?

A: Currently no. The plugin is feature-complete and free. Future premium features may be added based on user feedback.