- June 12, 2019 at 5:51 pm #235518
My WordPress directory is a subdirectory, so my SSL test page is at https://www.teigfam.net/oyvind/home/wp-content/plugins/really-simple-ssl/ssl-test-page.php (see Disclaimer below).
However, my whole page starts at https://www.teigfam.net. I see that there are two .htaccess files: one at the top and one at WordPress’s /home/ directory. Both are the original versions, so it looks like Really Simple SSL has not modified that latter either.
It was my ISP that suggested using Really Simple SSL (https://help.one.com/hc/no/articles/115005594065-Slik-bruker-du-https-i-site-laget-med-WordPress – in Norwegian), so I did.
Q: However, what do I need to do to make all of the rest of my site HTTPS enabled?
Aside: I will try update about this here: https://www.teigfam.net/oyvind/home/publishing/061-wordpress/#https_and_ssl. Disclaimer: No money, ads, gifts or the like with my blog notes. Only fun and expenses!June 13, 2019 at 8:12 am #235856
the site seems to be working fine on SSL, both for the main domain and the WordPress directory. Did you manage to solve your issue? To force a non WordPress site over https://, you can manually add the redirect to the main .htaccess file. To find out which redirect to use, see https://really-simple-ssl.com/knowledge-base/manually-insert-htaccess-redirect-http-to-https/.June 13, 2019 at 8:28 am #235858
Hi and thanks,
my non WordPress parts are still displayed with “Not secure” to me.. Hmm.. Can I then be sure they are? How did you infer that they were secure?
I have been reading the page that you refer to, but the syntax that is required in the .htaccess file scares me.
How might it typically look in my case? Like SSL/HTTPS onJune 14, 2019 at 10:24 am #236143
Mark WoltersKeymasterJune 14, 2019 at 10:35 am #236148
This is more than nice! Thanks a lot! I have done as you suggested.