getting error id: "bad_httpd_conf" after adding a new domain

fkroerank

New member
Joined
Apr 8, 2008
Messages
2
Hello,

I was able to set up 4 other domains today in direct admin, and they all worked fine, and I was able to view them as I would expect, but then when I went to set up http://j6.bz everything seemed to work fine until I went to try to view it and then I got this error

Site Temporarily Unavailable
We apologize for the inconvenience. Please contact the webmaster/ tech support immediately to have them rectify this.

error id: "bad_httpd_conf"

I contacted my host, and they said to ask here.

I tried deleting it and doing it again, and I tried setting up a different user account, and creating it that way and neither worked.. I got the same error.

any help?
 
It looks like the site is working fine now, what did you do to fix it?
 
I believe it fixed itself..
The only only other reasonable answer would be it didnt transfer to the servers as fast as the other sites did, and it could have still be pointing to dreamhost when it was there. I dont think it was a directadmin problem since it did work itself out, and the only thing I can find on it in google is pointed at dreamhost
 
DirectAdmin Forums

I was able to set up 4 other domains today in direct admin, and they all worked fine, and I was able to view them as I would expect, but then when I went to set up http://j6.bz everything seemed to work fine until I went to try to view it and then I got this error

Site Temporarily Unavailable
We apologize for the inconvenience. Please contact the webmaster/ tech support immediately to have them rectify this.

I contacted my host, and they said to ask here.

I tried deleting it and doing it again, and I tried setting up a different user account, and creating it that way and neither worked.. I got the same error.
 
You didn't give us much information to go with for checking.

j6.bz appears to use these nameservers:

ns1.johnthe3rd.com 66.79.183.66
ns2.johnthe3rd.com 66.79.165.212

but neither of these nameservers are returning the proper IP#s for j6.bz.
Code:
$ dig +short j6.bz
;; connection timed out; no servers could be reached
$
Are these your nameservers? If not, then you need to make some registrar changes.

if they are you need to check your server(s) to see if the nameservers are running, if they're responding to requests locally, and also to see if you've got some kind of firewall in place to keep them from responding to outside requests.

Jeff
 
I attempted to post this a little while ago, but it doesn't appear to have shown up for some reason. I can't find it in the forum, or under "my discussions", or when searching the entire site for "bad_httpd_conf" -- it seems to have disappeared into the ether. I'm hoping it will work this time. Quite possibly I did something wrong the first time around.
 
This response is to user daily jobs and to user fkroerank:

the error bad_httpd_conf is an error specific to the hosting company Dreamhost.

I don't think they use DirectPanel (they say they use their own control panel) and this error is NOT used by DirectAdmin. All google hits say it's a Dreamhost-specific problem.

You should contact them.

Jeff
 
hi,
I was able to set up 4 other domains today in direct admin, and they all worked fine, and I was able to view them as I would expect, but then when I went to set up http://j6.bz everything seemed to work fine until I went to try to view it and then I got this error

Site Temporarily Unavailable
We apologize for the inconvenience. Please contact the webmaster/ tech support immediately to have them rectify this.

error id: "bad_httpd_conf"

I contacted my host, and they said to ask here.

I tried deleting it and doing it again, and I tried setting up a different user account, and creating it that way and neither worked.. I got the same error.

any help?
 
That doesn't look like a DirectAdmin error to me. If you own your manage DirectAdmin based server then did you creae a custom suspension notice or any other custom error notices?

If you don't manage your own DirectAdmin based server, then the problem must be addressed by your hosting company.

Are you sure you've given us the correct domain name; when I try your domain I get:
Firefox can't find the server at j6.bz.
Jeff
 
Back
Top