Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

This has become an increasingly frustrating ordeal. I'm mostly a web developer, so forgive me if I am using improper terminology here.

I have a client that had purchased a domain at JustHost. We built him a website and have it on our own server space. Now, I'm mostly used to dealing with godaddy and it is simple enough to manage dns records and point the A record to our server IP, where Apache on our end deals with the domains via name-based virtual hosts.

But for some reason, in setting this up with JustHost, when attempting to go to the domain name, I either get a 502 or 503 error or "webpage does not exist". Now, I know that the basic functionality of the webpage must be working because I can access the the index etc straight through my servers www data (IE [server-ip]/website_folder).

I was on the phone with technical support for over three hours yesterday with justhost and the best I could get was "That's really weird..."

I've checked my logs and there doesn't seem to be anything coming through to my end. Does anybody have an idea of whats going on here? I would love for it to be a problem on my end, because justhost doesn't seem capable of helping further.

Any help is greatly appreciated, thanks.

I forgot to mention that we have several other sites up and running and completely accessible.

share|improve this question
Do you know of a proxy in your setup? What modules are you using? –  Somantra Jun 30 '12 at 14:40
All fine, but is this a dynamic or static website? –  Andrew Smith Jun 30 '12 at 14:49
it is a static website. @Somantra, using turnkey webstack. webmin and apache seem to be the only modules involved. I do not know of any proxies going on. –  Dave Jun 30 '12 at 15:04
I would try something like Firebug or Fiddler and watch the requests as you try to load the page. Also, I suspect that if the DNS records are correct, the traffic is it at least making it to your edge router. You may want to dig your URL to verify DNS. You probably will want to post your configs in the question too. You want to rule out the firewall as well. This post has some good troubleshooting steps: serverfault.com/questions/356442/nginx-to-proxy-to-apache –  Somantra Jun 30 '12 at 15:40
If you do dig yourdomain.com or nslookup yourdomain.com do you get the correct IP address back? –  Ladadadada Jul 2 '12 at 14:41

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.