273

So I'm trying to prototype a marketing page and I'm using Bootstrap and the new Font Awesome file. The problem is that when I try to use an icon, all that gets rendered on the page is a big square.

Here's how I include the files in the head:

<head>
        <title>Page Title</title>
        <link rel="stylesheet" href="css/bootstrap.css">
        <link rel="stylesheet" href="css/bootstrap-responsive.css">
        <link rel="stylesheet" href="css/font-awesome.css">
        <link rel="stylesheet" href="css/app.css">
        <!--[if IE 7]>
            <link rel="stylesheet" href="css/font-awesome-ie7.min.css">
        <![endif]-->
</head>

And here's an example of me trying to use an icon:

<i class="icon-camera-retro"></i>

But all that gets rendered in a big square. Does anyone know what could be going on?

Nabil Kadimi
  • 10,078
  • 2
  • 51
  • 58
Connor Black
  • 6,921
  • 12
  • 39
  • 70

44 Answers44

229

You must have 2 classes, the fa class and the class that identifies the desired icon fa-twitter, fa-search, etc …

<!-- Wrong -->
<i class="fa-search"></i>    

<!-- Correct -->
<i class="fa fa-search"></i>

Bootstrap 5 update

Note: "The fa prefix has been deprecated in version 5. The new default is the fas solid style and the fab style for brands." – Terje Solem

Nabil Kadimi
  • 10,078
  • 2
  • 51
  • 58
  • 4
    This should be the top answer, the CSS provided points to the right location for the font files so long as you dont move them - this was driving me up the wall thank you – alex3410 May 27 '16 at 09:50
  • 8
    Note: "The fa prefix has been deprecated in version 5. The new default is the fas solid style and the fab style for brands." – Terje Solem Feb 24 '18 at 12:52
  • 1
    This fixed it for me! I am using Angular (5 I think) along with primeng and it seems, that font-awesome already worked for e.g. MenuItem-definitions inside xx.component.ts (the icons rendered correctly). However: when adding something to xx.component.html (e.g. p-button with an icon), one **has to** add **fa** class **and** fa-! – Igor Mar 25 '18 at 23:56
  • 1
    @TerjeSolem the information you gave is very important. It solved my problem. as i was using older version but was using "fas" thanks – MindRoasterMir Feb 19 '19 at 17:56
  • The CSS classes are an absolute mess, and seem designed to cause problems for non-premium users. Even the documentation is incorrect, some of the icons tell you to use e.g. `fa-solid fa-comment` in v5, but the icon only loads using `fa fa-solid fa-comment` which according to their site is deprecated. – Jesse Nickles Sep 14 '22 at 17:48
157

According to the documentation (step 3), you need to modify the supplied CSS file to point to the font location on your site.

