If you are getting the following error message:
"Unable to connect to OptimizePress Security & Licensing service."
This means that your OptimizePress installation was not able to reach our licensing server. This could happen for several reasons, but usually waiting a few minutes and then clicking the green "Save Settings" button at the bottom of the OptimizePress > Global Settings screen will resolve this.
If you find that the license key is still not validating, please check the following:
1. API Key Matches:
Please login to http://members.optimizepress.com and click on the licensing tab on the top menu. Please verify that the key entered on your site matches a key on the licensing page.
2. Site URL Matches the API KEY
The site URL would also need to match. Make sure the URL on the right side of the license key is the same as the "Site Address (URL)" found under the WordPress Dashboard's "Settings" and "General" area.
If the site URL does not match, then click the "clear" link to the right of the site url in the licensing area of http://members.optimizepress.com to reset the key, and then click the "Save Settings" button again on your site in the OptimizePress > Global Settings screen to re-assign the site to the API key.
Please note that if you accidentally used an API key that is already in use, you might want to just copy and paste a new API key into the API field under Global Settings in OptimizePress.
NOTE: You can not use the same API key on multiple sites. Each site must use it's own unique API key for the licensing page of your site.
3. Web Hosting Company's Server Blocking Communications
If all this matches and you are still having problems getting this message, then please verify with your web hosting company that they are not blocking communications with a firewall or other means.
They may need to white-list our API Licensing Servers IP addresses. If that is the case, then please provide them the following information:
Please ensure BOTH of the following IP addresses are whitelisted:
If you have questions regarding any of the above, or still having issues with this message appearing, please contact the helpdesk for additional instructions and workarounds.