Not loading correctly my website, giving error/ not secure connection…

hello everyone,

I heard more than once now people not loading correctly my website, giving error/ not secure connection…

I read the article and trying to edit the htaccess file it doesn’t really work…
doesn’t paste the command line and if I write it should be all in one line … doesn’t aloud me to go to a new one…

What to do?


Did you create a .htaccess file inside of your htdocs folder and edit that one?


no I found it
doesn’t aloud me either to create a new one…
saying there’s some problem with ftp…

I split your posts to the a new topic in Hosting Support. Please keep the replies to documentation articles about the articles themselves, not about specific websites.

It sounds like you didn’t do this:


Your website loads just fine on HTTPS.


It really seems like you’re not creating the .htaccess file in the correct folder.
Are you creating it here?

If so, can you send a screenshot of the .htaccess file and the error you’re getting?


So is like you see opening the filemanager,
then opening htdocs there’s the htaccess file

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! :slight_smile: 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 :wink:


You did not follow instructions.

Did you not see the “DO NOT EDIT” warning in the htaccess outside the root?


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.


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.


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.