mayhewr
  • 4,003
  • 1
  • 18
  • 15
  • 7
    Great answer, just to give some additional info, you can as well place the fonts in the default path provided by the css, just open Font-awesome.css and you will find the following entry: @font-face { font-family: 'FontAwesome'; src: url('../font/fontawesome-webfont.eot?v=3.2.1'); src: url('../font/fontawesome-webfont.eot?#iefix&v=3.2.1') – Braulio Sep 16 '13 at 10:29
  • 1
    Just for future ASP.NET MVC readers with the same problem: If you have all the folders in the correct place, verify if you added the MIME type on your web.config file as pointed here: http://stackoverflow.com/questions/4015816/why-is-font-face-throwing-a-404-error-on-woff-files – jpgrassi Sep 10 '14 at 13:51
  • 1
    If you use the Data URI Scheme with a base64 version of the font (can easily convert online), then you don't have to worry about proper file path and resource hosting. – RenaissanceProgrammer Apr 21 '15 at 19:13
  • **Note**:if you don't want to modify the css, just put css and fonts in same folder, check [this](http://stackoverflow.com/a/30098214/2218697) – Shaiju T May 07 '15 at 10:27
  • It is still useful if using it building some browser extensions, where JS files must be local – VMh Mar 15 '16 at 05:13
  • 11
    @tutuca: Not everybody can use a CDN. – Lightness Races in Orbit Sep 02 '16 at 10:23
  • @tutuca are you saying you'r using the cdn. but when running it in local host the icons just do not render ? – eran otzap Aug 11 '18 at 19:14
  • I did all of this and I cant still resolve the empty square showing box. On local. I cant used CDN. – Mike Jun 07 '19 at 17:46
  • Not answerers fault, but modifying the css is not a great process, because if you're integrating these files using npm then they are going to get overwritten each restore. This is why libs like bootstrap let you supply your own variables file to mix in during compile with the default files so you can provide variables without modifying the package files. – AaronLS Aug 30 '19 at 16:18
  • 1
    Updated Hosting documentation by FontAwesome https://fontawesome.com/how-to-use/on-the-web/setup/hosting-font-awesome-yourself – chri3g91 Oct 12 '19 at 19:50
80

Use this

<link href="https://maxcdn.bootstrapcdn.com/font-awesome/4.2.0/css/font-awesome.min.css" rel="stylesheet">

I had similar issue with Amazon Cloudfront CDN but it got resolved after I started loading it from maxcdn

Antti29
  • 2,953
  • 12
  • 34
  • 36
Kumar Deepam
  • 989
  • 6
  • 11
  • 8
    this assumes you wish to use font-awesome's CDN. For a commercial production environment I would not do this. – Jay Edwards Apr 13 '18 at 14:23
  • @JayEdwards why not? – Agent Zebra Jan 05 '22 at 17:53
  • Because you're pulling from a resource that is not managed by you and is subject to whatever fate throws at it (e.g. scheduled server maintenance by font-awesome that you have no control over at times that are inconvenient for the region(s) in which you're hosting your service); to say nothing of the fact that you're relying on something that may be hosted nowhere near your own service, thereby adding needless traffic to your page load. Subject to your use-case I would use something webpack driven to locally retrieve the icons you need. E.g. In VueJS, I use Vue-Awesome. – Jay Edwards Jan 06 '22 at 00:08
  • this wont work as so many of my project now running to problem because of this CDN is not reachable best to do it host in your server. – sam kh Apr 17 '22 at 14:10
68

Check to ensure that you haven't inadvertently changed the font family on the icon. If you have changed the .fa item's font family from: FontAwesome the icon will not show. It's always something silly and small.

Dharman
  • 30,962
  • 25
  • 85
  • 135
Bren1818
  • 2,612
  • 1
  • 23
  • 28
  • 1
    Yep. Silly and small. This - changing the font for something else and affecting fontawesome icons - happened to me so many times that it's becoming stupid. – Edd Oct 22 '15 at 15:09
  • 3
    Yes - this line was to blame (to be more specific, the !important rule) : * { font-family: 'Source Sans Pro' !important} – Svet Feb 09 '16 at 22:19
  • Thank you so much! I was importing this and that only to find the issue with font-family override. – Naseem Ahamed Jun 22 '21 at 12:44
  • Be careful of another silly mistake: I was using the FREE version of font-awesome and was trying e.g. to use fa-binoculars with fa-regular, which only works for the PRO version, while fa-binoculars with fa-solid works with the FREE version, which made me think that I didn't install the fonts correctly. This answer reminded me of sanity-checks. – zmx Oct 31 '22 at 14:45
24

If you are using LESS or SASS, open the font-awesome.less/sass file and edit the path variable @fa-font-path: "../font"; which points to the actual fonts:

@fa-font-path: "../font";

@font-face {
  font-family: 'FontAwesome';
  src: url('@{fa-font-path}/fontawesome-webfont.eot?v=3.0.1');
  src: url('@{fa-font-path}/fontawesome-webfont.eot?#iefix&v=3.0.1') format('embedded-opentype'),
    url('@{fa-font-path}/fontawesome-webfont.woff?v=3.0.1') format('woff'),
    url('@{fa-font-path}/fontawesome-webfont.ttf?v=3.0.1') format('truetype');
  font-weight: normal;
  font-style: normal;
}

Same with CSS, except you edit the path in the @font-face declaration block:

