11 {{ upvoteCount | shortNum }}
11 {{ upvoteCount | shortNum }}

"RSS Error: WP HTTP Error: couldn't connect to host" v3.3.1

by trigger571
8 replies
HI there,

First of all sorry if I posted this in the wrong Forum, but not quite sure where it should go. I also gave up trying to get an answer from the wordpress forums, where my posts go unanswered for several months.

I have this problem "RSS Error: WP HTTP Error: couldn't connect to host" across 14 wordpress installations on one host. No problems on other WP installations on other hosts (BlueHost and HostMonster). The problem is obviously with the host (iWebHost) - BUT .

iWebHost, have been looking into this issue for some time now. They have enabled curl, changed the memory limit to 256mb verified the error
log and even worked with the suggested fix found on forums and the problem is still there. Now they are saying that maybe wordpress has actually blocked my site IP though I find no reason for this to be true as the problems were there as soon as the first site was up and running. The server is a dedicated host with a dedicated IP.

Any help to fix this would be greatly appreciated.
Thanks
  • Profile picture of the author BlueLayerHost
    Did you try this? rss error: WP HTTP Error: couldn’t connect to host – Techs11

    Or it sounds like you may need to find a new host?
    Signature
    BlueLayerHost - Shared + Managed VPS Hosting
    BlueLayerMedia - Web Development
    WPMalware - Resource for WordPress Seurity + Exploits
    {{ DiscussionBoard.errors[5992603].message }}
  • Profile picture of the author Kingfish85
    If your host can't figure this out, it's time to move. Seems to me something is blocking it. It probably isn't, but is this on a Windows server?
    Signature

    |~| VeeroTech Hosting - sales @ veerotech.net
    |~| High Performance CloudLinux & LiteSpeed Powered Web Hosting
    |~| cPanel & WHM - Softaculous - Website Builder - R1Soft - SpamExperts
    |~| Visit us @veerotech Facebook - Twitter - LinkedIn

    {{ DiscussionBoard.errors[5992655].message }}
    • Profile picture of the author trigger571
      Originally Posted by Kingfish85 View Post

      It probably isn't, but is this on a Windows server?
      Nope it's a Linux server.

      I don't particularly want to move. This host is the best I found in my 10 years on-line. Besides, I have 16 sites on this server, 4 of which are very high traffic. Pulling these for down for the 48 hour DNS propagation is not an option.

      @BlueLayerHost: Thanks for that. I had already seen that post, but I do not think it applies to my case. For starters, each site has its own separate DB. Plus on some, this was a new installation.

      Seriously people, I am lost for words as to what this could be. Anyone else with any ideas?
      {{ DiscussionBoard.errors[5995095].message }}
      • Profile picture of the author mojojuju
        Originally Posted by trigger571 View Post

        Nope it's a Linux server.

        I don't particularly want to move. This host is the best I found in my 10 years on-line. Besides, I have 16 sites on this server, 4 of which are very high traffic. Pulling these for down for the 48 hour DNS propagation is not an option.
        Moving your sites to a different server should not require your sites to be down for 48 hours. You can do it without any downtime if you do it properly.
        Signature

        :)

        {{ DiscussionBoard.errors[5995745].message }}
        • Profile picture of the author trigger571
          Originally Posted by mojojuju View Post

          Moving your sites to a different server should not require your sites to be down for 48 hours. You can do it without any downtime if you do it properly.
          Really? I will look into that. I always thought that to move server one needed to change DNS which means sites would be down. There goes to prove my ignorance of DNS. Thanks a bunch for that.
          {{ DiscussionBoard.errors[5998713].message }}
  • Profile picture of the author Kingfish85
    Did you get this straightened out yet?
    Signature

    |~| VeeroTech Hosting - sales @ veerotech.net
    |~| High Performance CloudLinux & LiteSpeed Powered Web Hosting
    |~| cPanel & WHM - Softaculous - Website Builder - R1Soft - SpamExperts
    |~| Visit us @veerotech Facebook - Twitter - LinkedIn

    {{ DiscussionBoard.errors[6009854].message }}
  • Profile picture of the author Kingfish85
    Is fsockopen enabled? Can you turn on php error reporting and try it again. then post the entire error message here? or PM me...?
    Signature

    |~| VeeroTech Hosting - sales @ veerotech.net
    |~| High Performance CloudLinux & LiteSpeed Powered Web Hosting
    |~| cPanel & WHM - Softaculous - Website Builder - R1Soft - SpamExperts
    |~| Visit us @veerotech Facebook - Twitter - LinkedIn

    {{ DiscussionBoard.errors[6009892].message }}
  • Profile picture of the author Earnie Boyd
    The DNS propagation may take up to 48 hours, you are correct about that. If you have an interactive site where your members are allowed to add content then you would need to put the old IP in static no new content mode and let the users know they would need to come back when the site is back online. You would add a notice in a template block to the old IP site that would not appear in the new IP site.

    Have you contacted the site you're trying to connect to with the RSS request? RSS is usually fed on port 80 so it seems unlikely to be that. Have you tried using lynx at a ssh terminal for the RSS URI to see if you get the data? Are you trying to use a secure connection from your host server to the remote server and that is failing? Just some things to look at.
    Signature
    Earnie Boyd
    {{ DiscussionBoard.errors[6013729].message }}

Trending Topics