SSL Insecure Content Fixer

Beschreibung

Clean up your WordPress website’s HTTPS insecure content and mixed content warnings. Installing the SSL Insecure Content Fixer plugin will solve most insecure content warnings with little or no effort. The remainder can be diagnosed with a few simple tools.

When you install SSL Insecure Content Fixer, its default settings are activated and it will automatically perform some basic fixes on your website using the Simple fix level. You can select more comprehensive fix levels as needed by your website.

WordPress Multisite gets a network settings page. This can be used to set default settings for all sites within a network, so that network administrators only need to specify settings on sites that have requirements differing from the network defaults.

See the SSL Insecure Content Fixer website for more details.

Übersetzungen

Many thanks to the generous efforts of our translators:

If you’d like to help out by translating this plugin, please sign up for an account and dig in.

Contributions

Installation

  1. Either install automatically through the WordPress admin, or download the .zip file, unzip to a folder, and upload the folder to your /wp-content/plugins/ directory. Read Installing Plugins in the WordPress Codex for details.
  2. Aktiviere das Plugin im ‚Plugins‘ Menu in WordPress.

If your browser still reports insecure/mixed content, have a read of the Cleaning Up page.

FAQ

Installation Instructions
  1. Either install automatically through the WordPress admin, or download the .zip file, unzip to a folder, and upload the folder to your /wp-content/plugins/ directory. Read Installing Plugins in the WordPress Codex for details.
  2. Aktiviere das Plugin im ‚Plugins‘ Menu in WordPress.

If your browser still reports insecure/mixed content, have a read of the Cleaning Up page.

How do I tell what is causing the insecure content / mixed content warnings?

Look in your web browser’s error console.

NB: after you open your browser’s console, refresh your page so that it tries to load the insecure content again and logs warnings to the error console.

Why No Padlock? has a really good online test tool for diagnosing HTTPS problems.

I get „insecure content“ warnings from some of my content

You are probably loading content (such as images) with a URL that starts with „http:“. Take that bit away, but leave the slashes, e.g. //www.example.com/image.png; your browser will load the content, using HTTPS when your page uses it. Better still, replace „http:“ with „https:“ so that it always uses https to load images, e.g. https://www.example.com/image.png.

Wenn deine Seite außerhalb von Browsern benutzt werden kann (z.B. in E-Mails oder anderen Dokumenten außerhalb des Webs), dann solltest du immer ein Protokoll verwenden und es sollte wahrscheinlich „https:“ sein (weil du ein SSL-Zertifikat hast). Siehe Inhalte bereinigen für mehr Details.

My website is behind a load balancer or reverse proxy

If your website is behind a load balancer or other reverse proxy, and WordPress doesn’t know when HTTPS is being used, you will need to select the appropriate HTTPS detection settings. See my blog post, WordPress is_ssl() doesn’t work behind some load balancers, for some details.

I get warnings about basic WordPress scripts like jquery.js

You are probably behind a reverse proxy — see the FAQ above about load balancers / reverse proxies, and run the SSL Tests from the WordPress admin Tools menu.

Ich habe die HTTPS-Erkennungs-Einstellungen geändert und jetzt kann ich mich nicht einloggen

Wahrscheinlich liegt ein Konflikt mit einem anderen Plugin vor, das versucht die HTTPS-Erkennung zu fixen. Füge die folgende Zeile deiner wp-config.php hinzu, über den Zeilen ABSPATH. Anschließend kannst du dieses Plugin auf seine Standard-Einstellungen zurücksetzen, bevor du weitermachst.

define('SSLFIX_PLUGIN_NO_HTTPS_DETECT', true);
I still get „insecure content“ warnings on my secure page

Post about it to the support forum, and be sure to include a link to the page. Posts without working links will probably be ignored.

You listed my plugin, but I’ve fixed it

Great! Tell me which plugin is yours and how to check for your new version, and I’ll drop the „fix“ from my next release.

Rezensionen

Fantastic

I am not a coder, so I easily get confused. Was super easy to use. I did not realize I needed it since my site was https already, then I found out I was getting the message „site not fully secure“. After looking around a while I got this plugin and everything is fine. Had to play with the settings a bit….went with the „capture“ setting, the first couple did not do the job for me.

No noticeable change in my page speed and now it is truly secure! Thanks so much.

Google couldn’t access your site because of a DNS error

Hi everyone,

I have recently redirect my old domain http://www.livecricketworldcup.com/ to https://www.livecricketworldcup.com/ under the same webmaster account. I am installed SSL Insecure Content Fixer it is working fine and I am using cloudflare for this site i am done everything in cloudflare. I have also changed the „change of address“ to notify google about the redirect. In my livecricketworldcup.com/ webmaster property showing the following error. I have also use the fetch as google option and it returns successful result and robots.txt is also working fine.

Lies alle 161 Rezensionen

Mitwirkende & Entwickler

„SSL Insecure Content Fixer“ ist Open-Source-Software. Folgende Menschen haben an diesem Plugin mitgewirkt:

Mitwirkende

„SSL Insecure Content Fixer“ wurde in 13 Sprachen übersetzt. Danke an die Übersetzerinnen und Übersetzer für ihre Mitwirkung.

Übersetze „SSL Insecure Content Fixer“ in deine Sprache.

Interessiert an der Entwicklung?

Durchstöbere den Code, sieh dir das SVN Repository an oder abonniere das Entwicklungsprotokoll per RSS.

Änderungsprotokoll

The full changelog can be found on GitHub. Recent entries:

2.5.0, 2017-11-23

  • changed: .htaccess rules file for non-WP test script now supports Apache v2.4; thanks, Andreas Schneider!
  • added: option to only fix content resource links for the current website; thanks, Luke Driscoll!
  • added: support for KeyCDN https detection via the X-Forwarded-Scheme header