FontAwesome - Failed to decode downloaded font

failed to decode downloaded font: <url>
failed to decode downloaded font webpack
ots parsing error: invalid version tag
ots parsing error: failed to convert woff 2.0 font to sfnt
servicenow failed to decode downloaded font
failed to decode downloaded font proxy
font-awesome
failed to decode downloaded font flaticon woff

I found allready this: https://stackoverflow.com/search?q=Failed+to+decode+downloaded+font

But the Answers dont help to fix my problem =/

I got on my page this errors in console:

Failed to decode downloaded font: http://devcomlink.kunena.dev-monkeys.com/components/com_kunena/template/devcomlink/fonts/font-awesome/fontawesome-webfont.woff2
    index.php?option=com_kunena&view=category&layout=list&Itemid=129&templateStyle=9:1 Failed to decode downloaded font: http://devcomlink.kunena.dev-monkeys.com/components/com_kunena/template/devcomlink/fonts/font-awesome/fontawesome-webfont.woff
    index.php?option=com_kunena&view=category&layout=list&Itemid=129&templateStyle=9:1 Failed to decode downloaded font: http://devcomlink.kunena.dev-monkeys.com/components/com_kunena/template/devcomlink/fonts/font-awesome/fontawesome-webfont.ttf

URL to my page: http://devcomlink.kunena.dev-monkeys.com/index.php?option=com_kunena&view=category&layout=list&Itemid=129&templateStyle=9

in Firefox and IE11 the icons totaly dont load...

Have anyone a idea how i can fix this?

The problem isn't with your HTML or CSS code... It must be with the font files or the server,

because normal font files should contain codes and can be downloaded when opened in browser like this : https://cdnjs.cloudflare.com/ajax/libs/font-awesome/4.7.0/fonts/fontawesome-webfont.eot?v=4.7.0

While your files looks empty without any code even when downloaded: http://devcomlink.kunena.dev-monkeys.com/components/com_kunena/template/devcomlink/fonts/font-awesome/fontawesome-webfont.eot?v=4.3.0

Try to replace the files ...

Failed to decode downloaded font, "Failed to decode downloaded font" means the font is corrupt, or is incomplete (missing metrics, necessary tables, naming records, a million possible things). Sometimes this problem is caused by the font itself. It seems to be working now. I'm gonna give it a try and debugg in all the devices to confirm. Working with Appcache is a little tricky sometimes.

I'm just answering this for later viewers. If you are working with a maven-war-plugin make sure you exclude the .woff and .ttf files in the filtering or maven will make the files corrupt.

<plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-war-plugin</artifactId>
    <configuration>
        <filteringDeploymentDescriptors>true</filteringDeploymentDescriptors>
        <webResources>
            <resource>
                <directory>${basedir}/src/main/webapp</directory>
                <targetPath />
                <filtering>true</filtering>
                <excludes>
                    <exclude>**/*.woff</exclude>
                    <exclude>**/*.woff2</exclude>
                    <exclude>**/*.ttf</exclude>
                </excludes>
            </resource>
        </webResources>
    </configuration>
</plugin>

Failed to decode downloaded font � Issue #10026 � FortAwesome , When I go offline I get this error: > Failed to decode downloaded font: .com/ ardemo2/m5/fonts/fontawesome-webfont.woff2?v=4.6.3 > OTS pa. Hi, we use CDN version of the font awesome, so you cannot find them on your localhost. Here you can find different ways of implementation: http://fortawesome.github

I had the same problem, and finally managed to solve it. It may help someone.

I have quite a large .htacces file, with a lot of RewriteCond's and RewriteRule's, and also used the following line to filter some folders from those conditions:

RewriteRule  ^(css|functions|js|media|tpl|vendor)($|/) - [L]

Upon adding the fonts folder (simply called fonts, and located in public_html/), the problem was solved.

RewriteRule  ^(css|fonts|functions|js|media|tpl|vendor)($|/) - [L]

Note that this line should be fairly at the top of your .htaccess file to work.

OTS parsing error � Issue #40 � components/font-awesome � GitHub, It works fine on local, but when deployed, the browser fails to parse. Failed to decode downloaded font: http://xyz.com/fonts/fontawesome-webfont. Make sure your server is sending the font files with the right mime/type.. I recently have the same problem using nginx because some font mime types are missing from its vanilla /etc/nginx/mime.types file.

Similar to the maven-war-plugin usage, if you are using maven-resources-plugin you need to specify that font files extensions shouldn't be filtered :

<plugin>
    <artifactId>maven-resources-plugin</artifactId>
    <version>2.7</version>
    <configuration>
        <encoding>UTF-8</encoding>
        <nonFilteredFileExtensions>
            <nonFilteredFileExtension>ttf</nonFilteredFileExtension>
            <nonFilteredFileExtension>woff</nonFilteredFileExtension>
            <nonFilteredFileExtension>woff2</nonFilteredFileExtension>
        </nonFilteredFileExtensions>
    </configuration>
</plugin>

Got the solution from this SO answer.

Failed to decode downloaded font fonts/fontawesome-webfont.w , Thanks Failed to decode downloaded font: http://localhost:3000/fonts/ fontawesome-webfont.woff2?v=4.5.0 categoryTreeEditor:1 OTS parsing error: invalid� I am doing assets pre-compile, and running the application in production mode. After compilation when I load the my index page I got followings warnings in the chrome console: Failed to decode

For what it's worth, I ran into this issue on my shared web server. The permissions on my font files and the enclosing folder were incorrect. Took me forever to figure it out. Changed them to 755 for the folder and 644 for the font files. Works perfectly now.

Custom fonts returns "Failed to decode downloaded font", I just had the same issue – but with Font Awesome, which is a really well known font. Turned out this was caused by a problem with FTP. The file� Webpack: Failed to decode downloaded font. Ask Question Asked 3 years, 4 months ago. Active 11 months ago. Viewed 2k times 3. Using FontFaceObserver and getting a

Failed to decode downloaded font: <URL> - help, css . // fontawesome import '@fortawesome/fontawesome-free/css/all.css';. And I' ve also copied the fonts in� / # root of web server css/ file-that-import-fonts.css fonts/ font-file.ext The output css file was trying to import font files at the same folder level of it. So it always hit 404 /css/font.x and my server rendered 404 error was mistaken as a broken font. That's why Failed to decode downloaded font.

Failed to decode downloaded font, Failed to decode downloaded font: http://localhost:8000/fonts/fontawesome- webfont.woff2?v=4.7.0 home:1 OTS parsing error: invalid version� Hi, I am having some issue with MVC 5 project where my fonts for plugin summernote works fine locally but when I deploy to Azure I get the following errors: Failed to decode downloaded font: https:

fontawesome failed to decode downloaded font, fontawesome failed to decode downloaded font. Cancel. Save. Loading Product, Action Form, Action Grid, Advanced Search, App Sharp, Authorize. Dismiss Join GitHub today. GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.

Comments
  • Thanks! I dont realy understand why the files gone broken.... but now it works! ;)
  • I had corrupt font files when I installed ui-grid via npm and replaced them by downloading the files from GitHub.
  • I had the same issue with one (shared hosting) server and at first thought it was because of the theme. The problem was within WinSCP which for some reason uploaded font files in TEXT instead of BINARY mode. Re-uploading files in binary mode fixed the issue. You can check this visually by comparing file sizes, in text mode files were smaller in size by few hundred bytes.
  • This really helps.
  • :-) This helped me using an ExtJS application with springboot and maven mix. Thanks a lot! I wonder how to find out issues like that when not using stackoverflow. I did make a cross check on the maven-war-plugin page but could not grasp an idea of solving my issue.
  • Totally saved me. My icons are alive! Thanks.
  • In my case, this was my problem. Thanks