-
ChaoticanWriter
Hello team,
I noticed that the fonts I applied in GeneratePress were visible on pages when I didn’t have a domain name pointing to the space with SSL. … When I applied a domain name (oddfairpress.com), the fonts reverted to the basic Times New Roman, etc, despite what I have configured in the theme.
I’m not sure if this is a known issue with SSL and fonts. … I found some articles indicating that I would need to change some CSS or HTML referencing fonts from “Http/Https” to “//” instead, but I can’t seem to figure out where that lives in GeneratePress (if it is indeed theme related).
Probing to see if this is a known challenge. If so, I could use some help figuring out how to resolve.
Regards,
Matthew Olson -
George
Hello.
Most likely cause: Google Fonts are being loaded via
http://instead ofhttps://, which gets blocked by the browser’s security policy when the site is on SSL. You could check the browser console (F12 -> Console tab) for mixed content warnings — they’ll show exactly which resources are being blocked.Are you using the Font Library to upload your local fonts or have you uploaded Google fonts? Can you send us a URL?
-
ChaoticanWriter
I’m using the Font Library with installed fonts.
I do see errors under console:
Failed to load resource: net::ERR_CERT_COMMON_NAME_INVALIDUnderstand this error
Quarion-BookDEMO.otf:1 Failed to load resource: net::ERR_CERT_COMMON_NAME_INVALIDUnderstand this error
Quarion-BoldDEMO.otf:1 Failed to load resource: net::ERR_CERT_COMMON_NAME_INVALIDUnderstand this error
GraviolaSoft-Medium.otf:1 Failed to load resource: net::ERR_CERT_COMMON_NAME_INVALID -
George
Hello.
Seems to be a certificate mismatch rather than mixed content. The font files are being requested from a URL where the SSL certificate doesn’t match the domain name.
Looking at the Network tab (F12 → Network, then filter by “font” or look for the .otf files) I can see that there is a Cloudways app URL that the fonts are trying to be served from.
This usually happens when a site was migrated from a staging or temporary URL and the old paths are still stored in the database. The fix is typically either re-uploading through the Font Library or doing a search-replace in the database to update the old domain to oddfairpress.com.
-
ChaoticanWriter
That seems to have done it!
-
Good to know!
- You must be logged in to reply to this topic.