Multisite Wordpress, SSL and htaccess to use the subfolder as a root












1















I have an SSL sertificate, so http -> https is a must (as a precaution). I intend to have multiple subdomains, i.e. subdomain1.example.com, subdomain2.example.com, currently there is one subdomain that works without any issues. I'm using a multisite Wordpress setup, that was installed (purposely) in one subfolder. The multisite setup is for other languages. The current server folder layout is as follows:




  • public_html


    • backstage


      • subdomain1 (folder for the subdomain)


    • frontstage


      • wp-admin



      • wp-content



      • wp-includes



      • (the rest of the WP files)


    • index.php (a test file, that shouldn't load if the redirection is set up properly)




Currently, the www.example.com/frontstage/ opens the main WP site, this is fine. I can access its wp-admin without issues. www.example.com/frontstage/en/ shows a 404 page, this is not fine. www.example.com/frontstage/en/wp-admin/ opens the dashboard fine for the other site.



I want to retain the stripping out of index.php from any links (to keep the links clean).



There are two "simple" things to configure properly:




  1. I want to retain the server folder structure as it is, but having the "frontstage" folder skipped, so that when you visit www.example.com, the main WP site loads (and in the case someone would load www.example.com/frontstage/ it would redirect to www.example.com). Naturally, the "shift" needs to allow for the www.example.com/en/ to open the secondary website (any any other language sites that may follow). Ideally without rewriting all the links within the WP sites.

  2. Currently the /en/ site doesn't load its root. The demo posts and pages load fine.


My current .htaccess on the root level looks like this:



# disable index.php from urls

RewriteEngine On
RewriteBase /

<IfModule mod_rewrite.c>
# redirect index.php requests
RewriteCond %{THE_REQUEST} ^GET.*index.php [NC]
RewriteRule (.*?)index.php/*(.*) /$1$2 [R=301,L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ /index.php/$1 [L]
</IfModule>

# force https and www

RewriteCond %{HTTPS} off [OR]
RewriteCond %{HTTP_HOST} !^www.example.com$ [NC]
RewriteRule ^(.*)$ https://www.example.com/$1 [L,R=301]

# move wordpress one level up

# allow subdomain

RewriteRule ^backstage/subdomain1/?(.*)$ "https://subdomain1.example.com/$1" [R=301,L]


Any help with this is highly appreciated (I'm still learning the htaccess bits and tricks and this one is truly beyond me). What am I missing in the above code to get it right?










share|improve this question





























    1















    I have an SSL sertificate, so http -> https is a must (as a precaution). I intend to have multiple subdomains, i.e. subdomain1.example.com, subdomain2.example.com, currently there is one subdomain that works without any issues. I'm using a multisite Wordpress setup, that was installed (purposely) in one subfolder. The multisite setup is for other languages. The current server folder layout is as follows:




    • public_html


      • backstage


        • subdomain1 (folder for the subdomain)


      • frontstage


        • wp-admin



        • wp-content



        • wp-includes



        • (the rest of the WP files)


      • index.php (a test file, that shouldn't load if the redirection is set up properly)




    Currently, the www.example.com/frontstage/ opens the main WP site, this is fine. I can access its wp-admin without issues. www.example.com/frontstage/en/ shows a 404 page, this is not fine. www.example.com/frontstage/en/wp-admin/ opens the dashboard fine for the other site.



    I want to retain the stripping out of index.php from any links (to keep the links clean).



    There are two "simple" things to configure properly:




    1. I want to retain the server folder structure as it is, but having the "frontstage" folder skipped, so that when you visit www.example.com, the main WP site loads (and in the case someone would load www.example.com/frontstage/ it would redirect to www.example.com). Naturally, the "shift" needs to allow for the www.example.com/en/ to open the secondary website (any any other language sites that may follow). Ideally without rewriting all the links within the WP sites.

    2. Currently the /en/ site doesn't load its root. The demo posts and pages load fine.


    My current .htaccess on the root level looks like this:



    # disable index.php from urls

    RewriteEngine On
    RewriteBase /

    <IfModule mod_rewrite.c>
    # redirect index.php requests
    RewriteCond %{THE_REQUEST} ^GET.*index.php [NC]
    RewriteRule (.*?)index.php/*(.*) /$1$2 [R=301,L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule ^(.*)$ /index.php/$1 [L]
    </IfModule>

    # force https and www

    RewriteCond %{HTTPS} off [OR]
    RewriteCond %{HTTP_HOST} !^www.example.com$ [NC]
    RewriteRule ^(.*)$ https://www.example.com/$1 [L,R=301]

    # move wordpress one level up

    # allow subdomain

    RewriteRule ^backstage/subdomain1/?(.*)$ "https://subdomain1.example.com/$1" [R=301,L]


    Any help with this is highly appreciated (I'm still learning the htaccess bits and tricks and this one is truly beyond me). What am I missing in the above code to get it right?










    share|improve this question



























      1












      1








      1


      1






      I have an SSL sertificate, so http -> https is a must (as a precaution). I intend to have multiple subdomains, i.e. subdomain1.example.com, subdomain2.example.com, currently there is one subdomain that works without any issues. I'm using a multisite Wordpress setup, that was installed (purposely) in one subfolder. The multisite setup is for other languages. The current server folder layout is as follows:




      • public_html


        • backstage


          • subdomain1 (folder for the subdomain)


        • frontstage


          • wp-admin



          • wp-content



          • wp-includes



          • (the rest of the WP files)


        • index.php (a test file, that shouldn't load if the redirection is set up properly)




      Currently, the www.example.com/frontstage/ opens the main WP site, this is fine. I can access its wp-admin without issues. www.example.com/frontstage/en/ shows a 404 page, this is not fine. www.example.com/frontstage/en/wp-admin/ opens the dashboard fine for the other site.



      I want to retain the stripping out of index.php from any links (to keep the links clean).



      There are two "simple" things to configure properly:




      1. I want to retain the server folder structure as it is, but having the "frontstage" folder skipped, so that when you visit www.example.com, the main WP site loads (and in the case someone would load www.example.com/frontstage/ it would redirect to www.example.com). Naturally, the "shift" needs to allow for the www.example.com/en/ to open the secondary website (any any other language sites that may follow). Ideally without rewriting all the links within the WP sites.

      2. Currently the /en/ site doesn't load its root. The demo posts and pages load fine.


      My current .htaccess on the root level looks like this:



      # disable index.php from urls

      RewriteEngine On
      RewriteBase /

      <IfModule mod_rewrite.c>
      # redirect index.php requests
      RewriteCond %{THE_REQUEST} ^GET.*index.php [NC]
      RewriteRule (.*?)index.php/*(.*) /$1$2 [R=301,L]
      RewriteCond %{REQUEST_FILENAME} !-f
      RewriteCond %{REQUEST_FILENAME} !-d
      RewriteRule ^(.*)$ /index.php/$1 [L]
      </IfModule>

      # force https and www

      RewriteCond %{HTTPS} off [OR]
      RewriteCond %{HTTP_HOST} !^www.example.com$ [NC]
      RewriteRule ^(.*)$ https://www.example.com/$1 [L,R=301]

      # move wordpress one level up

      # allow subdomain

      RewriteRule ^backstage/subdomain1/?(.*)$ "https://subdomain1.example.com/$1" [R=301,L]


      Any help with this is highly appreciated (I'm still learning the htaccess bits and tricks and this one is truly beyond me). What am I missing in the above code to get it right?










      share|improve this question
















      I have an SSL sertificate, so http -> https is a must (as a precaution). I intend to have multiple subdomains, i.e. subdomain1.example.com, subdomain2.example.com, currently there is one subdomain that works without any issues. I'm using a multisite Wordpress setup, that was installed (purposely) in one subfolder. The multisite setup is for other languages. The current server folder layout is as follows:




      • public_html


        • backstage


          • subdomain1 (folder for the subdomain)


        • frontstage


          • wp-admin



          • wp-content



          • wp-includes



          • (the rest of the WP files)


        • index.php (a test file, that shouldn't load if the redirection is set up properly)




      Currently, the www.example.com/frontstage/ opens the main WP site, this is fine. I can access its wp-admin without issues. www.example.com/frontstage/en/ shows a 404 page, this is not fine. www.example.com/frontstage/en/wp-admin/ opens the dashboard fine for the other site.



      I want to retain the stripping out of index.php from any links (to keep the links clean).



      There are two "simple" things to configure properly:




      1. I want to retain the server folder structure as it is, but having the "frontstage" folder skipped, so that when you visit www.example.com, the main WP site loads (and in the case someone would load www.example.com/frontstage/ it would redirect to www.example.com). Naturally, the "shift" needs to allow for the www.example.com/en/ to open the secondary website (any any other language sites that may follow). Ideally without rewriting all the links within the WP sites.

      2. Currently the /en/ site doesn't load its root. The demo posts and pages load fine.


      My current .htaccess on the root level looks like this:



      # disable index.php from urls

      RewriteEngine On
      RewriteBase /

      <IfModule mod_rewrite.c>
      # redirect index.php requests
      RewriteCond %{THE_REQUEST} ^GET.*index.php [NC]
      RewriteRule (.*?)index.php/*(.*) /$1$2 [R=301,L]
      RewriteCond %{REQUEST_FILENAME} !-f
      RewriteCond %{REQUEST_FILENAME} !-d
      RewriteRule ^(.*)$ /index.php/$1 [L]
      </IfModule>

      # force https and www

      RewriteCond %{HTTPS} off [OR]
      RewriteCond %{HTTP_HOST} !^www.example.com$ [NC]
      RewriteRule ^(.*)$ https://www.example.com/$1 [L,R=301]

      # move wordpress one level up

      # allow subdomain

      RewriteRule ^backstage/subdomain1/?(.*)$ "https://subdomain1.example.com/$1" [R=301,L]


      Any help with this is highly appreciated (I'm still learning the htaccess bits and tricks and this one is truly beyond me). What am I missing in the above code to get it right?







      php wordpress .htaccess ssl multisite






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 25 '18 at 15:40









      billynoah

      10.6k54361




      10.6k54361










      asked Nov 24 '18 at 11:01









      V____V____

      62




      62
























          1 Answer
          1






          active

          oldest

          votes


















          0














          When I have WP installed within a subfolder, I just goto Settings => General and change the Website URL by removing the subfolder.



          Afterwards I move the file index.php one folder level up and in your case, would change it to:



           require( dirname( __FILE__ ) . '/frontstage/wp-blog-header.php' );


          Does this solve your problem?



          Find a detailed description how to move WP to a subdirectory on this site - You can find a detailed description about putting Wordpress in a subdirectory on the following website https://codex.wordpress.org/Giving_WordPress_Its_Own_Directory



          Regarding a redirection from http to https - this is possible within the .htaccess. Much better, in my opinion, would be an alias on the apache (this usually should be done by your hoster).



          The difference:



          The htaccess redirect goes back to the user and then again to the server, which costs some time. The alias is - as far as I know - redirected on the server.



          if you want to force https, you can do it with the following entry.



          <IfModule mod_rewrite.c>
          RewriteEngine On
          RewriteCond %{SERVER_PORT} !^443
          RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L]
          </IfModule>





          share|improve this answer


























          • Tried with the procedure you describe, I get a blank start page with the error "Can't establish a database connection" - something along those lines, written in a large black font (generated by WP, not by the server). Regarding the https, I left that in the htaccess just out of precaution, in case the SSL validity ends (and I guess I'll be moving to another server pretty soon, with not being able to immediately transfer the SSL).

            – V____
            Nov 24 '18 at 19:31













          • Isn't the current statement just checking if it is not https that it will forward to the same link with https, but if it is https (as probably properly configured by the host, I get https links even without that piece of code in the htaccess) it just skips any action on that matter?

            – V____
            Nov 24 '18 at 19:35











          • Did you reset the htaccess to the original one?

            – AnotherArt
            Nov 25 '18 at 8:46











          • If you mean the WPs htaccess, it was untouched from the start, I only made changes in the root's htaccess (my custom htaccess, everything in the folders works fine even without it)

            – V____
            Nov 25 '18 at 13:51











          • I would remove any htaccess.

            – AnotherArt
            Nov 25 '18 at 15:04











          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53457447%2fmultisite-wordpress-ssl-and-htaccess-to-use-the-subfolder-as-a-root%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          0














          When I have WP installed within a subfolder, I just goto Settings => General and change the Website URL by removing the subfolder.



          Afterwards I move the file index.php one folder level up and in your case, would change it to:



           require( dirname( __FILE__ ) . '/frontstage/wp-blog-header.php' );


          Does this solve your problem?



          Find a detailed description how to move WP to a subdirectory on this site - You can find a detailed description about putting Wordpress in a subdirectory on the following website https://codex.wordpress.org/Giving_WordPress_Its_Own_Directory



          Regarding a redirection from http to https - this is possible within the .htaccess. Much better, in my opinion, would be an alias on the apache (this usually should be done by your hoster).



          The difference:



          The htaccess redirect goes back to the user and then again to the server, which costs some time. The alias is - as far as I know - redirected on the server.



          if you want to force https, you can do it with the following entry.



          <IfModule mod_rewrite.c>
          RewriteEngine On
          RewriteCond %{SERVER_PORT} !^443
          RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L]
          </IfModule>





          share|improve this answer


























          • Tried with the procedure you describe, I get a blank start page with the error "Can't establish a database connection" - something along those lines, written in a large black font (generated by WP, not by the server). Regarding the https, I left that in the htaccess just out of precaution, in case the SSL validity ends (and I guess I'll be moving to another server pretty soon, with not being able to immediately transfer the SSL).

            – V____
            Nov 24 '18 at 19:31













          • Isn't the current statement just checking if it is not https that it will forward to the same link with https, but if it is https (as probably properly configured by the host, I get https links even without that piece of code in the htaccess) it just skips any action on that matter?

            – V____
            Nov 24 '18 at 19:35











          • Did you reset the htaccess to the original one?

            – AnotherArt
            Nov 25 '18 at 8:46











          • If you mean the WPs htaccess, it was untouched from the start, I only made changes in the root's htaccess (my custom htaccess, everything in the folders works fine even without it)

            – V____
            Nov 25 '18 at 13:51











          • I would remove any htaccess.

            – AnotherArt
            Nov 25 '18 at 15:04
















          0














          When I have WP installed within a subfolder, I just goto Settings => General and change the Website URL by removing the subfolder.



          Afterwards I move the file index.php one folder level up and in your case, would change it to:



           require( dirname( __FILE__ ) . '/frontstage/wp-blog-header.php' );


          Does this solve your problem?



          Find a detailed description how to move WP to a subdirectory on this site - You can find a detailed description about putting Wordpress in a subdirectory on the following website https://codex.wordpress.org/Giving_WordPress_Its_Own_Directory



          Regarding a redirection from http to https - this is possible within the .htaccess. Much better, in my opinion, would be an alias on the apache (this usually should be done by your hoster).



          The difference:



          The htaccess redirect goes back to the user and then again to the server, which costs some time. The alias is - as far as I know - redirected on the server.



          if you want to force https, you can do it with the following entry.



          <IfModule mod_rewrite.c>
          RewriteEngine On
          RewriteCond %{SERVER_PORT} !^443
          RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L]
          </IfModule>





          share|improve this answer


























          • Tried with the procedure you describe, I get a blank start page with the error "Can't establish a database connection" - something along those lines, written in a large black font (generated by WP, not by the server). Regarding the https, I left that in the htaccess just out of precaution, in case the SSL validity ends (and I guess I'll be moving to another server pretty soon, with not being able to immediately transfer the SSL).

            – V____
            Nov 24 '18 at 19:31













          • Isn't the current statement just checking if it is not https that it will forward to the same link with https, but if it is https (as probably properly configured by the host, I get https links even without that piece of code in the htaccess) it just skips any action on that matter?

            – V____
            Nov 24 '18 at 19:35











          • Did you reset the htaccess to the original one?

            – AnotherArt
            Nov 25 '18 at 8:46











          • If you mean the WPs htaccess, it was untouched from the start, I only made changes in the root's htaccess (my custom htaccess, everything in the folders works fine even without it)

            – V____
            Nov 25 '18 at 13:51











          • I would remove any htaccess.

            – AnotherArt
            Nov 25 '18 at 15:04














          0












          0








          0







          When I have WP installed within a subfolder, I just goto Settings => General and change the Website URL by removing the subfolder.



          Afterwards I move the file index.php one folder level up and in your case, would change it to:



           require( dirname( __FILE__ ) . '/frontstage/wp-blog-header.php' );


          Does this solve your problem?



          Find a detailed description how to move WP to a subdirectory on this site - You can find a detailed description about putting Wordpress in a subdirectory on the following website https://codex.wordpress.org/Giving_WordPress_Its_Own_Directory



          Regarding a redirection from http to https - this is possible within the .htaccess. Much better, in my opinion, would be an alias on the apache (this usually should be done by your hoster).



          The difference:



          The htaccess redirect goes back to the user and then again to the server, which costs some time. The alias is - as far as I know - redirected on the server.



          if you want to force https, you can do it with the following entry.



          <IfModule mod_rewrite.c>
          RewriteEngine On
          RewriteCond %{SERVER_PORT} !^443
          RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L]
          </IfModule>





          share|improve this answer















          When I have WP installed within a subfolder, I just goto Settings => General and change the Website URL by removing the subfolder.



          Afterwards I move the file index.php one folder level up and in your case, would change it to:



           require( dirname( __FILE__ ) . '/frontstage/wp-blog-header.php' );


          Does this solve your problem?



          Find a detailed description how to move WP to a subdirectory on this site - You can find a detailed description about putting Wordpress in a subdirectory on the following website https://codex.wordpress.org/Giving_WordPress_Its_Own_Directory



          Regarding a redirection from http to https - this is possible within the .htaccess. Much better, in my opinion, would be an alias on the apache (this usually should be done by your hoster).



          The difference:



          The htaccess redirect goes back to the user and then again to the server, which costs some time. The alias is - as far as I know - redirected on the server.



          if you want to force https, you can do it with the following entry.



          <IfModule mod_rewrite.c>
          RewriteEngine On
          RewriteCond %{SERVER_PORT} !^443
          RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L]
          </IfModule>






          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Nov 25 '18 at 15:13

























          answered Nov 24 '18 at 15:17









          AnotherArtAnotherArt

          33




          33













          • Tried with the procedure you describe, I get a blank start page with the error "Can't establish a database connection" - something along those lines, written in a large black font (generated by WP, not by the server). Regarding the https, I left that in the htaccess just out of precaution, in case the SSL validity ends (and I guess I'll be moving to another server pretty soon, with not being able to immediately transfer the SSL).

            – V____
            Nov 24 '18 at 19:31













          • Isn't the current statement just checking if it is not https that it will forward to the same link with https, but if it is https (as probably properly configured by the host, I get https links even without that piece of code in the htaccess) it just skips any action on that matter?

            – V____
            Nov 24 '18 at 19:35











          • Did you reset the htaccess to the original one?

            – AnotherArt
            Nov 25 '18 at 8:46











          • If you mean the WPs htaccess, it was untouched from the start, I only made changes in the root's htaccess (my custom htaccess, everything in the folders works fine even without it)

            – V____
            Nov 25 '18 at 13:51











          • I would remove any htaccess.

            – AnotherArt
            Nov 25 '18 at 15:04



















          • Tried with the procedure you describe, I get a blank start page with the error "Can't establish a database connection" - something along those lines, written in a large black font (generated by WP, not by the server). Regarding the https, I left that in the htaccess just out of precaution, in case the SSL validity ends (and I guess I'll be moving to another server pretty soon, with not being able to immediately transfer the SSL).

            – V____
            Nov 24 '18 at 19:31













          • Isn't the current statement just checking if it is not https that it will forward to the same link with https, but if it is https (as probably properly configured by the host, I get https links even without that piece of code in the htaccess) it just skips any action on that matter?

            – V____
            Nov 24 '18 at 19:35











          • Did you reset the htaccess to the original one?

            – AnotherArt
            Nov 25 '18 at 8:46











          • If you mean the WPs htaccess, it was untouched from the start, I only made changes in the root's htaccess (my custom htaccess, everything in the folders works fine even without it)

            – V____
            Nov 25 '18 at 13:51











          • I would remove any htaccess.

            – AnotherArt
            Nov 25 '18 at 15:04

















          Tried with the procedure you describe, I get a blank start page with the error "Can't establish a database connection" - something along those lines, written in a large black font (generated by WP, not by the server). Regarding the https, I left that in the htaccess just out of precaution, in case the SSL validity ends (and I guess I'll be moving to another server pretty soon, with not being able to immediately transfer the SSL).

          – V____
          Nov 24 '18 at 19:31







          Tried with the procedure you describe, I get a blank start page with the error "Can't establish a database connection" - something along those lines, written in a large black font (generated by WP, not by the server). Regarding the https, I left that in the htaccess just out of precaution, in case the SSL validity ends (and I guess I'll be moving to another server pretty soon, with not being able to immediately transfer the SSL).

          – V____
          Nov 24 '18 at 19:31















          Isn't the current statement just checking if it is not https that it will forward to the same link with https, but if it is https (as probably properly configured by the host, I get https links even without that piece of code in the htaccess) it just skips any action on that matter?

          – V____
          Nov 24 '18 at 19:35





          Isn't the current statement just checking if it is not https that it will forward to the same link with https, but if it is https (as probably properly configured by the host, I get https links even without that piece of code in the htaccess) it just skips any action on that matter?

          – V____
          Nov 24 '18 at 19:35













          Did you reset the htaccess to the original one?

          – AnotherArt
          Nov 25 '18 at 8:46





          Did you reset the htaccess to the original one?

          – AnotherArt
          Nov 25 '18 at 8:46













          If you mean the WPs htaccess, it was untouched from the start, I only made changes in the root's htaccess (my custom htaccess, everything in the folders works fine even without it)

          – V____
          Nov 25 '18 at 13:51





          If you mean the WPs htaccess, it was untouched from the start, I only made changes in the root's htaccess (my custom htaccess, everything in the folders works fine even without it)

          – V____
          Nov 25 '18 at 13:51













          I would remove any htaccess.

          – AnotherArt
          Nov 25 '18 at 15:04





          I would remove any htaccess.

          – AnotherArt
          Nov 25 '18 at 15:04


















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53457447%2fmultisite-wordpress-ssl-and-htaccess-to-use-the-subfolder-as-a-root%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Contact image not getting when fetch all contact list from iPhone by CNContact

          count number of partitions of a set with n elements into k subsets

          A CLEAN and SIMPLE way to add appendices to Table of Contents and bookmarks