wordpress-mobile / wordpress-mobile/WordPress-iOS

Self-Hosted Site: Create Post: "Something went wrong The response from the Jetpack site could not be verified."

Open
#24,547 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

[Type] Bug Posting/Editing Self-hosted
Dominant language
Swift
Stars
3.9k
Forks
1.2k
Avg merge
23h 51m
Merged PRs (30d)
58

Description

Description

I am connected to my site hosted on a (LEMP Server) private domain via the Wordpress iOS app. When I try to publish a post on iOS, I get the following error message that pops up:

Something went wrong
The response from the Jetpack site could not be verified.
OK

I hit "OK" and it just returns me to the post edit screen.

What is going on here?
Why can't I publish a post on my Wordpress iOS app? Please help me debug this. Thanks.

Step-by-step reproduction instructions

Go to iOS app.
Select "My Site" .
Select "Posts".
Hit "+" icon.
Add a title
Write something
Hit "+' button
Select "Image"
Select "Take a Photo"
"Snap a photo with my camera"
Select "Use Photo"
Select "Publish"
Screen drops to Draft without publishing
Tap on "Arrow pointing in a half circle" icon, just above the "Failed to insert media. Tap for more info.".
Pop-up opens with the following message:

Media Options
cURL error 52: Empty reply from the server
Stop upload
Retry
Dismiss

I hit "Retry"
Blue Photo upload bar starts to fill up. Then it dissapears and gives me the screen that says:

Failed to insert media.
Tap for more info.

This cycle repeats itself.

Screenshots, screen recording, code snippet

No response

Environment info

Latest version of iOS and iOS App.
Wordpress Server = LEMP (Linux, Nginx, Mariadb, PHP8.3)

Please confirm that you have searched existing issues in the repo.
  • Yes

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No repository file, test, or entry point is identified in the report. Start by reproducing the iOS post-with-photo flow and inspect the server-side response associated with cURL error 52; done requires a reproducible failure and a narrowed cause for the failed media upload or verification.

Written by the indexing model from the issue text.

Assessment

Tech stack
ios, mariadb, nginx, php, swift
Domain
backend, mobile, networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.