Actually you were correct. The Subscribe2 plugin is trying to connect to our API server to check for a Subscribe2 plugin update/upgrade. Oops someone screwed up royally over at Subscribe2. 
Since the Subscribe2 plugin is trying to check for a plugin update/upgrade from our API server and obviously only the BPS Pro plugin exists on our API Server and not the Subscribe2 plugin then that update/upgrade check is being rejected/blocked by our API server and this also means that since Subscribe2 has hijacked the BPS Pro API server update/upgrade check then a check for a BPS Pro plugin update/upgrade is being broken.
Do you have a paid/premium version of Subscribe2? I tested the free version, but assume the premium version has an API server check and for this type of problem to be occurring the Subscribe2 API server checking code is not defining its API server URI/URL and is hijacking all API server connections.
- This reply was modified 1 day, 10 hours ago by AITpro Admin.
- This reply was modified 1 day, 10 hours ago by AITpro Admin.