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.
Someone else recently had a similar problem. I think the issue is that since site2 does not have ssl configured in the site.conf file, it automatically defaults to site1.
A possible theoretically-it-should-work around is to add ssl to your site2.conf file, and then add something to your site2 .htaccess file to redirect everything to non-ssl.
From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.