hotweazel
Forum Replies Created
-
Hello Mario,
Hoping to hear back from you regarding this issue. Thank you.
Hello Mário, hope you had a chance to review my last post. Please let me know. Thank you!
<span style=”font-size: inherit;”>Thanks for the explanation.</span>
We confirmed with our hosting provider that the hostname resolves to a public IP address from within the server environment and not to a private/internal IP range.
We also confirmed:
- Direct curl POST requests succeed.
- The endpoint returns HTTP 200.
- The issue began after the change from wp_remote_post() to wp_safe_remote_post().
One notable detail is that the webhook endpoint uses HTTPS on a non-standard port rather than port 443.
Could wp_safe_remote_post() or WordPress safe URL validation be rejecting the request because of the custom HTTPS port?
If not, is there a way to expose the underlying WP_Error code/message so we can see exactly why WordPress is rejecting the request?
Forum: Fixing WordPress
In reply to: Error after updating to 4.2@dingo_bastard I am facing the same issue but don’t know how to make a counter $i. Would you please give me the instructions? Thank you in advance for your help!