@font-face {
  font-family: 'FontAwesome';
  src: url('your/path/fontawesome-webfont.eot?v=3.0.1');
  src: url('your/path/fontawesome-webfont.eot?#iefix&v=3.0.1') format('embedded-opentype'),
    url('your/path/fontawesome-webfont.woff?v=3.0.1') format('woff'),
    url('your/path/fontawesome-webfont.ttf?v=3.0.1') format('truetype');
  font-weight: normal;
  font-style: normal;
}
keepitreal
  • 547
  • 5
  • 15
jonschlinkert
  • 10,872
  • 4
  • 43
  • 50
21

Open your font-awesome.css theres code like :

@font-face {
  font-family: 'FontAwesome';
  src: url('../fonts/fontawesome-webfont.eot?v=4.5.0');
  src: url('../fonts/fontawesome-webfont.eot?#iefix&v=4.5.0') format('embedded-opentype'), url('../fonts/fontawesome-webfont.woff2?v=4.5.0') format('woff2'), url('../fonts/fontawesome-webfont.woff?v=4.5.0') format('woff'), url('../fonts/fontawesome-webfont.ttf?v=4.5.0') format('truetype'), url('../fonts/fontawesome-webfont.svg?v=4.5.0#fontawesomeregular') format('svg');
  font-weight: normal;
  font-style: normal;
}

you must have folder like :

font awesome -> css
             -> fonts

or the easiest way :

<link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/font-awesome/4.4.0/css/font-awesome.min.css">
Erga Kandly
  • 777
  • 1
  • 6
  • 17
18

You must have 2 classes, the fas class and the fa-* class. See Basic Use in the docs:

The fa prefix has been deprecated in version 5. The new default is the fas solid style and the fab style for brands.

// Correct (version >= 5)
<i class="fas fa-search"></i>    

// Wrong (version < 5)
<i class="fa fa-search"></i>
leymannx
  • 5,138
  • 5
  • 45
  • 48
Israel
  • 1,165
  • 11
  • 11
  • 7
    Didn't realise this - from v5 they now require a `fab` or `fas` class instead of the `fa` class. – Echilon Jul 10 '18 at 09:44
15

I am using Font Awesome 4.3.0 just linking from maxcdn works as mentioned here,

But to host in your server putting fonts and CSS in same folder worked for me, like this

enter image description here

Then just link the CSS:

<link href="~/fonts/font-awesome.min.css" rel="stylesheet" />
Dharman
  • 30,962
  • 25
  • 85
  • 135
Shaiju T
  • 6,201
  • 20
  • 104
  • 196
14

I tried to solve the same problem with a few previous solutions, but they didn't work in my situation. Finally, I added these 2 lines in HEAD and it worked:

<link rel="stylesheet" href="http://maxcdn.bootstrapcdn.com/font-awesome/4.3.0/css/font-awesome.min.css">
<link rel="stylesheet" href="http://fortawesome.github.io/Font-Awesome/assets/font-awesome/css/font-awesome.css">   
14

If you are using the version 5.* or greater, then you have to use the

all.css or all.min.css

Including the fontawesome.css does not work as it has no reference to the webfonts folder and there is no reference to the @font-face or font-family

You can inspect this by searching the code for the font-family property in fontawesome.css or fontawesome.min.css

the_haystacker
  • 1,585
  • 18
  • 20
9

I had this issue and went through each step carefully...even though I've been using FA for ages...and then I realized I had this line in my mail css file:

* {
font-family: Arial !important;
}

Silly mistake, but this could tip off someone in future!

J Doe
  • 121
  • 2
  • 11
7

I had this issue. The problem was I had a font-family CSS style with !important overriding the fontawesome font.

Jonny White
  • 875
  • 10
  • 21
6

In case you are working with Maven and Apache Wicket also check for the following in order to try to resolve the issue with Font-Awesome and icons not being loaded:

If you have placed your files for example in the following file structure

/src
 /main
  /java
   /your
    /package
     /css
      font-awesome.css
     /font
      fontawesome-webfont.eot
      fontawesome-webfont.svg
      fontawesome-webfont.svgz
      fontawesome-webfont.ttf
      fontawesome-webfont.woff

