1

Any help would be greatly appreciated. I am stuck with this issue for a long time now.

Now here is the thing. I have on my ubuntu 16.04 server two vhosts, one for Nextcloud (https://mydomain.com/owncloud/) that works perfectly and one for my wordpress (https://mydomain.com/) that does not work. Each time I enter https://mydomain.com it returns https://mydomain.com:16501 and my web browser safari says it cannot connect to the server mydomain.com.

My wordpress used to work and I have no idea where this 16501 comes from.

I have basicaly three vhosts in sites-enabled...

000.default.conf

<VirtualHost *:80>
    ServerAdmin webmaster@localhost
    DocumentRoot /var/www/html

    ErrorLog ${APACHE_LOG_DIR}/error.log
    CustomLog ${APACHE_LOG_DIR}/access.log combined

RewriteEngine on
RewriteCond %{SERVER_NAME} =mydomain.com
RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent]
</VirtualHost>

nextcloud.conf

<IfModule mod_ssl.c>
   <VirtualHost _default_:443>

     ServerAdmin mail@mymail.com
     ServerName mydomain.com
     DocumentRoot /var/www/html

Alias /nextcloud "/var/www/owncloud/"

<Directory /var/www/owncloud/>
  Options +FollowSymlinks
  AllowOverride All

 <IfModule mod_dav.c>
  Dav off
 </IfModule>

 SetEnv HOME /var/www/owncloud
 SetEnv HTTP_HOME /var/www/owncloud

</Directory>

    ErrorLog ${APACHE_LOG_DIR}/error.log
    CustomLog ${APACHE_LOG_DIR}/access.log combined 

     <IfModule mod_headers.c>
          Header always set Strict-Transport-Security "max-age=15768000; preload"
     </IfModule>

SSLCertificateFile /etc/letsencrypt/live/mydomain.com/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/mydomain.com/privkey.pem
Include /etc/letsencrypt/options-ssl-apache.conf


   </VirtualHost>
</IfModule>

wordpress.conf

<IfModule mod_ssl.c>
   <VirtualHost _default_:443>

     ServerAdmin mail@mymail.com
     ServerName mydomain.com
     ServerAlias www.mydomain.com
     DocumentRoot /var/www/html

<Directory /var/www/html/>
  AllowOverride All

</Directory>

    ErrorLog ${APACHE_LOG_DIR}/error.log
    CustomLog ${APACHE_LOG_DIR}/access.log combined 

SSLCertificateFile /etc/letsencrypt/live/mydomain.com/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/mydomain.com/privkey.pem
Include /etc/letsencrypt/options-ssl-apache.conf


   </VirtualHost>
</IfModule>

Thanks for your help!

Edwin
  • 129

1 Answers1

0

You are have two VirtualHost's with the same ServerName directive, so Apache can't threat this and uses only the first one. The first one is those defined in the file nextcloud.conf, because the letter 'n' is located before 'w' in the alphabet.

One way to solve this is to combine the content of nextcloud.conf and wordpress.conf and create one VirtualHost - you can name the new configuration file mydomain.com.conf, for example:

<IfModule mod_ssl.c>
    <VirtualHost _default_:443>

        ServerAdmin mail@mymail.com
        ServerName mydomain.com      # Note along with mydomain.com your cert. file must
        ServerAlias www.mydomain.com # contain www.mydomain.com to use ServerAlias here

        DocumentRoot /var/www/html    
        <Directory /var/www/html/>
            AllowOverride All
        </Directory>

        Alias /nextcloud "/var/www/owncloud/"
        <Directory /var/www/owncloud/>

            Options +FollowSymlinks
            AllowOverride All

            <IfModule mod_dav.c>
                 Dav off
            </IfModule>

            SetEnv HOME /var/www/owncloud
            SetEnv HTTP_HOME /var/www/owncloud

            <IfModule mod_headers.c>
                Header always set Strict-Transport-Security "max-age=15768000; preload"
            </IfModule>

        </Directory>

        ErrorLog ${APACHE_LOG_DIR}/error.log
        CustomLog ${APACHE_LOG_DIR}/access.log combined 

        SSLCertificateFile /etc/letsencrypt/live/mydomain.com/fullchain.pem
        SSLCertificateKeyFile /etc/letsencrypt/live/mydomain.com/privkey.pem
        Include /etc/letsencrypt/options-ssl-apache.conf

    </VirtualHost>
</IfModule>

In this case you should be able to access the WordPress installation at https://mydomain.com and the ownCloud installation at https://mydomain.com/nextcloud. Don't forget to a2dissite the old conf files, a2ensite the new one and restart Apache.

Another way is to use different domain names (FQDN) for the booth VirtualHosts. For example mydomain.com for WordPress and www.mydomain.com (or cloud.mydomain.com) for ownCloud. In this case you do not need to use the directive Alias /nextcloud "/var/www/owncloud/" instead that you can use DocumentRoot /var/www/owncloud/, so you will be able to access your ownCloud directly at https://www.mydomain.com (respectively at https://clould.mydomain.com).

In addition: within the Apaches documentation you will be advised to do not use the rewrite engine when you can use more simple directives. Within your HTTP host definition you can use the Redirect directive as it is shown here. The only limitation of this approach is that you must create HTTP VirtualHost per FQDN.

pa4080
  • 30,621