Error Id Bad_httpd_conf Vps
reviewsA2 Hosting reviewsGreenGeeks reviewsFat Cow.com reviews Compare Hosting Best For… WordPress PHP Linux ASP Joomla Windows Drupal Magento Hosting By Type Shared VPS Dedicated Cloud Reseller Search For Operating Systems Web Servers Applications Niche Hosting Hosting Coupons SiteGroundiPageBlueHosteHost.comArvixeInMotion HostingDreamhostGreenGeeksFat Cow.comHostPapa About DMCA Resources Blog Contact How to Fix a Dreamhost bad_httpd_conf Error Home » Tutorials » How to Fix a Dreamhost bad_httpd_conf Error New round here? Be sure to subscribe to our RSS feed. Got the dreaded bad_httpd_conf error on your DreamHost site? Don’t panic. This post explains what bad_httpd_conf means, and how to fix the problem. What Does bad_httpd_conf Look Like? You'll know you've got this problem if you see a message like this on your Dreamhost site: 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” What Causes bad_httpd_conf? Your gut reaction may be that your blog or CMS software is throwing the error, but bad_httpd_conf is actually a custom error message that only Dreamhost clients will encounter. That's why it's hard to fix. The error is produced when the IP address associated with your domain points to an Apache web server that’s not associated with it. The 3-Step Quick Fix For bad_httpd_conf Go to your Dreamhost web panel. Navigate to Domain > Manage Domains > Edit. Then click the Change Fully Hosted Settings Now! button. You don’t have to actually make any changes before you save. Just following these steps will rebuild the httpd_conf file for your website. Wait up to 10 minutes and check that the problem is fixed. The Static IP Fix For bad_httpd_conf Got a static IP? Delete it, then add it again in your web panel. Often, this is enough to remove the error. Note: Dreamhost will give you a refund and charge you again for the IP address. Don't worry: you'll break even. The Final Fix For Bad_httpd_conf Still having problems
804 Next » » getting error: error id: "bad_httpd_conf" Threaded Mode | Linear Mode getting error: error id: "bad_httpd_conf" 02-07-2003, 01:25 PM Post: #1 hipchick Dreamling Posts: 1 Joined: Feb 2003 getting error: error id: "bad_httpd_conf" I upgraded a parked domain that was being mirrored to a regular domain. Now when you go to the domain address the following message is displayed: Site Temporarily Unavailable We http://www.whoishostingthis.com/blog/2008/06/13/bad_httpd_conf/ apologize for the inconvenience. Please contact the webmaster/ tech support immediately to have them rectify this. error id: "bad_httpd_conf" What do I need to change or fix so that the index.html within the domain will show? 02-07-2003, 01:45 PM Post: #2 will Previous DH Staff Posts: 1,941 Joined: May 2001 getting http://forum.dreamhosters.com/troubleshooting/4412-getting-error-error-id-bad_httpd_conf.htm error: error id: "bad_httpd_conf" What's the domain? « Next Oldest | Next Newest » View a Printable Version Send this Thread to a Friend Subscribe to this thread Forum Jump: Please select one: -------------------- Private Messages User Control Panel Who's Online Search Forum Home DreamHost -- DreamHost Announcements -- Suggestions Customer Discussion -- General Troubleshooting -- Beginner's Forum -- Curious About DreamHost? -- VPS and Dedicated Servers -- DreamObjects -- DreamCompute -- DreamHost Rewards Web Development -- WordPress -- Web Applications and One-Click Installs -- Software Development -- Web Design Beta Testing Retired Forums -- Beta Testing -- Offtopic Discussion -- Multimedia -- E-Commerce -- Promotion -- DreamHost Apps Index | Dreamhost (Signup · Panel · Wiki) | Contact Us | Archive Mode | RSS Syndication DreamHost is a registered trademark of New Dream Network, LLC © 1997-2013 DreamHost, your dream web host! Powered By MyBB, © 2002-2010 MyBB Group.
you through why you may be seeing this error and how to resolve it. The root cause of the error The 'Site Not Found' error means the IP address your domain is using is not pointed to the https://help.dreamhost.com/hc/en-us/articles/215613517-Site-not-found correct IP. More technically, the 'Site Not Found' error means that the DNS records for your domain are resolving to the IP address of an Apache web server service that is not configured for your domain. When this happens, the Apache web server is designed to just show the first domain listed in its config file. To make sure that nobody's site ever accidentally shows a random site hosted on error id the same Apache service, DreamHost makes the first domain in all its config files show the same custom error page. There are a few reasons why your IP may not be correctly pointed to your web server IP which are explained below. Viewing your site’s IP address in your browser Due to the way that DreamHost configures Apache, unless you have purchased a Unique IP address for your domain, attempting to error id bad_httpd_conf view your site by entering the IP address in your browser automatically gives you the Site not found error. This is because you’re viewing the shared IP of your web server, not the IP of your site. If you absolutely need to view your site through an IP address, you must purchase a Unique IP. You can read more about Unique IPs here: Unique IP DNS changes Frequently this error appears due to a change in your IP address, which is commonly triggered by removing hosting for a domain and then setting up a MIRROR, REDIRECT, PARK, or CLOAK. While changes to the DreamHost DNS are nearly instantaneous, the new information doesn't reach other servers around the world until the other servers expire the old data that they are holding on to. This is referred to as DNS propagation. The reason why you get this error during this period of time is that the DNS information you are receiving to your local computer is outdated, and the Apache instance that you are being incorrectly sent to no longer has any record of your site. Depending on your location, it can take up to several hours for DNS changes to propagate, so the best thing to do is leave your domain