I upgraded my instance last night after putting it off for many months, and now almost all of my icons have stopped working, pro and non-pro. Below is a video of the category icon selector to demonstrate. You can see I previously had fal-comment-pen. I also tried different combinations, with differing results: Light/Classic [CleanShot 2025-12-30 at 08.50.39@2x] Regular/Classic [CleanShot 2025-12-30 at 08.49.20@2x] I’ve double checked my web_only.yml configuration and everything looks good, including the key. But the issue seems to go beyond pro, so I’m not sure where to go from here, any suggestions?

I removed the raise_on_fail: false and then the rebuild failed with this: I, [2026-01-04T17:38:39.450544 #1] INFO -- : > cd /var/www/discourse/plugins/discourse-fontawesome-pro && /var/www/discourse/plugins/discourse-fontawesome-pro/scripts/install.sh fatal: detected dubious ownership in repository at '/var/www/discourse' To add an exception for this directory, call: git config --global --add safe.directory /var/www/discourse ERROR Error during pnpmfile execution. pnpmfile: "/var/www/discourse/.pnpmfile.cjs". Error: "Command failed: git clean -f -X app/assets/javascripts fatal: detected dubious ownership in repository at '/var/www/discourse' To add an exception for this directory, call: git config --global --add safe.directory /var/www/discourse ". For help, run: pnpm help install I, [2026-01-04T17:38:40.142946 #1] INFO -- : [.pnpmfile.cjs] Detected old app/assets/javascripts directory. Cleaning up gitignored files... FAILED -------------------- Pups::ExecError: cd /var/www/discourse/plugins/discourse-fontawesome-pro && /var/www/discourse/plugins/discourse-fontawesome-pro/scripts/install.sh failed with return # Location of failure: /usr/local/lib/ruby/gems/3.3.0/gems/pups-1.3.0/lib/pups/exec_command.rb:131:in `spawn' exec failed with the params {"cd"=>"$home/plugins/discourse-fontawesome-pro", "cmd"=>["$home/plugins/discourse-fontawesome-pro/scripts/install.sh"]} bootstrap failed with exit code 1 ** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one. ./discourse-doctor may help diagnose the problem. be6b0968a3bab273e52bd1927a6c3dac611a9e6103c75fa7ce8ea9b85ea3e233 x86_64 arch detected. 755bbed4f3cf Nothing to do, your container has already started! So I did this: - exec: cd: $home/plugins/discourse-fontawesome-pro cmd: - git config --global --add safe.directory /var/www/discourse - $home/plugins/discourse-fontawesome-pro/scripts/install.sh Which then successfully rebuilt and I’m back in business!

At some point font awesome changed the names of a bunch of stuff. There were some things in place to map to the old names, but maybe those aws gone now?

I tried removing the FA Pro plugin, and the non-pro icons returned, so it does seem to be an issue with the plugin. [CleanShot 2025-12-30 at 19.07.58@2x]

I’ve determined it’s only pro icons that are not displaying, I was initially on Light, which are all pro. Is anyone else having this issue or just me?

Fontawesome broken after upgrade?

Product Support

davidkingham (David Kingham) December 30, 2025, 6:25pm 3

Thanks Jay, I remember going through that process this summer, so I don’t think that’s it. Especially since many of the default icons are missing as well. For example:

Topic		Replies	Views
Pro icons plugin broken? Product Support fontawesome-pro	2	139	February 13, 2025
Did something with icons update overnight? Product Support fontawesome-pro	7	317	November 5, 2025
Ginormous icons after upgrade today Product Support	21	2269	December 1, 2018
FontAwesome Pro Plugin Not Changing All Default Icons Bug fontawesome-pro	5	454	June 12, 2025
Bookmark clock icon broken after changing icon set Bug fontawesome-pro	12	830	September 30, 2024

Fontawesome broken after upgrade?

Related topics