I cannot do the screenshot cause it disappear the menu of the right click … where normally you have copy paste delete… …
but I can say the voices appearing in the menu that opens:
1 change all occurrences
2 cut
3 copy
4 command palette
well… done at the end with keyboard commands! 
i hope it’s fine!!
I know mostly it load well but more than one person had warning message … if the command in htaccess makes more stable this encrypted url x everyone good!!!
I copied and pasted.
thanks x your assistance as always and if you could check how it looks now I really thank you cause is a professional eye more 
thanks
You did not follow instructions.
Did you not see the “DO NOT EDIT” warning in the htaccess outside the root?
5 Likes
Yes,
The file I edited was a htaccess file in htdocs already there maybe created by wordpress itself.
Is not ok?
I tried to create one but didn’t aloud me for some ftp error.
This morning I opened the website and gave me a warning error too :-/
So is not well done the copy/paste of command done to open https in htaccess ?
If there is already a .htaccess file, you’ll want to add the rules to it. Of course, if you try to create a file that already exists, it won’t work.
Right now, your website doesn’t seem to force HTTPS at all, which is why you may see Not Secure errors.
Also, if your .htaccess file already has a lot of rules in it, please consider that rewrite rules are evaluated from top to bottom. So if there are other rules in the file that apply before the HTTPS rules are hit, the HTTPS rules are never applied.
One possible solution may be to move the HTTPS rules to the top of the files, so they are evaluated before all other rules.
3 Likes
thanks,
ok
done…
let’s see…
I don’t know where you see that is not set : to force all… https…
anyway I add screenshots
looks me lot about AllInOne Wordpress security rules/settings
and in the beginning the web health status had some issues…
(imported website)
And I rewrote like this… is ok?
Should I erase the last lines (https rules previously added?) and I’m not sure about which rules maybe about http…
do you see that to erase?
Yep, that looks a lot better! I can also see the force HTTPS rules are being applied now, so I think it works!
I think you’ll only want to keep the force HTTPs lines at the top, those at the bottom can be removed.
Of course, please make sure to not make any modifications to the existing rules of WordPress and the security plugin you’re using.
5 Likes
ok, thanks so much!!
is doing that to me too now… not secure connection…
after applying the new rules it opened once or twice easily and then gives not secure connection… like if is a new device first time visiting it doesn’t load directly…
what more can I do…?
I think I followed the all suggestions to force all connections to https…
I checked your site and it’s still forcing HTTPS to me. I don’t see why you would see a “not secure” issue. Could you please try to clear your browser cache? Because that may also prevent the redirect from taking effect.
5 Likes
ok, thanks.
I’ve done it…
on the pc it works, on the smartphones no…
??
hello,
sorry what do you suggest?
waiting to see if could be fixing in the new set I can see it doesn’t.
Keeps loading weel on te pc and giving to me not secure connection on smartphones…
Do I erase the lines?
What can I do?
Gently
and merry Christmas!!
is it possible to follow more privately ?
Please
testing the website with wpsupercache it gives 3 html all beginning with http… why?
when I downloaded wordpress by softaculous I wrote directly https, made a ssl certificate and imported by a wordpress importer plugin the exported copy I had… Gaves some issues on the health screen
Could it be related with this?
Now In a different browser (mullvad) it goes on unsecure connection even on the pc… 
And results to be not trusted certificate being self-signed certificate (again?!)
Wow… Moving on the other topic if you want, what should I do?
So what exactly is this “not secure” message you’re getting? Any specifics or error codes?
I’m guessing the certificate isn’t “self signed” (certificates don’t suddenly become signed in a different way), but rather “not trusted”. Please remember that “self signed” means it’s “not trusted”, but “not trusted” doesn’t mean it’s “self signed”.
This could be caused by the lack of CA chain support on free hosting, meaning any SSL certificate is installed is technically incomplete. For 99% of all browsers, this is not an issue, but it appears that for some of the browsers you’re using, it is.
I don’t understand what you mean. What does WP Super Cache have to do with any of the issues in this topic?
7 Likes
And about the wpsupercache my question is why it reports the 3 times testing my website address with http , even if is caching in html… It shouldn’t see the https address?
Thanks!!
Right, that makes more sense. It says “because its certificate issuer is unknown, the certificate is self-signed or the server is not sending the correct intermediary certificates”. Like the message says, the certificate being self signed is one of the options, but there are other options.
Why is why I wrote this:
I’m sorry, but this doesn’t make it more clear for me. I know roughly what WordPress caching plugins are supposed to do, but I’m not familiar with all the features and options of WP Super Cache specifically.
As far as I know, a caching plugin just caches stuff. So when you say it does “reporting” and “testing”, I don’t know what you mean.
If you haven’t do so already, please make sure that your WordPress site URL is configured to use HTTPS as well:
5 Likes
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.