Issues with Font Awesome library

Hello @tamar

Thank you for your inquiry and I am happy to help.
The problem is with the CDN or to be precise the CORS configuration on the AWS.
So, you need to reach out to AWS support for assistance and check this link for assistance and this is also helpful.
Thanks!

Thanks @vmarko but I’m using MaxCDN – how is AWS a factor here?

Following up –

I already have the following in .htaccess, so I don’t think this is a CORS issue.

<FilesMatch "\.(ttf|ttc|otf|eot|woff|font.css|css|woff2)$">
Header set Access-Control-Allow-Origin "*"
</FilesMatch>

Hello @tamar

Thank you for the information. I can also see that AWS is being used.
If you check the console errors you will see the following for all fonts:
Access to font at 'https://tamarcom-tamar.netdna-ssl.com/wp-content/plugins/elementor/assets/lib/eicons/fonts/eicons.ttf?5.11.0' from origin 'https://tamar.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
SO the problem is with the CDN provider and the CORS rules.
Thanks!

Hmm. Well I’m not actually using AWS (I don’t have an AWS account LOL). So how do I turn this off?

And how do I refine the rule to fix what I pasted above?

Is there a way to rerun the wizard and start anew?

Hello @tamar

The rule seems fine, however the console errors are still there.
I would recommend reaching out to your CDN Provider for assiance.
Thanks!

Thanks. Is there a way to restart the wizard? Maybe I can clear things up that way?

Hello @tamar

Not likely but the only way is to create a new distribution on your CDN and then use the API to connect with the W3TC. I would strongly suggest you contact the support of the CDN provider.
Thanks!

There’s no way to flush the database of all W3TC instances and start anew?

Another reason why I’d want to is due to this error I am getting here:

The following memcached servers are not responding or not running:

Database Cache: 127.0.0.1:11211.
This message will automatically disappear once the issue is resolved.

If I try to reinstall W3TC from scratch, maybe it will not give me so many problems.

I don’t mind getting my hands dirty on a little MySQL. Let me know what I’d need to touch to start over.

Okay, I found a page that does a reinstall but you are right, there’s something else somewhere ?? I enabled CORS on my CDN – you mention AWS. I really don’t have an AWS account (I use Cloudflare too but not AWS). So my question is – where is AWS configured in W3 Total Cache? What code indicates the use of AWS?

So I reset my settings and I thought I’d update this because I have CORS set up correctly at the CDN.

I unchecked “host custom files” on W3’s settings and it worked. What’s weird is the item list on the custom files is the default stuff, so I’m not sure honestly why the CORS header didn’t get applied to the fonts even though it’s present on the settings on the homepage.

I’ll see about reaching out to them – thank you.