If you are using any of the above fonts, replace them with the corresponding "JF" font (such as Adage Script JF).
Typekit Error 400 when publishing or exporting an Adobe Muse site
Read this article to resolve "Error 400: Font not Available" when publishing or exporting Adobe Muse sites.
Font not available when you publish or export a site
When you publish or export your site from Adobe Muse, you see the following error: "Could not generate code to enable one or more fonts on page. [Error 400: Font not Available]"
Solution: Replace certain Typekit fonts
The following Typekit fonts can cause the issue:
- Proxima Nova Soft
- Adage Script
- Veer Annabelle
- Baroque Text
- Buena Park
- Corner Store
- Peachy Keen
- Franklin Gothic URW Condensed SC Book & Medium
- Baucher Gothic URW Alt and Alt Extended
- Leitura News
- Velino Poster
- Le Monde Sans Std Extra Demi
- Le Monde Sans Std 2 Extra Demi
- Luxi Serif
Typekit has retired Alverata PE, Alverata Informal PE, Alverata Irregular PE, Anisette Std Petite 2 Extra Light and Proxima Nova Soft font families from the Typekit Library. These fonts are replaced by the non-PE equivalently named fonts as found on the Alverata family page.
If you are using the Proxima Nova Soft font, you must manually change the font to Proxima Soft. To change the font, perform the following steps:
- Click File > Add/Remove Web Fonts.
- From Typekit, choose Proxima Soft, and Click OK.
- From your Adobe Muse page, select the text wherever you have used Proxima Nova Soft.
- From the Text drop-down list, choose the Proxima Soft font that you have added.
- Save the file and export/publish your HTML files.
If you are not using any of the above fonts or if replacing the font does not resolve the issue, do the following:
- Exit Adobe Muse.
- Sign out from the Creative Cloud application and sign in again.
- Relaunch Adobe Muse.
If your issue persists, visit Customer Care and click Still need help.