Forums

Request failed: forbidden (403)

  1. If we try to add a blog on the app we get: "Could not login Request failed: forbidden (403)"

    We have used wordpress and the app for many years and this has never been visible before.
    We have checked that our web host has not disabled xml-files. The xmlrpc.php is place in the root. Wordpress is updated.

    We have tried to disable all plugins and we know our web host don't block xml... But we still can't use the app.
    We got this logg from the tries:

    16/08/17 16:40:53:345 Error Domain=com.alamofire.error.serialization.response Code=-1011 "Request failed: forbidden (403)" UserInfo={com.alamofire.serialization.response.error.response=<NSHTTPURLResponse: 0x1601c88e0> { URL: http://blogg-kulan.se/2007c/xmlrpc.php } { status code: 403, headers {
    Connection = "keep-alive";
    "Content-Length" = 18;
    "Content-Type" = "text/html; charset=utf-8";
    Date = "Wed, 17 Aug 2016 14:40:53 GMT";
    Server = Varnish;
    "X-Varnish" = 912589832;
    } }, NSErrorFailingURLKey=http://blogg-kulan.se/2007c/xmlrpc.php, com.alamofire.serialization.response.error.data=<546f6f20 4d616e79 20526571 75657374 732e>, NSLocalizedDescription=Request failed: forbidden (403)}
    2016/08/17 16:40:57:832 Error Domain=com.alamofire.error.serialization.response Code=-1011 "Request failed: forbidden (403)" UserInfo={com.alamofire.serialization.response.error.response=<NSHTTPURLResponse: 0x16017b9b0> { URL: http://blogg-kulan.se/2007c/xmlrpc.php } { status code: 403, headers {
    Connection = "keep-alive";
    "Content-Length" = 18;
    "Content-Type" = "text/html; charset=utf-8";
    Date = "Wed, 17 Aug 2016 14:40:57 GMT";
    Server = Varnish;
    "X-Varnish" = 838452212;
    } }, NSErrorFailingURLKey=http://blogg-kulan.se/2007c/xmlrpc.php, com.alamofire.serialization.response.error.data=<546f6f20 4d616e79 20526571 75657374 732e>, NSLocalizedDescription=Request failed: forbidden (403)}
    2016/08/17 16:41:01:162 Error Domain=com.alamofire.error.serialization.response Code=-1011 "Request failed: forbidden (403)" UserInfo={com.alamofire.serialization.response.error.response=<NSHTTPURLResponse: 0x1600e4790> { URL: http://blogg-kulan.se/2007c/xmlrpc.php } { status code: 403, headers {
    Connection = "keep-alive";
    "Content-Length" = 18;
    "Content-Type" = "text/html; charset=utf-8";
    Date = "Wed, 17 Aug 2016 14:41:01 GMT";
    Server = Varnish;
    "X-Varnish" = 819554229;
    } }, NSErrorFailingURLKey=http://blogg-kulan.se/2007c/xmlrpc.php, com.alamofire.serialization.response.error.data=<546f6f20 4d616e79 20526571 75657374 732e>, NSLocalizedDescription=Request failed: forbidden (403)}

    During this week we have succeeded to add a blog to the app twice, but it only worked for a few minutes.
    Those of us that already are logged in to the app can use it and there is no problem, but we cannot add a new blog.
    We think that this started somewhere along the update of the system and the plugins

    Unfortunately, since our site isn't hosted on WordPress.com, we can't get the help we need from the app-support.

    What can be the problem?

    ~Jessica

  2. Hi Jessica,

    Thanks for providing a log and some excellent details about what is happening.

    There are a couple of things of particular interest:

    During this week we have succeeded to add a blog to the app twice, but it only worked for a few minutes.
    Those of us that already are logged in to the app can use it and there is no problem, but we cannot add a new blog.

    and

    NSErrorFailingURLKey=http://blogg-kulan.se/2007c/xmlrpc.php, com.alamofire.serialization.response.error.data=<546f6f20 4d616e79 20526571 75657374 732e>, NSLocalizedDescription=Request failed: forbidden (403)

    Based on this, I'd guess that your web host might be throttling XML-RPC requests. The throttle would be pretty lenient as you can use the app successfully for most tasks. I'd suspect the number and frequency of requests the app makes when adding a new site is just enough to trigger the throttling.

    Have you contacted your web host's support staff about the HTTP 403 Errors? Perhaps they can review the server logs and offer some insight about the exact cause. If it is an issue with throttling perhaps they can either white list the app or make it a bit more permissive.

    Let us know what they say.

    Cheers.

Topic Closed

This topic has been closed to new replies.


About this Topic