COmountainClimber
By:
COmountainClimber

Why am i getting "Welcome to nginx! further configuration is required" when I type www.jamspaces.com instead of just jamspaces.com

November 7, 2015 4.4k views
Nginx Deployment

So i am hosting two seperate domains on the same droplet by utlizing nginx and getting this error. Cant seem to figure out why as I have my other site set up identically and both cruxcalculator.com and www.cruxcalculator.com work fine.

When I run whois www.jamspaces.com I get absolutely no results. Totally confused if someone could explain what is going on it would be much appreciated!

2 comments
  • nickponte November 7, 2015

    when you whois jamspaces.com are you getting the digital ocean name servers?
    This would look like :
    Name Server: NS1.DIGITALOCEAN.COM
    Name Server: NS2.DIGITALOCEAN.COM
    Name Server: NS3.DIGITALOCEAN.COM

    I think your having an issue with the proper name servers not being set up, or you don't have the correct Cname or A record set up in your Digital ocean networking dashboard for that specific domain.

    Im not an expert but I had that issue and worked through these few steps

  • COmountainClimber November 7, 2015

    so when I run whois jamspaces.com I get my DO name servers. when I run whois www.jamspaces.com I get "no match" super confusing to me...

    ZONE FILE:

    $ORIGIN jamspaces.com.
$TTL 1800
jamspaces.com. IN SOA ns1.digitalocean.com. hostmaster.jamspaces.com. 1446855892 10800 3600 604800 1800
jamspaces.com. 1800 IN NS ns1.digitalocean.com.
jamspaces.com. 1800 IN NS ns2.digitalocean.com.
jamspaces.com. 1800 IN NS ns3.digitalocean.com.
jamspaces.com. 1800 IN A 104.131.121.222
www.jamspaces.com. 1800 IN CNAME jamspaces.com.
Log In to Comment
3 Answers
lulzsecd November 7, 2015

Edit your domain conf
Server www.crazytut.com crazytut.com;

Reply
COmountainClimber November 7, 2015

this did not seem to fix the problem :(

Reply
COmountainClimber November 7, 2015

server {
listen 80;

server_name www.jamspaces.com jamspaces.com;

location / {
    proxy_pass http://localhost:8080;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection 'upgrade';
    proxy_set_header Host $host;
    proxy_cache_bypass $http_upgrade;
}

}

Reply
Have another answer? Share your knowledge.

Related Questions