Sounds like issues with your server connecting to Salesforce. Possibly the new endpoint due to it’s being configured differently.
Unfortunately, that likely has very little (if anything) to do with the plugin… and more to do with your server configuration.
Thread Starter
Dan
(@danielnr87)
Hi Nick,
Humm, unusual. Please can you confirm the recommended server requirements, ie. php ver, allowed IP’s etc? I’m wondering if Wordfence could be blocking it, have you experienced this before?
Also, is there anything that needs to change on the plugin to enable the new API, or is it enabled by default?
Many thanks
Nothing special: If you can run WordPress, the plugin should work.
It uses the WordPress “remote post” functions to make the remote connection to SF, which falls back to curl if needed, has sane defaults, etc.
Other users have had issues with timeouts, outdated curl, outdated openssl, etc. No common reasons other than their hosting was all configured differently, and SF has been removing SSL ciphers and requiring newer versions of TLS (and deprecating SSL)… so it’s exposing some poorly managed web hosts.
But those are all way below the level of even WordPress and definitely the plugin.
As you can imagine, I can’t help you troubleshoot low-level server issues like these on this forum.
The new endpoint is enabled by default. Switching back is not a valid solution as the old endpoint is going away soon.
-
This reply was modified 9 years ago by
Nick Ciske.