Check 1) Are you correctly using a Package Resource Guard in order to allow to load the font files correctly?

Example from your class which extends WebApplication:

@Override
public void init() {
    super.init();   
    get().getResourceSettings().setPackageResourceGuard(new PackageResourceGuard());

}

Check 2) After you have made sure that all fonts are correctly transferred to the Web Browser, check for what has been actually transferred to the Web Browser, i.e., did the integrity of the font files change? Compare the files in your source directory and the files transferred to the Web Browser using, e.g., the Web Developer Toolbar of Firefox and DiffDog (for file comparison).

In particular if you are using Maven be aware of resource filtering. Do not filter the folder where your /font files are contained - otherwise they will be corrupted.

Example from your pom.xml

<build>
    <finalName>Your project</finalName>
    <resources>
        <resource>
            <filtering>true</filtering>
            <directory>src/main/resources</directory>
        </resource>
        <resource>
            <filtering>false</filtering>
            <directory>src/main/java</directory>
            <includes>
                <include>**</include>
            </includes>
            <excludes>
                <exclude>**/*.java</exclude>
            </excludes>
        </resource>
    </resources>
</build>

In the example above we do not filter the folder src/main/java, where the css and font files are contained.

For further information on the filtering of binary data please also see the documentation:

http://maven.apache.org/plugins/maven-resources-plugin/examples/filter.html

In particular the documentation warns: "Warning: Do not filter files with binary content like images! This will most likely result in corrupt output. If you have both text files and binary files as resources, you need to declare two mutually exclusive resource sets. The first resource set defines the files to be filtered and the other resource set defines the files to copy unaltered..."

Philipp
  • 538
  • 6
  • 14
6

As of Dec 2018, I find it easier to use the stable version 4.7.0 hosted on bootstrapcdn instead of the font-awesome 5.x.x cdn on their website -- since every time they upgrade minor versions the previous version WILL break.

<link media="all" rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/font-awesome/4.7.0/css/font-awesome.min.css">

Icons are the same:

<i class="fa fa-facebook"></i>
ehacinom
  • 8,070
  • 7
  • 43
  • 65
5

font-weight: 900;

I had a different issue with Font Awesome 5. Default font-weight should be 900 for FontAwesome icons but I overwrote it to 400 for span and i tags. It just worked, when I corrected it.

Here is the issue reference in their Github page, https://github.com/FortAwesome/Font-Awesome/issues/11946

Dharman
  • 30,962
  • 25
  • 85
  • 135
manian
  • 1,418
  • 2
  • 16
  • 32
4

This should be much simpler in the new version 3.0. Easiest is to point to the Bootstrap CDN: http://www.bootstrapcdn.com/?v=01042013155511#tab_fontawesome

Font Awesome
  • 276
  • 1
  • 3
4

If your server is IIS, be sure to add the correct MIME to serve .woff file extension. The correct MIME is application/octet-stream

  • If you are using IIS 7, you can follow the procedure here: https://technet.microsoft.com/en-us/library/cc725608(v=ws.10).aspx – dresh Mar 16 '17 at 09:03
4

You must return the header Access-Control-Allow-Origin to * for your fonts files

tronic
  • 459
  • 2
  • 11
  • 2
    Exactly! Using third party providers to serve your font awesome files does not solve your problem, you just passing it to others to be solved. – Simanas Nov 22 '16 at 08:18
3

After struggling for finding a solution and NOT finding the official documentation helpful, this solved the issue for me:

  1. Download the Fontawesome.zip. I'm using version 5.10.2 and i got it from here https://fontawesome.com/download
  2. Inside the zip file there are several folders.You only need css and webfonts folders enter image description here

    1. Create 2 folders in your web projects, and name them css and webfonts. enter image description here

These names are mandatory. Now copy the content of css and webfonts from the zip into the corresponding folders in your project. And that's all!

Beware fontawesome! Awesomeness is making things simple for the user!

BabaNew
  • 884
  • 1
  • 13
  • 27
3

I was having the same issue with font awesome 5 downloaded with yarn, I made added the min.css file ALONG with the all.js file.

Hope this helps someone someone

<link  rel="stylesheet"   href="node_modules/@fortawesome/fontawesome-free/css/fontawesome.min.css">
<script src="node_modules/@fortawesome/fontawesome-free/js/all.js" charset="utf-8"></script>
2

It could be possible that your font path is not correct so that css not able to load the font and render the icons so you need to provide the stranded path of attached fonts.

@font-face { 
font-family: "FontAwesome";
src: url("fonts/fontawesome-webfont.eot");
}
SantoshK
  • 1,789
  • 16
  • 24
2

Use this <i class="fa fa-camera-retro" ></i> you have not defined fa classes

jitendra varshney
  • 3,484
  • 1
  • 21
  • 31
2

Starting in version 5, if you downloaded the package from this site:

https://fontawesome.com/download

The fonts are in the all.css and all.min.css file.

This is what your reference would look like using the latest version now (replace with your folder):

<link href="/MyProject/Content/fontawesome-free-5.10.1-web/css/all.min.css" rel="stylesheet">
live-love
  • 48,840
  • 22
  • 240
  • 204
2

MUST WORK THIS WAY

  1. make sure you have the fontawesome cdn linked in the top of your page fontawesome cdn
  2. make sure the .fa class has not been given another font-family property. Usually this happens when we give all the tags in our page a style. like this

* {
  font-family: Arial;
}

instead use this

*:not(.fa){
  font-family: Arial;
}
  1. make sure you typed in the exact class name give in the fontawesome website. copy and paste to make sure.

If you are using Cloudflare CDN you can use the link tag below to use font awesome in your page

<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/5.15.3/css/all.min.css">
<i class="fa fa-home"></i>
Abana Clara
  • 4,602
  • 3
  • 18
  • 31
A. Atal
  • 75
  • 2
  • 7
1

I have changed from 3.2.1 to 4.0.1 and the folder was font and now is called fonts.

src: url('../font/fontawesome-webfont.eot?v=3.2.1');

src: url('../fonts/fontawesome-webfont.eot?v=4.0.1');
Dharman
  • 30,962
  • 25
  • 85
  • 135
André Duarte
  • 295
  • 1
  • 11
1

I use the Official Font Awesome SASS Ruby Gem and fixed the error by adding the below line to my application.css.scss

@import "font-awesome-sprockets";

Explanation:

The font-awesome-sprockets file includes the sprockets assest helper Sass functions used for finding the proper path to the font file.

Marklar
  • 1,247
  • 4
  • 25
  • 48
1

if your using sass and have imported in your main.scss @import '../vendor/font-awesome/scss/font-awesome.scss';

The error may come from the font-awesome.scss file that is looking for the font files in it's relative path.

So remember to override the $fa-font-path variable: $fa-font-path: "https://netdna.bootstrapcdn.com/font-awesome/4.3.0/fonts" !default;

like this there is no need to add the cdn in your index.html

vilsbole
  • 1,922
  • 1
  • 18
  • 22
1

Double check the fontawesome-all.css file - at the very bottom there will be a path to the webfonts folder. Mine had "../webfonts" format in it, which meant that the css file would be looking 1 level up from where it is. As all of my css files were in css folder and I added the fonts to the same folder, this was not working.

Just move your fonts folder up a level and all should be well :)

Tested with Font Awesome 5.0

Web Dev
  • 2,677
  • 2
  • 30
  • 41
  • This should be the preferred answer since it answers the question directly without linking to outdated documentation. Kudos – Kyle Jun 17 '19 at 11:05
1

Use with the upper class

<div class="container">
  <i class="fa fa-facebook"></i>
</div>
Bengi Besçeli
  • 3,638
  • 12
  • 53
  • 87
1

The /css/all.css file contains the core styling plus all of the icon styles that you’ll need when using Font Awesome. The /webfonts folder contains all of the typeface files that the above CSS references and depends on.

Copy the entire /webfonts folder and the /css/all.css into your project’s static assets directory (or where ever you prefer to keep front end assets or vendor stuff).

Add a reference to the copied /css/all.css file into the of each template or page that you want to use Font Awesome on.

Just Visit - https://fontawesome.com/how-to-use/on-the-web/setup/hosting-font-awesome-yourself You will get the answer.

1

With the (free) Font Awesome 5 version, there's this tiny detail which was hard to figure out for me and I didn't pay attention to it:

Style   Availability    Style Prefix    Example Rendering
Solid   Free            fas             <i class="fas fa-camera"></i>
Brands  Free            fab             <i class="fab fa-font-awesome"></i>

(extracted from the documentation)

With this cited, brand icons such as fa-twitter or fa-react need to be used with class fab while all other (free) icons need to be used with class fas. That's easy to oversee.

Lars Blumberg
  • 19,326
  • 11
  • 90
  • 127
  • Yep, that was it. The `fa` prefix has been deprecated in version 5. The new default is the `fas` solid style and the `fab` style for brands. – leymannx Oct 31 '20 at 14:24
1

After 5+ hours of struggling I found what was causing the problem for me.

  1. Using FontAwesome 5 you should be using fas (notice the "s" at the end):

<i class="fas fa-camera"></i>
  1. I was using "regular" font, which apparently is paid in this version - I switched to "solid" and it all started working fine.
A Petrov
  • 417
  • 1
  • 9
  • 23
0

Using absolute instead of relative paths solved it for me. I was using relative paths (see first example below) and that didn't work. I checked via console and found the server was returning a 404, files not found.

Relative path caused a 404:

@font-face { 
font-family: "FontAwesome";
src: url("../fonts/fontawesome-webfont.eot?v=4.0.3");
}

Absolute path solved it cross browser:

@font-face { 
font-family: "FontAwesome";
src: url("http://www.mysite.com/fonts/fontawesome-webfont.eot?v=4.0.3");
}

I wouldn't recommend doing this unless you have to, but it works for me. Ofcourse, you should repeat this for all the font formats in the font-awesome.css file.

Tim
  • 1,680
  • 2
  • 15
  • 21
0

It wasn't working for me because I had Allow from none directive for the root directory in my apache config. Here's how I got it to work...

My directory structure:

root/
root/font-awesome/4.4.0/css/font-awesome.min.css
root/font-awesome/4.4.0/fonts/fontawesome-webfont.*
root/dir1/index.html

where my index.html has:

<link rel="stylesheet" href="../font-awesome/4.4.0/css/font-awesome.min.css">

I chose to continue to disallow access to my root and instead added another directory entry in my apache config for root/font-awesome/

<Directory "/path/root/font-awesome/">
    Allow from all
</Directory>
user3325776
  • 105
  • 2
  • 10
0

My problem was with adding the

<link rel="stylesheet" href="bower_components/font-awesome/css/font-awesome.min.css">

inside a

<!-- build:css assets/styles/main.css -->
<!-- endbuild -->

tag

I fixed it by placing it outside the tag.

Alex Burdusel
  • 3,015
  • 5
  • 38
  • 49
0

What fixed the issue for me (on my Windows 7 machine) was decrypting my project directory. It's crazy how many visual and functional glitches originally arise from that when testing your website. Just get to a command prompt and run:

attrib -R %PROJECT_PATH%\*.* /S
cipher /a /d /s:%PROJECT_PATH%

...where %PROJECT_PATH% is the full pathname to the directory where your code is stored.

ShieldOfSalvation
  • 1,297
  • 16
  • 32
0

Now in fontawesome 5 you can deliver a cached version of JS over Https.

<script defer src="https://use.fontawesome.com/releases/v5.0.9/js/all.js" integrity="sha384-8iPTk2s/jMVj81dnzb/iFR2sdA7u06vHJyyLlAd4snFpCl/SnyUjRrbdJsw1pGIl" crossorigin="anonymous"></script>

More info on https://fontawesome.com/get-started/svg-with-js

desertSniper87
  • 795
  • 2
  • 13
  • 25
0

I tried a number of the suggestions above without success.

I use the NuGeT packages. The are (for some reason) multiple named version (font-awesome, fontawesome, font.awesome, etc.)

For what it's worth: I removed all the version installed and then only installed the latest version of font.awesome. font.awesome just worked without the need to tweak or configure anything.

I assume there are a number of things are missing from the other named versions.

0

So many answers so I add my working for me (Change name if you dont use PRO): In _typography.less

//
//  Common
//  _____________________________________________

& when (@media-common = true) {
  .lib-font-face(
    @family-name: @font-family-name__fontawsomeregular,
    @font-path: '@{baseDir}fonts/webfonts/fa-regular-400',
    @font-weight: 400,
    @font-style: normal
  );
  .lib-font-face(
    @family-name: @font-family-name__fontawsomelight,
    @font-path: '@{baseDir}fonts/webfonts/fa-light-300',
    @font-weight: 300,
    @font-style: normal
   );
  .lib-font-face(
    @family-name: @font-family-name__fontawsomebrands,
    @font-path: '@{baseDir}fonts/webfonts/fa-brands-400',
    @font-weight: normal,
    @font-style: normal
  );
  .lib-font-face(
    @family-name: @font-family-name__fontawsomesolid,
    @font-path: '@{baseDir}fonts/webfonts/fa-solid-900',
    @font-weight: 900,
    @font-style: normal
  );
}

In _theme.less

@import '../includes/fontawesome/fontawesome.less';
@fa-font-path: '@{baseDir}fonts/webfonts';

//  Fonts
@font-family-name__fontawsomeregular: 'Font Awesome 5 Pro';
@font-family-name__fontawsomelight: 'Font Awesome 5 Pro';
@font-family-name__fontawsomebrands: 'Font Awesome 5 Brands';
@font-family-name__fontawsomesolid: 'Font Awesome 5 Pro';

and example of usage:

 .my-newclass:before{
     content: '\f002';
     display: inline-block;
     float: left;
     font-family:  @font-family-name__fontawsomelight;
     font-size: 16px;
}
BartZalas
  • 305
  • 5
  • 12
0

Please add

@import 'https://****.net/*********/font-awesome.min.css';
@font-face {
    font-family: 'FontAwesome';
    src: url('https://****.net/*********/FontAwesome.otf');
    src: url('https://****.net/*********/FontAwesome.otf?#iefix')
}

