Answer by MrWhite for Using htaccess to force HTTPS doesn't work

tl;dr You're HTTP to HTTPS redirect is in the wrong place. It needs to go near the start of the /clickandbuild/bebechan/.htaccess file, not at the end. (See below for further explanation.)

There seems to be a lot of misinformation / confusion here...

The host that takes care of my SSL just told me "The SSL that we provide with your contract only protect one domain OR one subdomain, not both"

That should OK, you only appear to have one domain. However, your SSL cert does need to cover both the domain apex (ie. example.com) and the www subdomain (ie. www.example.com) - it should do - I would be very surprised if it didn't. And by what you stated at the start of the question; it does.

They told them then that it's why bebechan.net/ebook wasn't protected but bebechan.net was.

That's nonsense. The security certificate (SSL cert) protects hostnames, not subdirectories. If example.com is protected then example.com/ebook is also protected, as is example.com/<anything>.

But, bebechan.net/ebook isn't a subdomain right? It's still part of my domain bebechan.net?

Exactly.

I just checked right now and it's written that the SSL is provided for 'clickandbuild/bebechan' and I indeed have a clickandbuild folder when I check my FTP ... and there is already a .htaccess there. Maybe that's the issue? Maybe I should edit this one instead of creating a new one in the root?

It's possible that the document root is set to the directory /clickandbuild/bebechan, but as noted above, SSL certs cover hostnames, not subdirectories.

For the sake of the rest of this answer, I will assume that /clickandbuild/bebechan is actually the document root directory. ie. the directory that is served when you request http://example.com/ (HTTP and HTTPS).

Your FTP screenshot is confusing/ambiguous. If there is a .htaccess file in the /clickandbuild/bebechan subdirectory then presumably that is where WordPress is installed? However, your screenshot appears to show a .htaccess file and WordPress installation in the root directory?! I assume this is above the document root? So, what do these files relate to?

...there is already a .htaccess there. Maybe that's the issue? Maybe I should edit this one instead of creating a new one in the root?

This could very well be the issue. You should not need to manually create the .htaccess file. WordPress will create (and use) one by default - it is necessary to drive the WordPress "pretty" permalinks, which you appear to already be using.

So yes, edit the existing .htaccess file. Do not create another .htaccess file elsewhere.

If you create a .htaccess file in a parent directory (eg. in the root directory from your FTP screenshot - which I assume is where you are creating this .htaccess file?) with a mod_rewrite redirect (which is what this is) then it will likely be overridden by the mod_rewrite directives in the subdirectories .htaccess file and simply be ignored (which appears to be what is happening).

The end of your existing /clickandbuild/bebechan/.htaccess file reads...

:<IfModule mod_rewrite.c>    RewriteEngine On    RewriteBase /    RewriteRule ^index\.php$ - [L]    RewriteCond %{REQUEST_FILENAME} !-f    RewriteCond %{REQUEST_FILENAME} !-d    RewriteRule . /index.php [L]</IfModule>AddHandler x-mapp-php5.5  .php# BEGIN WordPress<IfModule mod_rewrite.c>RewriteEngine OnRewriteBase /RewriteRule ^index\.php$ - [L]RewriteCond %{REQUEST_FILENAME} !-fRewriteCond %{REQUEST_FILENAME} !-dRewriteRule . /index.php [L]</IfModule># END WordPress<IfModule mod_rewrite.c>RewriteEngine OnRewriteCond %{SERVER_PORT} 80RewriteRule ^(.*)$ https://www.bebechan.net/$1 [R,L]</IfModule>

The main problem here is that the HTTP to HTTPS redirect is in the wrong place! It should not be at the end of the config file like this. It needs to go near the top of the .htaccess file - importantly, it needs to go before the WordPress front-controller (ie. the code block in the # BEGIN WordPress ... # END WordPress comment markers that currently precedes it).

By placing the redirect at the end, as it appears here then it will not do "much". It will redirect example.com/ (the document root), but not example.com/smth - which is the behaviour you stated initially in your question. However, you also stated that www.example.com/smth IS redirected - that behaviour cannot be explained by this.

In the above .htaccess file, the WordPress front-controller is also unnecessarily repeated - two blocks of code are identical - this is a mistake.

Solution

The end of that .htaccess file should read like the following instead:

:AddHandler x-mapp-php5.5  .php# HTTP to HTTPS redirectRewriteCond %{SERVER_PORT} 80RewriteRule (.*) https://www.bebechan.net/$1 [R=301,L]# BEGIN WordPress<IfModule mod_rewrite.c>RewriteEngine OnRewriteBase /RewriteRule ^index\.php$ - [L]RewriteCond %{REQUEST_FILENAME} !-fRewriteCond %{REQUEST_FILENAME} !-dRewriteRule . /index.php [L]</IfModule># END WordPress

About wordpress, I'm not sure how is it installed and I havent configured wordpress to do anything. Maybe I should?

Yes, you should. Either using a plugin or manually... you need to ensure that the "WordPress Address (URL)" and "Site Address (URL)" are set correctly (ie. probably to https://www.example.com/). You may need to also set define('FORCE_SSL_ADMIN', true); in the wp-config.php file. There is more information about configuring WordPress elsewhere.

You don't want your .htaccess redirects to conflict with what WordPress thinks your canonical URL should be.