Support » Plugin: Content Syndication Toolkit » transport error – could not open socket

  • Hi there.

    I trying this plugin, it works well if I pulled the content from my content server, but the content server doesn’t pushed the post. I checked the log on the reader client, and it says: transport error – could not open socket.

    I can get from my content server the xmlrpc.php, it says: “XML-RPC server accepts POST requests only.”
    I saved the post on my content server but there is no a log.

    Could you help me?

    Thanks in advance.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author ben.moody

    (@benmoody)

    Hi

    Does this happen everytime?

    The reason I ask is that when a post is published on the Master site it pings all the reader sites to let them know there is a new post to download, and the the reader sites download the posts.

    There can be times when some of the reader sites are on slow servers and the inital ping request on post save doesn’t make it to all the reader sites as they are too slow to respond in time.

    I’m working on an update to the reader plugin to schedule regular checks for new content to get around this issue

    I’m having the same issue. I can only pull posts from the master site. When I publish nothing is pushed to the client site. I have both plugins installed and can only assume that the client site works properly because it can manually pull content. So the issue must be on the master site?

    Interestingly enough, when I delete a post from the master site, I see this in my error log:
    [21-Feb-2017 18:26:38 UTC] PHP Warning: Invalid argument supplied for foreach() in /home/website/public_html/assets/plugins/push-syndication/push-syndication.php on line 887

    [21-Feb-2017 18:26:43 UTC] PHP Warning: Invalid argument supplied for foreach() in /home/website/public_html/assets/plugins/push-syndication/push-syndication.php on line 887

    • This reply was modified 4 years, 2 months ago by T.McGuire. Reason: hide domain
Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘transport error – could not open socket’ is closed to new replies.