Movable Type Knowledge Base: HTTP error: 500 read timeout When Sending Pings

Question

My activity log reports these errors when trying to send pings, for example: Ping 'http://rpc.weblogs.com/RPC2' failed: HTTP error: 500 Can't connect to rpc.weblogs.com:80 (connect: timeout).

Answer

If you find that, despite these errors, your ping has been successfully sent to the other site, this most likely means Movable Type simply did not receive back a non-error reply from the recipient server in enough time to conclude the ping was successful.

Try adjusting the PingTimeout directive in mt-config.cgi¹.

This setting defaults to 15, so experiment with a higher number. Note that this may increase the time it takes to save a new entry, because Movable Type will wait longer for a response from the recipient server.

If you continue to see these errors even after increasing the PingTimeout, then there may be a problem with the recipient server itself.

¹ In versions prior to 3.2, the configuration file is named mt.cfg.

Submit Feedback on This Article

Your comments on how we can improve this article are appreciated; but please do not use the feedback form to submit support requests or questions. We will not respond to or publish such queries submitted through this form. If you have a technical question or problem, visit Movable Type Support.

Name:

Email Address:

URL:

Remember personal info?

Comments: (you may use HTML tags for style)

Comments will be moderated and may appear on this page or be incorporated into future versions of this document. For full details, see our Terms of Service.