Related

Migrate Wordpress Website onto Apache Server Question Question
One droplet, 2 domains, but second domain loads to the first domain. What did I do wrong? Question Question

Question

Non-www shows empty directory listing. www. works fine.

Posted April 2, 2020 139 views
ApacheWordPressUbuntu 18.04

Hi,

I’m running Wordpress 5.4 on Ubuntu 18.04.1 and Apache/2.4.29.

When I go to example.com I see this empty directory listing.

But www.example.com works fine.

Also working fine is a 301 redirect I have in htaccess. As well as any redirect from example.com/page to www.example.com/page and HTTPS.

It’s only the root non-www. that does this.

Here is my htaccess but maybe this is something to do with a DNS record or even virtual hosts?

I’m not sure where to look next any help would be really appreciated.

Add a comment
By:
ellebovski
Add a comment

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.

×
1 answer
bobbyiliev April 2, 2020

Hi there @ellebovski,

It sounds like that you don’t have your non-www version added to your Apache virtual host.

You need to make sure that you have both the www and the non-www verion specified in your ServerName and ServerAlias lists in your Apache Vhost. To check that you can do the following:

  • Open your Apache Vhost with your favorite text editor:
sudo nano /etc/apache2/sites-enabled/your_domain.conf

  • Update your ServerName to match your non-www version

  • Add a ServerAlias to match your www version

  • Then run a config test:

  • sudo apachectl -t
  • If you get Syntax OK then restart Apache:
  • sudo systemctl restart apache2

Let me know if you have any questions.
Regards,
Bobby

Reply Report
  • ellebovski April 2, 2020

    Thanks a lot @bobbyiliev

    I may be mistaken but I think I have that in place already as per this conf file.

    I have three .conf files in that folder; the default one, the one I linked above for SSL and the original before SSL was added. Is that normal?

    Here is the first few lines of apache2ctl -S in case that helps…?

    root@example:/etc/apache2/sites-enabled# apache2ctl -S
VirtualHost configuration:
*:443                  example.com (/etc/apache2/sites-enabled/example.com-le-ssl.conf:2)
*:80                   is a NameVirtualHost
         default server example.com (/etc/apache2/sites-enabled/000-default.conf:1)
         port 80 namevhost example.com (/etc/apache2/sites-enabled/000-default.conf:1)
         port 80 namevhost example.com (/etc/apache2/sites-enabled/example.com.conf:1)
                 alias www.example.com
    Reply Report
    • bobbyiliev April 5, 2020

      Hi there @ellebovski,

      The config file that you’ve shared actually looks correct.

      However, the output of the apache2ctl -S command makes me think that you have a duplicate entry for your domain name in your default config file and the original config file for your example.com.

      What I could suggest is making sure that in your default config file you don’t have anything specified as the ServerName, you can comment that line by adding a # sign before the `ServerName, it would look like this:

              #ServerName www.example.com

      Then run a config test and restart Apache.

      Let me know how it goes!
      Regards,
      Bobby

      Reply Report
Submit an Answer

Related

Looking for something else?

Ask a new question Search for more help