Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I running CentOS release 5.8 (Final) for my WordPress blog ( I have a backup plugin BackupBuddy, and it says:

HTTP Loopback Connections are not enabled on this server

After some tries on Google, I found some solutions, but none work. The best answer I think is changing the /etc/hosts file, and I already did that: localhost localhost6 localhost.localdomain localhost6.localdomain6
::1       localhost localhost6 localhost.localdomain localhost6.localdomain6

But the warning from the plugin still appears.

I also tested in command line:

telnet 0 80

All work.

I don't know what's right now. My blog is running slow, and I guess the HTTP loopback connection is the main problem. Any help is appreciated! Thanks!


More information about the web server (Apache)

Listen 80


apachectl -S
VirtualHost configuration:
wildcard NameVirtualHosts and _default_ servers:
*:80                   is a NameVirtualHost
         default server (/usr/local/apache/conf/extra/httpd-vhosts.conf:2)
         port 80 namevhost (/usr/local/apache/conf/extra/httpd-vhosts.conf:2)
         port 80 namevhost (/usr/local/apache/conf/extra/httpd-vhosts.conf:9)
Syntax OK

(I host some other sites on the server as well, default is

share|improve this question
Did you tried looking at… – atolani Aug 24 '12 at 17:02
I tried, no luck. That solution just enables the alternative WP cronjob, which doesn't solve the problem with server. I'm looking for a real solution. – Rilwis Aug 24 '12 at 17:48
Just edit my question with added information. – Rilwis Aug 24 '12 at 17:53
This question would probably do better on our dedicated Wordpress Site -- I can move it there if you would like, but it doesn't seem to be on-topic for Server Fault... – voretaq7 Aug 24 '12 at 18:17
@voretaq7 I don't think so. I'm an active member at WPSE. And I believe that this problem is related with server than WordPress. – Rilwis Aug 24 '12 at 19:04

The solution is to instruct the server to answer with the right content for the requests directed towards In order to do this you need a VirtualHost directive linked to this loopback address :

DocumentRoot /var/www/yourdomain
ErrorLog  logs/webserv/xgraphic_error_log
CustomLog logs/access_log combined

You will need an entry of this type for each domain you are hosting on the server, even though you might already have an entry for your domain.

Cosmin Ioachim Damian.

share|improve this answer

Along the lines' of Cosmin's answer, but not quite, I had this issue because my vhost entry was not completely configured. A lot of people follow simple local dev vhost tutorials, which show you just the basics. In fact, you need a more-complete vhost entry, including rules, which solves this without any hosts files voodoo (beyond

File: /etc/hosts

# Localhost  localhost
::1        localhost

# Your custom, local dev site

File: /path/to/apache2/extras/httpd-vhosts.conf:

<VirtualHost *:80>
DocumentRoot "/Users/examplename/Sites/"
<Directory "/Users/examplename/Sites/">
    Options Indexes FollowSymLinks Includes execCGI
    AllowOverride None
    Order Allow,Deny
    Allow From All

Now, granted, there is more in the Directory than you need. But it works.

At least for me.

share|improve this answer
Atomox, I hope you don't mind that I removed your mom from this post. – Daniel Jan 28 at 7:18
@Daniel If you are going to change domain names, then use which is reserved for use in examples. And see this answer. – kasperd Jan 28 at 8:07

Your Answer


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

Not the answer you're looking for? Browse other questions tagged or ask your own question.