Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Hi @bardic,
Let’s start going over the possibilities one by one.
/var/www/wordpress-multisite.
To do so, go to /var/www/ and executels -ld
It should show you both your site1 and wordpress-multisite folders. Are they using the proper owernship and permissions?
When you try and open your website, what do you see, what error?
Load site2.com into your browser while at the same time following your Apache error_log
tail -f /var/log/apache2/error_log
What does it say there, are they indications of errors?
Regards, KFSys
Hi,
The VirtualHost (vhost) blocks, you have already shared with us, do not catch requests for site3.com, thus, Apache uses first vhost block available, for site1.com in that case.
Let’s look at your wordpress-multisite.conf:
@bardic wrote//wordpress-multisite.conf
<VirtualHost *:80>
ServerAdmin webmaster@localhost
ServerName site2.com
ServerAlias *.site2.com
DocumentRoot /var/www/wordpress-multisite
ErrorLog ${APACHE_LOG_DIR}/error.log
CustomLog ${APACHE_LOG_DIR}/access.log combined
RewriteEngine on
RewriteCond %{SERVER_NAME} =site2.com [OR]
RewriteCond %{SERVER_NAME} =www.site2.com [OR]
RewriteCond %{SERVER_NAME} =site3.com [OR]
RewriteCond %{SERVER_NAME} =www.site3.com
RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent]
</VirtualHost>
This block is just for *.site2.com. Although, you extend your vhost configuration with site3.conf, there may still be something to do with your vhost blocks for SSL/TSL traffic on port 443. What I can suggest is to take a look at them.