The MU forums have moved to

XMLRPC 32300:transport error - HTTP status code was not 200 (3 posts)

  1. newscloud
    Posted 16 years ago #

    When I try to use XMLRPC, I'm starting to repeatedly run into
    32300:transport error - HTTP status code was not 200

    and I have no idea why.

    While the WordPress forums report that various plugins have caused this in the past, I deactivated all my plugins but still get the same error.

    Does anyone know how to fix this and what the problem might be?

    I am trying to add a user via xmlrpc - and the user is created and the blog is created, it fails before creating new tables for the user's blogs. This worked great in the past ... and I can't figure out why it's now not working.

  2. newscloud
    Posted 16 years ago #

    Turned out I was out of memory

    PHP Fatal error: Allowed memory size of 8388608 bytes exhausted

    Changing php.ini to allow 10M seems to fix it.

    But I can't help but wonder if there is a memory leak in WordPress or xmlrpc ... since this worked most of yesterday then stopped working.

    Does anyone have any thoughts on this?

  3. SteveAtty
    Posted 16 years ago #

    Step 2 in the PHP section of the readme

    2. If your PHP is compiled with memory limit checks, the default is 8MB which is much too small. You should increase this to at least 32MB or 64MB to avoid PHP out of memory errors. Look for "memory_limit" in your php.ini file.

    I've set mine a lot higher.

About this Topic

  • Started 16 years ago by newscloud
  • Latest reply from SteveAtty