Use these troubleshooting techniques to resolve issues that occur when you use Typekit fonts through Adobe Muse.
When you publish your site using Business Catalyst, some Typekit fonts are not displayed properly in your live site. The fonts in the published site either revert to a default font like Arial, or the fonts appear small and different.
When you use Typekit fonts in your site and export your site as HTML, the font is not exported. Instead, you see a standard font in your published site.
When you export your site as HTML, or upload your site to an FTP host, you see the following error: “Internal Error: 403 Forbidden operation.”
Web fonts from Typekit are served only to those domains that you specify when you export your site. When you export your site from Adobe Muse to HTML, or when you upload your site to an FTP host, you need to add all your domain names.
Follow this procedure to add a domain name or a site URL when you export your site as HTML:
When you publish your Adobe Muse website, you see the following error message: “Error 0: Not Connected. Could not generate code to enable one or more web fonts on page.”
This error was fixed in the September 2015 update of the Creative Cloud desktop application. However, if there is a mismatch between your Muse login status, Typekit, and the Creative Cloud desktop app, you continue to see this error.
To resolve this issue:
You are not able to browse, select, or use the Skolar Web and Modesto fonts in your Adobe Muse sites.
Typekit no longer supports Skolar Web and Modesto fonts. See this announcement from Typekit for more information.
You cannot access Typekit through your account if your payment is under processing or if your payment has not been successful. The subscription account goes to a suspended state until the payment goes through. During this time you can use all the Creative Cloud services except Typekit.
To rectify this issue, contact the Customer Service team.