search

gatsbyjs / wp-gatsby

WordPress plugin for gatsby-source-wordpress
Other
167 stars 41 forks source link

No webhooks are triggering #196

Closed bogdancss closed 3 years ago

bogdancss commented 3 years ago

We have a gatsby site hooked up to wordpress and ever since the 29th of September, we cannot seem to get the automated builds and/or previews to work anymore. This might be a coincidence, but that is when the NODE_VERSION thing changed

we have all the latest versions of all the plugins up and running - and the WPGatsby plugin is setup correctly but the builds are still not being started when we post/update changes

we are using Gatsby Cloud as a host and have updated the NODE_VERSION to 14

used Postman to try and trigger the build webhook and that works fine, so it's something in wordpress

I removed the WPGatsby plugin and removed all options that contain the string gatsby from Settings > Options, then reinstalled the plugin (the fields we re now empty), filled them in with the appropriate webhooks and still nothing happens when updating a post

chrisbooth247 commented 3 years ago

Hey @bogdancss

We're having a similar issue, specifically with just preview builds on Gatsby cloud not working. We're using the WPGatsby plugin to hit our Netlify webhook on page update, and just using Gatsby Cloud for the page Preview functions.

We've tried hitting the Gatsby Cloud Build and Preview webhooks using a PHP script on our server, and it seems to just be silently failing, where as the Netlify build hook is triggered fine!

Sending a CURL req. to the Gatsby Cloud webhooks from terminal on a local machine however seems to work fine. I can only assume in our case something to do with the server as opposed to Wordpress itself?

Did you have any luck solving this at all?

Thanks!

Edit: After a bit more debugging, we found that we were unable to send the CURL request to Gatsby Cloud due to curl error 60 - an issue with our SSL cert. We managed to confirm this by adding add_filter('https_ssl_verify', '__return_false'); to our functions.php file, which allowed us to temporarily trigger builds, before we identified and fixed the root issue with our SSL cert and solved the problem!

bogdancss commented 3 years ago

@chrisbooth247 - no still the same. So when we POST the build webhook using something like Postman, it works - so it's something wrong on the wordpress side.

Hoping @TylerBarnes or @jasonbahl will shed some light on this.

bogdancss commented 3 years ago

ok - just restarted the wordpress server and not sure what that did, but that seem to have fixed the build & preview/content sync triggers.