Font Awesome appears as "blocks" in Nginx under Freebsd 10.1

Asked

Viewed 1,386 times

3

I have a website that I have transported from Centos to Freebsd using rsync + mysqldump. Centos + Apache ran normal on Freebsd + Nginx gave this error: erro

I believe it is related to this code that "converts" f086 into an icon.

#primary_nav #nav_app_forums a:before {
    content: "\f086";
}

Instead of the icons appearing "blocks", I am using IP.Board 3.4.6 with the theme Dispersion and Promenu.

Does anyone have any idea how to solve?

Thank you.

nginx unix font

  • Are you sure the Font Awesome CSS is being imported to the page?

  • Yes, no bugs on the Chrome console and checked the paths.

  • To make a Font Awesome icon appear, you need to put the classes in a tag i, thus: <i class="fa fa-bed"></i>. Being fa-bed the class of the desired icon. See if this solves your problem. If you do not want to use i, you will need to copy all class properties fa and the icon class for your CSS rule.

  • Actually I didn’t edit any code, it’s all from IP.Board and Promenu: https://www.invisionpower.com/apps/board/ http:/community.invisionpower.com/files/file/5435-promenu-basic/ the strange thing is that it worked normal in Centos.

  • Apparently the source of the Font Awesome. Check that the source files have been migrated correctly, not corrupted and everything else. Also test by changing the CSS to use elsewhere, like this: <link rel="stylesheet" href="http://maxcdn.bootstrapcdn.com/font-awesome/4.3.0/css/font-awesome.min.css">

  • Still the same mistake.

  • 1

    You can inspect the element using the browser developer tools and see the source that is actually being used in these squares?

  • 1

    Any error appears in the console when opening the page?

  • No error appeared on the console no. This question is a little old, unfortunately I do not have the site anymore...

  • I voted to close that question as non-reproducible. The text of the question does not have enough information to know what is the cause of the problem or reproduce it, since there are numerous possible causes. The author of the question (@systematics) no longer has the site because the question is old. In this way, attempts to produce an answer (such as mine or the two deleted answers) will be guesswork attempts that cannot be ascertained. Therefore, there is no way to give a correct answer to this question, only kicks, and so I am voting for closure.

Show 5 more comments

1 answer

1

Sometimes I have this problem with uBlock Origin, which ends up blocking the download of fonts from Font Awesome.

If this is the cause, the solution is to simply unlock the source in uBlock Origin or another type of Adblock you are using. It is true that you have no way to force your user to unlock, and therefore guide you in cases like this turns out to be the best way out.

Browser other questions tagged nginx unix font

You are not signed in. Login or sign up in order to post.