>>>>> Steinar Bang <[email protected]>: > I have been using org2blog to maintain blogposts on wordpress.com for a > couple of years now.
> But on October 11 this year I suddenly started getting HTTP error code > 429 Too Many Requests on xmlrpc operations from org2blog to wordpress > https://github.com/org2blog/org2blog/issues/357 > The same thing has happened to a couple of other org2blog users > https://github.com/org2blog/org2blog/issues/354 > https://github.com/org2blog/org2blog/issues/355 > The short story here is that the restriction on xmlrpc operations have > appeared when sites have been moved to a new hosting. And my site was > moved on October 11, the day I first encountered the problem. The problem has now been fixed by having wordpress.com remove the request-burst blocking for my site: https://github.com/org2blog/org2blog/issues/357#issuecomment-6540945769 To fix it, what was needed: 1. Start chatting on https://wordpress.com/support/contact/ and explain your problem: i.e. org2blog getting 429 Too Many Request responses on xmlrpc 2. When the chatbot sends you to a real human (which to me happened very quickly) ask to have the request-burst blocking lifted on your site 3. You will need to switch to application password for org2blog: 1. in the wordpress dashboard for your site, select Users->All Users 2. click on the user you are using with org2blog 3. Scroll down until you get to "Application passwords" 4. Type a descriptive name in "New Application Password Name" and click on "Add Application Password" 5. Copy the generated password, remove the spaces from the password, and put it in for your site in ~/.netrc or ~/.authinfo or wherever you keep org2blog's auth info (the spaces must be removed, or else emacs will choke on parsing the auth info)
