Figured it out! I had a config issue, but will describe what happened in case it helps others. I apologize for wasting anyone’s time answering this.
I’m on a Windows system, running WAMP. I have a batch script that I run from the command-line to put the PHP executable on the system path, so it can be quickly run by typing “php”.
WAMP has two php.ini files in each of it’s PHP version folders. One called php.ini, and one called phpForApache.ini. The change I made to the Apache version (to make Sentry work when in a webpage), was not applied to the normal php.ini files, which the command line uses.
The change needed was to give curl a valid cert file, in the curl.cainfo setting. I use the one bundled with Firefox.
What would be nice
I’m not sure why Sentry v2 on Windows requires a CA cert this when v1 didn’t. But I’ve seen this issue in a few threads. It would be great if Sentry could check for this and warn the user, or document it better. Or at the least throw a meaningful error when the curl promise fails too many times. This issue was definitely my fault, but some sort of notification would have gone a long way to helping diagnose it.