Hi,
Thanks for the detailed report, and to the plugin author for the quick reply. Your trace helped us find the issue quickly.
The cause was on the ProvenExpert side, not in the plugin or your WordPress setup. When the auto-connect was started more than once for the same site (for example after an interrupted or repeated attempt), our server stored the setup token incorrectly. The plugin’s final connect request was then always rejected with 401 Unauthorized, however many times it was retried. A first-time connection wasn’t affected.
On the Content-Type point: we checked it, and our API reads the JSON body correctly even without that header, so it wasn’t the cause here.
The fix is now live. To connect, open Settings > ProvenExpert in WordPress and start the auto-connect once more. It should now complete. Entering the API credentials manually is no longer needed, though it keeps working.
If it still fails for you, please reply here or contact our support, and we’ll look into it right away.
Sorry for the trouble, and thanks again for the thorough report!
Best regards
ProvenExpert Support
