Forums

Can't Post In iOS App

  1. I can't post or edit articles or pages using the iOS app. I tried the simplest test:

    - Blog Posts
    - + to add a post
    - Test for the title and Testing for the content
    - Post

    I get "Error occurred during publishing"

    I turned on extra debugging and checked the logs:

    2016/11/12 13:58:34:639 <WPPostViewController: 0x102038400> savePost
    2016/11/12 13:58:35:456 Detected unbalanced register/unregister private site protocol.
    2016/11/12 13:58:35:481 post failed: The Jetpack site is inaccessible or returned an error: transport error - HTTP status code was not 200 (502) [-32300]

    I checked the PHP logs on the server and there was nothing (which isn't surprising given the 502 error).

    I've tried deleting/reinstalling the app. I've tried turning the JSON API off and back on. I've tried deactivating JetPack and reactivating it. I've tried disabling all plugins except JetPack.

    I even tried setting up a brand new WordPress site to test with. It is self-hosted and I'm using a Genesis theme from StudioPress.

    The only thing I can think of would be if it's using a port other than port 80 to post. The site is on a Google Cloud Engine server, which means you have to explicitly open up ports you want to use. I did a Google search and didn't see anything to indicate that JetPack uses a different port.

  2. Hi Mark,

    Thanks for sharing the excellent debugging steps you've already taken.

    Looking at the log snippet:

    2016/11/12 13:58:35:481 post failed: The Jetpack site is inaccessible or returned an error: transport error - HTTP status code was not 200 (502) [-32300]

    This suggests the problem exists somewhere between the Jetpack plugin, and its connection to WordPress.com's REST API. One way to test that theory would be to sign into the WordPress.com account connected to the Jetpack plugin, and see if you can make a test post to your blog via WordPress.com's editor. If you see an error there, then its likely the folks at https://jetpack.com/contact-support/ would be able to help.

    Let me know how it goes!

    Cheers
    Eric

  3. Thanks for the reply.

    I forgot to mention I had tried from WordPress.com and it worked. I just tested again (from both WordPress.com and the app). It worked from WordPress.com, but not the app.

  4. Hi Mark,

    That's very curious. If you don't mind mind sharing your blog's URL here I'd like to investigate a bit and see what I can discover.

    Cheers!

  5. http://mfm.consulting/ It has no content yet except a couple of test pages and posts.

    It happens with all the sites I manage as well. Also, I've tested from both my iPad and iPhone with the same results (error).

  6. Hmm... are all of the affected sites using the .consulting tld?

  7. No. The others are all .com.

  8. Another question:

    In the app, what do you see under the Notifications tab. Does it prompt you to connect to Jetpack or are you already connected?
    Also, if you look under My Sites > Site Name > Stats, do you see the stats feature appear?

    Both stats and notifications rely on Jetpack to function properly. It could be helpful to know if both are working or are showing errors of any kind.

  9. The notifications tab doesn't prompt me to connect. The stats page shows the same values that I see when viewing from the website, so it appears to be working correctly.

  10. I also tested changing Blog settings (My Sites > Site Name > Settings > anything under General) and received the same 502 error. Tried severals sites.

  11. Hi Mark,

    > I also tested changing Blog settings (My Sites > Site Name > Settings > anything under General) and received the same 502 error. Tried severals sites

    Interesting. It sounds like the app can read all the data it wants but isn't allowed to write anything.

    I've been chatting with some of the Jetpack support folks hoping to get some insight into what could be going on. We're wondering if there might be something configured by your web host to block or limit requests from the WordPress.com REST API. Maybe something that restricts POST requests under certain conditions? I don't think it would be a blanket rule since you can post to your blogs via WordPress.com's dashboard.

    I'm sorry I don't have a solution to offer. This is a tricky one and I confess I'm rather stumped.

  12. I appreciate you looking into it.

    Is that app communicating directly with JetPack on the blog site or is it going through WordPress.com?

  13. It communicates with WordPress.com, which communicates with Jetpack on the blog.

    I neglected to mention it before, but if the Notifications and Stats features are not essential, you could try signing out from WordPress.com in the app, and then using the self-hosted sign in form to add each blog individually. This method won't rely on the WordPress.com REST API to communicate with your blog. Instead it will use your blogs XMLRPC API. It's a different communication system, and would let the app talk to your blog directly. The catch is that certain features that depend on Jetpack will not be available.
    The self-hosted version of the sign in screen is the one that asks for your blogs URL and can be accessed via a link at the bottom of the initial sign in screen.

    I'd be curious to know if it gets around the error or maybe shows a different one.

  14. Hmmm... I just tried setting the site tag from WordPress.com and got an error. But I can still add a new post.

    I'm looking at the logs for the load balancer our servers are using. The error it is reporting is (translated):

    The backend sent a non-error response (1XX or 2XX) to an HTTP POST/PUT request before receiving the whole request body.

    Apparently, this can be related to an HTTP/1.1 100 Continue response from the server.

  15. I tried the self-hosted sign in and was able to post a blog entry using that method. That will work as a stop-gap, but I would really like to solve the problem with the WordPress.com/JetPack posting.

Topic Closed

This topic has been closed to new replies.


About this Topic

Tags

No tags yet.