It looks as if http://www.arcate.ch gets redirected to https as expected, while arcade.ch redirects to wp-signup.php.
Can you send me a debug report and the added htaccess and wpconfig rules?
To check if the plugin is the cause: deactivate htaccess editing in the plugin settings, and remove the plugin redirects from your htaccess.
Yes you are correct it happens just if I don’t type the www
This is the debug report:
loading options…
pluginurl: https://www.arcate.ch/wp-content/plugins/really-simple-ssl/
plugin version: 2.2.6
testing for ssl…
SSL test page loaded successfully
ssl type: SERVER-HTTPS-ON
— ssl detected: TRUE
— force ssl: FALSE
Starting ssl configuration
No loadbalancer detected, so no wp-config fix needed.
testing htaccess rules…
htaccess rules test success.
checking if .htaccess can or should be edited…
per site activation or hsts option change, updating htaccess…
single site or networkwide activation
no siteurl/homeurl defines in wpconfig
converting siteurl and homeurl to https
This is the hatches part
<IfModule mod_rewrite.c>
RewriteEngine on
RewriteCond %{HTTPS} !=on [NC]
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L]
</IfModule>
The problem persist after erasing your part from htaccess and disabling the editing.
This is the remaining part in htacces:
# BEGIN WordPress
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ – [L]
# add a trailing slash to /wp-admin
RewriteRule ^wp-admin$ wp-admin/ [R=301,L]
RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ – [L]
RewriteRule ^(wp-(content|admin|includes).*) $1 [L]
RewriteRule ^(.*\.php)$ $1 [L]
RewriteRule . index.php [L]
# END WordPress
Based on your info, I think it has nothing to do with Really Simple SSL.
You could try fixing it by redirecting all requests to the www domain, by adding this to the top of your .htaccess:
RewriteCond %{HTTP_HOST} ^yourdomain.com [NC]
RewriteRule ^(.*)$ https://www.yourdomain.com/$1 [L,R=301]
You are right,
after making your trial I think my mistake was in the initial multisite configuration, where I left as domain http://www.arcate.ch instead of arcate.ch
In my other multisite installation my main domain has no www. and works fine
Ok the problem with the bad redirection has been corrected.
But on Firefox I still have the “Not Secure Connection” because not all the elements in the page are secure
IN your settings I see: Mixed content detected but that’s ok, because the mixed content fixer is active.
If I see ALL the mixed content is from themify, but it should be ok.
Then if I open the page code on firefox I see the only not https content is
<html itemscope=”itemscope” itemtype=”http://schema.org/WebPage” lang=”en-US”>
<div id=”page-4739″ class=”type-page” itemscope itemtype=”http://schema.org/Article”>
So I don’t understand why it is not working now…
As far as I can see there is only one insecure issue: the banner image. The link for this file is located in the themify framework css.
The insecure content fixer cannot fix css files dynamically, so that explains why the issue persists even with the mixed content fixer active.
I see. I am using other beautiful themes like enfold that do not have this issue.
Probably I am gonna change it….
Thanks
Ok the problem was solved. Themify support found a way
It was just needed to repeat the background assign after the SSL was already active.
