Hello everyone, I finally deployed my Hestia - Debian 10 Buster, I’m very proud! I’m thinking of writing a how-to on the subject to help others.
I migrated a Wordpress MU (multisite); installation; main_domain/subsite, without too many problems, it works.
However, then I get a bit lost. Before, on my other VPS, I created an Apache virtualhost manually that I pointed to the Wordpress MU and the domain found its way to the sub-site.
Now with Hestia, I don’t know if I’m doing it right:
I created a Hestia user for the main domain ; democrasite.com
Then, I created a Hestia Site with a Wordpress MU installation with DNS zone creation.
At my registrar, I modified the DNS zone > Hestia_ip
Ok, it works
For the first sub-site; sandybeearts.com , I also created a Hestia User + a Hestia domain with creation of DNS zones as advised.
Then, at the registrar, I changed the DNS zone of sandybeearts.com (fields A > ip of my Hestia with the main domain)
Normally, the domain mapping should direct the request to the sub-site (democrasite.com/sandybeearts) but it doesn’t work.
Finally, I wonder if I should not have simply created a domain in Hestia for the sub-sites without a Hestia user, besides I don’t necessarily need it, the sub-sites don’t need ftp access. Maybe an email account…
My question is not necessarily directed to Multi-site Wordpress users, but rather to find a logic to solve the problem; as I said, on my old server, I only created Apache Vhosts that pointed to the main Wordpress, but here in Hestia, I don’t really understand if I’m doing it right.
Sorry for this a bit long post, and thanks for your lights.
Translated with www.DeepL.com/Translator (free version)