Hi @sanjitsharkbyte,
Thank you for writing! I checked the post you shared as an example and found this:
Response code 403: This response code could be due to a robots.txt block. Please allowlist facebookexternalhit on your sites robots.txt config to utilize Facebook scraping
You ca see that here: https://developers.facebook.com/tools/debug/?q=https%3A%2F%2Fpurrca.wpenginepowered.com%2Fblog%2Fjetpack-test%2F
Please make sure to update your robots.txt file accordingly. Additionally, the same issue could be affecting Instagram, so you may want to ensure that Instagram’s scraping bot is also allowed.
If you continue to experience issues after making these changes, please let me know, and we can investigate further.
Looking forward to your update.
Hello @alinclamba
I have fixed the robots.txt file and tried to reshare another test post. After publishing the post, Jetpack successfully shared it on Facebook, but it did not work for Instagram.
For your reference, here are the relevant links:
Could you please investigate why the post is not being shared on Instagram? Your assistance in resolving this issue would be greatly appreciated.
Hi @sanjitsharkbyte,
I checked this with our developers. It appears there as a potential syncronisation issue.Can you please try again and let us know if the issue persists. To reshare, click on the Instagram icon and click on share post for a post that has already been published.
Please give this a try and let us know how it goes.
Thank you!
Hello @alinclamba
I tried to reshare a post on Instagram, but I received an “Unable to share the Post” error message. Upon inspecting the network, I found that the Jetpack endpoint returns a “No media to share” error, even though the post has a featured image set.
Hi @sanjitsharkbyte –
I tested this using the image that you had and it worked in my tests:

Could you try publishing a completely new post, setting the featured image, and selecting to share to Instagram? Please then share the URL of the new post with us so that we can look at our logs.
Hello @sanjitsharkbyte,
Do you have updates about that? We usually close inactive threads after one week of no activity, but we want to make sure we’re all set before marking it as solved. Thanks!