Fixing CORS issues with Font-Icons in Mapped Domains

After mapping a domain to a sub-site you might find out that site having trouble to load custom fonts. That’s caused by a cross-origin block on your server settings.

Since font files are almost always loaded directly from CSS, our domain mapping plugin is not able to rewrite the URLs to use the mapped domain instead of the original one, so in order to fix the issue, you’ll need to amend your server configuration files.

Below are code snippets to fix the issue for Apache and NGINX. These changes require advanced knowledge about server configuration files (.htaccess files and NGINX config files). If you are not comfortable with making those changes yourself, send this page to your hosting provider support agents when requiring assistance.


On your .htaccess file, add:

<IfModule mod_headers.c>

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



On your server config file (the location varies from server to server), add:

location ~ \.(ttf|ttc|otf|eot|woff|font.css|css)$ {

  add_header Access-Control-Allow-Origin “*”;

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.