atsballen

@erania-pinnera Thanks for the response. I’m hosting this instance myself and don’t believe I have any blocks on that file. Are you having trouble accessing it? It’s also worth nothing that the Jetpack plugin is disable at the moment because of the crashing. The WordPress instance has 128MB of memory which should be enough for a site this lightweight. My other sites are all much more resource intensive than this one yet don’t crash. Jetpack also seems to be eating up said memory very fast.

EDIT: After doing some reading on xmlrpc.php, it seems like an archaic method of interfacing with WordPress and most resources recommend it be disabled. The documentation you linked states that xmlrpc.php support is required, and while I don’t know enough about the inner-workings of WordPress to decide whether or not enabling xmlrpc.php is a wise decision, I’m also skeptical that it’s causing memory leaks. I’d imagine that in the event a required setting wasn’t enable, Jetpack would throw me a warning/error instead of crashing my apache instance.

• This reply was modified 3 years, 11 months ago by atsballen.