By Steve Lack
I have set up a virtual host for a site where the directory only contains an index.html. The virtual host file in the sites-available directory looks exactly the same as other sites on the same droplet. I have set up A records for both @ and www. My client has pointed to the site using a Cname from their registrar account. It worked until I moved to a new Droplet by installed a snapshot image. When my client changed Cname to the new IP the site started redirecting to the root of my server instead of accessing their directory in the /var/www directory. The logs show a 403 when I try to hit the site. I can access the site using the droplets IP so I suspect it’s a DNS issue rather than a permissions error but don’t really know where to start to trouble shoot this.
The Virtual Host file looks like this:
<VirtualHost *:80> ServerAdmin webmaster@localhost ServerName sitename.com ServerAlias www.sitename.com
DocumentRoot /var/www/sitedirectory
<Directory />
Options FollowSymLinks
AllowOverride all
</Directory>
<Directory /var/www/>
Options Indexes FollowSymLinks MultiViews
AllowOverride all
Order allow,deny
allow from all
</Directory>
ScriptAlias /cgi-bin/ /usr/lib/cgi-bin/
<Directory "/usr/lib/cgi-bin">
AllowOverride all
Options +ExecCGI -MultiViews +SymLinksIfOwnerMatch
Order allow,deny
Allow from all
</Directory>
ErrorLog ${APACHE_LOG_DIR}/error.log
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
LogLevel warn
CustomLog ${APACHE_LOG_DIR}/access.log combined
Alias /doc/ "/usr/share/doc/"
<Directory "/usr/share/doc/">
Options Indexes MultiViews FollowSymLinks
AllowOverride all
Order deny,allow
Deny from all
Allow from 127.0.0.0/255.0.0.0 ::1/128
</Directory>
</VirtualHost>
The site directory is 755 and I even changed it to 777 to see if that helped, but it didn’t.
This exact set up works with other sites on this droplet. Could this be something to do with the Cname record? They are pointing to the IP of the server and an A record is entered for the domain in the DO DNS.
Here’s the DNS entry:
$TTL 1800 @ IN SOA NS1.GENLACKCLOUD.COM. hostmaster.sitename.com. ( 1386531108 ; last update: 2013-12-08 19:31:48 UTC 3600 ; refresh 900 ; retry 1209600 ; expire 1800 ; ttl ) IN NS NS1.GENLACKCLOUD.COM. NS NS2.GENLACKCLOUD.COM. NS NS3.GENLACKCLOUD.COM. @ IN A 162.243.245.207 www IN A 162.243.245.207
The Droplet is running Ubuntu 12.04
Thanks for any advice anyone may have!
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!
Thanks for your help Pablo! It turns out that the client is loading the page through an iframe on their own server and not redirecting to our droplet. So it was a setup issue at all.
<b>“The virtual host file in the sites-available directory looks exactly the same as other sites on the same droplet.”</b> <br> <br>Yea, but is the virtual host in the <code>/etc/apache2/sites-enabled/</code> directory? <br> <br>Also, don’t discount the possibility that it may simply be a DNS propagation issue. Changes to DNS records can take up to 48 hours to propagate through the Internet.
The yes it is in the /etc/apache2/sites-enabled directory and the change was made several days ago, so I don’t think it’s a propagation issue. When I do an nslookup I get this: <br> <br>Server: 8.8.8.8 <br>Address: 8.8.8.8#53 <br> <br>Non-authoritative answer: <br>Name: sitename.com <br>Address: 184.168.221.19 <br> <br>My client has their domain pointing to our DO droplet and when it hits the droplet, which is at genlack.co, it acts as if you went to genlack.co instead of the sitename.com site, so I guess it has something to do with the DO DNS entry but I can’t see what it could be. The A records for @ and www are correct.
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
Full documentation for every DigitalOcean product.
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
Stay up to date by signing up for DigitalOcean’s Infrastructure as a Newsletter.
New accounts only. By submitting your email you agree to our Privacy Policy
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.