I want to add FontAwesome as a font in PRTG. I have updated the custom_styles.css as well as the htmlheader.htm to include the applicable stylesheets and links to the fonts. I consistently get a 404 on the files after confirming that they are there. Is the web server that powers PRTG blocking certain filetypes?

It seems to only fail on WOFF, WOFF2 and TTF filetypes. The EOT, SVG and OTF filetypes load fine and are located in the same directory.

Article Comments

Where do you try to use them actually? Just pasted 

/* latin */
@font-face {
  font-family: 'Raleway';
  font-style: normal;
  font-weight: 400;
  src: local('Raleway'), url(http://fonts.gstatic.com/s/raleway/v9/0dTEPzkLWceF7z0koJaX1A.woff2) format('woff2');
  unicode-range: U+0000-00FF, U+0131, U+0152-0153, U+02C6, U+02DA, U+02DC, U+2000-206F, U+2074, U+20AC, U+2212, U+2215, U+E0FF, U+EFFD, U+F000;
}
/* latin */
@font-face {
  font-family: 'Raleway';
  font-style: normal;
  font-weight: 800;
  src: local('Raleway ExtraBold'), local('Raleway-ExtraBold'), url(http://fonts.gstatic.com/s/raleway/v9/1ImRNPx4870-D9a1EBUdPPk_vArhqVIZ0nv9q090hN8.woff2) format('woff2');
  unicode-range: U+0000-00FF, U+0131, U+0152-0153, U+02C6, U+02DA, U+02DC, U+2000-206F, U+2074, U+20AC, U+2212, U+2215, U+E0FF, U+EFFD, U+F000;
}
/* latin */
@font-face {
  font-family: 'Raleway';
  font-style: normal;
  font-weight: 900;
  src: local('Raleway Heavy'), local('Raleway-Heavy'), url(http://fonts.gstatic.com/s/raleway/v9/PKCRbVvRfd5n7BTjtGiFZPk_vArhqVIZ0nv9q090hN8.woff2) format('woff2');
  unicode-range: U+0000-00FF, U+0131, U+0152-0153, U+02C6, U+02DA, U+02DC, U+2000-206F, U+2074, U+20AC, U+2212, U+2215, U+E0FF, U+EFFD, U+F000;
}

*{font-family: "Raleway" !important; }

...this into my styles_custom.css and it works seemlessly :)


Aug, 2015 - Permalink

I am including the font-awesome.css in the htmlheader.htm. The stylesheet then references the fonts that I have put in /css/fonts (new folder). They were returning HTTP 404 errors. It turns out it was blocking by file extension on mine, and as soon as I renamed them to font.woff.css and then declared the format in the CSS it worked for me. It appears this was a webserver error rather than a CSS error.


Aug, 2015 - Permalink

And it works for you now comepletely? :)


Aug, 2015 - Permalink

It sure does. All content types are working as expected. Thankfully the server doesn't filter on MIME type ;)


Aug, 2015 - Permalink

Hehe, well done :) I'll mark your reply as best answer ;)


Aug, 2015 - Permalink