Hello!
TSF always outputs a fully qualified domain name; this includes the scheme (http(s):) in front.
Another plugin must be stripping the schemes from the URLs on your pages; you should deactivate that feature or plugin. To help you find it easier, the “http(s)” part is called “scheme,” and this feature claims to resolve “mixed content” errors with SSL/TLS.
If you get mixed content errors after removing the feature, you should rectify those manually (don’t use a plugin). The first step is to make sure that you use “https” at the General Settings of WordPress for options WordPress Address and Site Address. Then, look at your content and fix URLs that still use “http,” such as those of images.
Although unlikely, some older themes may still use “http” by default, but they should automatically switch schemes based on WordPress’s is_ssl() or set_url_scheme(). Reach out to the theme developer if their resources like JS, CSS, or SVG files use “http” instead of “https”.
If you like reading, Kinsta provides more details on the mixed content issue: https://kinsta.com/blog/mixed-content-warnings/.
Thank you it was WP-Rocket causing the issue.
