transport error HTTP status code was not 200 (403) [-32300]

  • Resolved Richard Lukins

    (@richardlukins)


    6 years, 9 months ago

    Last week could post and save drafts from iOS, android, Windows Desktop & WP website via the Jetpack plugin … but it seems my hosting company made some changes and now I can’t and get errors, the Android app gives most information:
    Jetpack site is inaccessible or returned an error: transport error HTTP status code was not 200 (403) [-32300]

    from the wordpress website:
    https://wordpress.com/post/www.website_name.com
    just get “Saving of the draft failed” nothing extra!

    The website and admin pages are all fine, and drafts/posts can be made from there with no issues.

    The hosting company have come up with a fix and I now need to add a command to the .htaccess file in the root of the public_htnl:
    allow from all

    This appears a little broad, and their support staff are little lost in why this change is needed and if there is any broader security issues from the change! I think my hosting provider is not going to understand Jetpack well enough to provide any better fix, so hold no hope there!

    I was hoping to hear back from anyone here if there is a more targetted fix, based on their Jetpack knowledge of the files that need this access for the cUrl/API access, or if there is a file permission fix that could be applied to just the required files or databases etc?

    Sadly I’m unable to get any information on the change they have made which created the issue, so can’t tackle it from that angle either ??

    thanks in advance
    Richard

    The page I need help with: [log in to see the link]

Viewing 12 replies - 1 through 12 (of 12 total)
  • Thread Starter Richard Lukins

    (@richardlukins)

    Hi
    Just for anyone else out there who suffers this issue, the fix in my instance was to narrow the change, of “allow from all” to just one file, adding this to the .htaccess file in my WP root

    <Files xmlrpc.php>
allow from all
</Files>

    Not sure if this is going to be too narrow, but appears to be working for now.
    Hosting Company still unable to ascertain what they’ve changed, which is a concern, but back up and running and a solution I can accept in terms of security.
    Hope that helps others in the future.

    thanks
    Richard

    What is the address of the Jetpack site you were having an issue with?

    If you’d like, we can double-check that things are working well from our end, as well.

    Thread Starter Richard Lukins

    (@richardlukins)

    Hi
    thanks
    site with issues! Hopefully not anymore

    Let me know if you see any issues other than the obvious new site with lack of detailed contents as yet!
    Cheers
    Richard

    This site’s Jetpack connection looks good from our end, as well.

    However, you are running an old version of PHP. You may want to contact your host and have them update you to at least version 7.

    If you have additional questions, please let us know!

    Thread Starter Richard Lukins

    (@richardlukins)

    Sorry, had reverted to early PHP when trying to find a fix, reverted back to 7.1.5
    As this issue affects only the one file xmlrpc.php is there another way to solve this issue, via maybe file permissions?

    Currently file permission is set to 0644, would changing it to say 0755 fix it too?

    What does the “allow from all” .htaccess command actually change? I’m not a linux master as can be seen, so be gentle, I get that it changes the source requesting IP permissions, which is different from file permissions, but how come the site loads if the same IP would be blocked? A bit confused on this point!!!

    Thanks

    Thread Starter Richard Lukins

    (@richardlukins)

    Just to save time, tested with permission changed to 755 and removing the .htaccess, that also fixes the issue.
    Should the xmlrpc.php file be set with something other than 644 by default, ie 755?
    While all the folders of the WP install are 755, all the files are set to 644 … is this correct?
    Thanks
    Richard

    Thread Starter Richard Lukins

    (@richardlukins)

    …err … well either WP v2.9.3 or my hosts have changed something, as tested it reverted to 644 and it still works? Blinking confused!

    Thanks
    Richard

    Not sure if this is going to be too narrow, but appears to be working for now.
    Hosting Company still unable to ascertain what they’ve changed, which is a concern, but back up and running and a solution I can accept in terms of security.

    Your host should be able to properly secure your server. If you feel like you’re not getting a satisfactory response from them, you may want to evaluate the hosting options here:

    https://www.ads-software.com/hosting/

    What does the “allow from all” .htaccess command actually change?

    You can find information on this topic under the Allow Directive section here:

    https://httpd.apache.org/docs/2.4/mod/mod_access_compat.html

    While all the folders of the WP install are 755, all the files are set to 644 … is this correct?

    Permission can vary from host to host, but that is part of the permissions scheme for WordPress:

    If WordPress is running as the FTP account, that account needs to have write access, i.e., be the owner of the files, or belong to a group that has write access. In the latter case, that would mean permissions are set more permissively than default (for example, 775 rather than 755 for folders, and 664 instead of 644).

    https://codex.www.ads-software.com/Changing_File_Permissions#Permission_Scheme_for_WordPress

    …err … well either WP v2.9.3 or my hosts have changed something, as tested it reverted to 644 and it still works? Blinking confused!

    The Jetpack connection for this site still looks good. Are you seeing any change on your end?

    If you’d like more information on secure file permissions for WordPress, please refer to the following:

    https://codex.www.ads-software.com/Changing_File_Permissions#Finding_Secure_File_Permissions

    We hope that helps!

    Thread Starter Richard Lukins

    (@richardlukins)

    thanks, a perfect list of resources that I promise to read!

    Oddly the issue with no fix in place has become intermittent rather than resolved, and my host is not really giving answers, so I’m back to using

    <Files xmlrpc.php>
allow from all
</Files>

    The hosts have said using 755 permission is not the same and provides a larger security issue than the .htaccess modification above. So following that advise.

    The intermittent issue means that sometimes, from the WORDPRESS Android app when editing or adding blog posts/pages, I get no error and success, sometimes I get an error but still success in terms of upload, and once got the error and no upload. So rather than being left dangling, I’ve applied to mod and hope the issue is banished!

    Thanks again for your great advise and help.
    Ricahrd

    Thanks for getting back to us.

    I’ve checked it on Jetpack Debug page.

    It looks good now.

    Hi,
    I’m an extremely basic user and getting the same issue. We are on the road so I really need to be able to update posts via the wordpress app but getting the same error as above. Contacted my host (blue host) who advised the issue is due to night hare ssl bug this seems wrong to me as it was all working fine until today and haven’t changed anything at my end.

    Does anyone have a fix and a mini guide in how to do it please? I’m using a free theme so whole I’m sure I can copy paste pretty well I’ll prob need a few more details if using html ??

    All help would be massively appreciated. Thanks in advance.

    Site is thentravel.net

    Thanks

    Hi @neilo223,

    https://thentravel.net/xmlrpc.php is returning “HTTP/1.1 403 Forbidden”.

    You would check your hosting provider (Bluehost) to see if there is any limit or block to this file.

    In the case, the issue is still there, could you please start your own thread, as per the Forum Welcome?
    https://www.ads-software.com/support/plugin/jetpack#new-post

    Thank you!

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘transport error HTTP status code was not 200 (403) [-32300]’ is closed to new replies.