This to top of your css, download and link the css and font correctly, the problem is due to FontAwesome not loading correctly.

Thanks

subindas pm
  • 2,668
  • 25
  • 18
0

If you installed font-awesome via package manager (yarn or npm) then, please be aware which version was installed. Alternatively, if you've already installed font-awesome long time ago then, check what version was installed.

In essence, versions installed via package managers might be behind version that is shown on https://fontawesome.com/ website. Thus, as it is today (21.06.2019) package manager will install v4.7.0 as the latest version but, website will point to documentation that refers to v5.*.

Solution, visit the website that documents icons for v4.7.0 https://fontawesome.com/v4.7.0, copy appropriate icon e.g. <i class="fa fa-sign-in" aria-hidden="true"></i> and incorporate it into your html. More context can be found here.

Lukasz Dynowski
  • 11,169
  • 9
  • 81
  • 124
0

If the MIME TYPE is already having the .woff and .woff2 file types and still it's giving HTTP-404 error, check the request filtering. If this is restrictive, add these file types these with allow to serve and it shall work. Check it out!

0

In my case, I just copied

<i class="fa-solid fa-tags"></i> //provided by font awesome

for an existing front-end template that included some other icons from font awesome, but this did not worked, So by adding 'fas' class and it worked ;

<i class="fas fa-solid fa-tags"></i> //working
-1

I found a solution today which was to:

  1. Download the entire project from their Github page
  2. Then follow the rest of the steps on their page under the Default CSS section about moving the directory into your project and adding the link in the HEAD section of an .html file

The problem with their documentation is that they do not specify a link to where you should get a copy of the entire font-awesome project to put into your project.

Jesus Noland
  • 197
  • 2
  • 11