Change Wordpress installation to Multisite

sancha_f 2019-07-12 08:00:34 UTC #1

Keywords: WordPress - Google Cloud Platform - How to - Other
Description:
Hi! Did follow one of the how to's, but ran into problem where I experienced login redirect for the main site and couldn't login, so replaced files in filezilla with the origial ones and now have the regular one site installation. I still would like to turn it into multisite, so what are the right steps to do it without having problems?

Thank you.

jota 2019-07-12 09:01:44 UTC #2

Hi @sancha_f,

thank you for using Bitnami. This other post in this community forum explains how to change WordPress from single site to multi site, did you follow it?

https://community.bitnami.com/t/how-can-i-enable-wordpress-multisite/47708/2?u=jota

Happy to help!

Was my answer helpful? Click on

sancha_f 2019-07-15 09:42:57 UTC #3

Hello @jota!

Thank you very much for your time and info!

Yes, I followed this article and everything seems fine now.
However when trying to access the subdomain, it shows ERR_TOO_MANY_REDIRECTS and no SSL. How to fix this?

Thank you!

The code from bitnami tool:

47b21e66-6071-84ca-bd37-7b4d91035f1f

alejandror 2019-07-15 10:36:01 UTC #4

Hi @sancha_f,

I just checked accessing the URL of your site and it looks correct for me: it redirected me from http://yourdomain.com to https://www.yourdomain.com, no redirect loop.

Is it possible that you have applied any change since you wrote your message that may have fixed it? Or maybe your browser is somehow caching the reply? Could you check if using a different browser or computer you also get the same issue?

sancha_f 2019-07-15 12:51:10 UTC #5

Hi @alejandror!

Than kyou for your message!

This redirect loop is happening for the subdomain I made. It's - sandbox.domain.com

How to fix it? Thank you.

alejandror 2019-07-16 10:41:18 UTC #6

Hi @sancha_f,

Thanks for clarifying it. I suspect that there is a conflict between the redirection to www. that you configured in Apache and the one that WordPress would be applying.

In your /opt/bitnami/apache2/conf/bitnami/bitnami.conf, I can see this:

  RewriteCond %{HTTP_HOST} !^www\. [NC]
  RewriteCond %{HTTP_HOST} !^(localhost|127.0.0.1)
  RewriteCond %{REQUEST_URI} !^/\.well-known
  RewriteRule ^(.*)$ http://www.%{HTTP_HOST}%{REQUEST_URI} [R=permanent,L]

This should not be applied for your subdomains. The simplest solution could be modifying this rule to only apply to your main domain:

  RewriteCond %{HTTP_HOST} ^domain.com [NC]
  RewriteCond %{REQUEST_URI} !^/\.well-known
  RewriteRule ^(.*)$ http://www.%{HTTP_HOST}%{REQUEST_URI} [R=permanent,L]

Then restart Apache.

Could you check if the above works for you?

sancha_f 2019-07-16 13:07:13 UTC #7

Hi @alejandror!

Thank yuo so much for pointing out where the issue was.

Here is my bitnmai support code- cb9a8a53-cd0c-6f97-3058-4fc9a5a01cf2

I now can open the login page for the subdomain, however can't login to the dashboard and the url sub.domain.com is still showing the redirects info. What elso could be wrong here? Thank you for your help!

alejandror 2019-07-17 10:32:45 UTC #8

Hi @sancha_f,

I'm sorry, my instructions were not totally accurate. I only provided the changes for the HTTP virtualhost, but you applied it to the HTTPS one. You would then need to fix the RewriteRule to use https://:

  RewriteRule ^(.*)$ https://www.%{HTTP_HOST}%{REQUEST_URI} [R=permanent,L]

In fact, you can remove that part from the HTTP virtualhost, since it would be always redirected to the HTTPS one, and applying the change to www. there.

With regards, to the login page issues, could you double-check that the URLs for the sites are correct? You should be able to see this on the main site's configuration, under the Sites section.

sancha_f 2019-07-17 12:55:42 UTC #9

Hi!

Thank you so much, it fixed everything. Now it looks great!
What should be done to add ssl to the subdomain?

Thank you!

alejandror 2019-07-18 09:52:57 UTC #10

Hi @sancha_f,

I'm glad it worked, thanks for letting us know!

You can make the Let's Encrypt certificate to also be valid for the subdomain.

If you used the Bitnami HTTPS Configuration Tool, this should be just as simple as adding the sub.domain.com to the list of domains when generating the certificate when prompted. This would revoke the current certificate and generate a new one that is valid for both main and subdomains.

Otherwise, if you are calling the lego tool manually, you would need to add an additional --domains=sub.domain.com.

system 2019-08-01 09:53:00 UTC #11

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.

Bitnami provides free all-in-one installers, virtual machines and cloud images for popular open source applications. Get them now!