phbernard

Great! Thank you for the feedback!!

Thank you very much for your feedback Tobias!

The SSL certificate was just updated. That should fix the issue.

Could you please retry?

Hi,

I’m sorry for this inconvenience.

I can’t reproduce the issue: the URL in the error message works, whatever I use Chrome or CURL (the tool used in background by your WordPress site).

How is your site hosted? If you are using a hosting provider, which one is it?

The problem might come from an old version of CURL or OpenSSL, something you can’t do anything about if you are using a hosting provider.

Whatever the root cause, I’m going to try a workaround, which I’ll deploy on Sunday.

I’m glad you found a workaround!

Here is the trick to be W3C compliant, without hack: when you are on RealFaviconGenerator and you design you icons, in the “macOS Safari” section, choose “No icon” (full caption: “No icon. Safari uses the first letter of your domain name to create a default icon. You should use this option if your site absolutely needs to be W3C compliant.”).

Unless you definitely don’t want to spend any more time on this topic, I advice you to create your favicon again and this time select “No icon” as the macOS Safari choice. The reason for this is that the plugin not only generated the mask icon, it also kept trace of it. And if it upgrades the icons automatically (yes, it can do that, for example when Apple releases a new Touch icon with a higher resolution…), your hack will be overwritten, the mask icon will be back and the validation will fail again.

I hope that helps!

Thanks! 🙂

Thanks Mario!