Support

Is the folder called webfont? Where is it placed? In your site's root or the administrator directory?  Your screenshots claim it's in both places at the same time which cannot, of course, be true. What is its exact path?

What are the extensions of your files? Case matters. TTF, ttf and Ttf are three different file extensions as far as your server is concerned.

Are the extensions of your files already present in the correct frontend or backend file types allowed in selected directories of .htaccess Maker and in the correct case (as I said: TTF, ttf and Ttf are three different file extensions!).

Your problem is that there is a mismatch in the subdomain you told .htaccess Maker to use and what you are using to access your site.

Check your configuration.php file. If you have a non-empty $live_site there try emptying it. If your site doesn't work with an empty $live_site please make sure that you are using the EXACT protocol and subdomain of your site. The following are four different sites:

• http://www.example.com
• http://example.com
• https://www.example.com
• https://example.com

Now go back to your .htaccess Maker page. Check what is the "Redirect www and non-www addresses" setting. You must choose something other than "Do not redirect".

Now scroll all the way down and check your "Host name for HTTPS requests (without https://)" and "Host name for HTTP requests (without http://)" settings.

If you chose "Redirect non-www to www" earlier these two domains MUST include the www. subdomain prefix.

If you chose "Redirect www to non-www" earlier these two domains MUST NOT include the www. subdomain prefix.

The technical explanation is that web fonts are static resources. Static resources can only be retrieved from the same domain and protocol as the page which tries to include them. If the protocol or domain (including the subdomain) do not match it's a cross-site request which may be rejected by some browser, most notably Firefox, at the preflight stage of the request i.e. when the browser considers whether to even send the request to the server. That would be why any change in the .htaccess had zero effect; a request was never made by your browser to the server in the first place.

This can happen if you are using the non-www to www redirection (or vice versa) but the canonical domain name you've entered in the .htaccess Maker doesn't match it. For example, if you tell the .htaccess Maker to redirect non-www to www but set the non-www domain name as the canonical all your static resources are now cross-site requests.

Unfortunately this cannot be caught programmatically because there are legitimate if less common use cases which involve a proxy or load balancer where a mismatch between what you enter in the redirect option and what you enter in the domain options are actually necessary.

You're welcome!