Product registration occurs online, which means you'll need a stable internet connection for the process to complete successfully. If you experience registration issues, we invite you to contact our Support Team.
In the meantime, this article covers the most common causes and solutions. We have categorized them into visual issues, common browser/plugin blocks, and advanced server-side restrictions that can interfere with the communication between your WordPress site and our registration servers.
Visual & Layout Issues
Theme not properly installed
If your System Status page doesn't appear organized (missing the clean column layout, the green button, etc.), it means the theme was not installed correctly. Incomplete file uploads to the server can result in a broken System Status page where elements appear misplaced, files are missing, or yellow underlines show up, screenshot. This often happens with incomplete FTP uploads. To fix this, please reinstall the theme directly from the WordPress admin panel via Appearance → Themes → Add New → Upload Theme.
Common Blocks & Browser Issues
Disable browser extensions (AdBlockers)
Active ad-blocking extensions (such as AdBlocker, uBlock, or similar tools) can block the background communication between servers necessary to complete the registration. Please deactivate these extensions temporarily, or try completing the activation using your browser's Incognito Mode or a completely different browser.
Disable Coming Soon or Maintenance Mode plugins
The use of Coming Soon or Maintenance Mode plugins can restrict external access to your WordPress installation and block verification calls from our registration servers. Please temporarily disable these plugins during the activation procedure.
Disable Server Authentication Services
Make sure your server does not have active security prompts (like HTTP Basic Authentication) that restrict front-end or back-end access behind a specific username and password popup. These services prevent external APIs from communicating with your site. You may need to ask your web host to temporarily deactivate this block, screenshot .
Advanced & Hosting Server Issues
ISP Blockage & Country Restrictions (Proxy Solution)
Some Internet Service Providers (ISPs), notably in countries like Turkey and Russia, frequently block websites and networks that utilize Cloudflare. This completely cuts off connectivity to our API and store validation servers.
Solution: You can bypass this blockage and activate your license using a temporary proxy by following these steps:
- Go to an open proxy list such as us-proxy.org.
- Get the connection details (IP and Port) of the first available stable proxy.
- Add the following code snippet to the
functions.phpfile of your active Child Theme (replace the placeholder text with your proxy details):
add_action('http_api_curl', function( $handle ){
curl_setopt($handle, CURLOPT_PROXY, "REPLACE_ME_WITH_PROXY_IP");
curl_setopt($handle, CURLOPT_PROXYPORT, REPLACE_ME_WITH_PROXY_PORT);
}, 10)
- Perform the product registration. Once the license is successfully activated, remove or comment out this code to prevent future standard site requests from routing through the proxy.
Host Blocking Connections & Firewalls
Ensure there are no strict application firewalls running on your server. Security configurations like a cURL Firewall or general external restriction rules can prevent your site from reaching out. If you are registering an Envato purchase, temporary marketplace API outages can also cause timeouts.
Check with your hosting provider to verify they aren't blocking outbound connections to external domains. If they are, please ask them to whitelist our validation endpoint: api.undsgn.com.
Security Layer Blockage (e.g., ModSecurity)
License key generators (including Freemius) randomly generate multi-character strings using alphanumeric combinations and special characters. Certain web server security modules (such as ModSecurity) or strict firewall plugins might intercept the activation request because the string sequence looks "suspicious" to their default filters.
Solution: Temporarily deactivate the security plugin or web server module for the brief moment you perform the license activation. Turn it back on immediately after successful registration.
Caching Layer Issues (Memcached / Redis)
For maximum performance, certain store and license variables are saved together as a single row entry inside your database's wp_options table. Object caching layers like Memcached or Redis often have a strict Byte-limit allocation for individual stored options. If the length of the data payload exceeds that set memory limit, the settings might fail to load, save incompletely, or become corrupted.
Solution: Temporarily flush and disable your object caching layer/plugin just for the registration process, then re-enable it.
Database Column Encoding Issues
If there are special UTF-8 or UTF-16 characters (such as accents, non-Latin alphabets, or specific symbols) inside your profile registration name or billing address, a misconfigured database collation might fail to write the activation token into your database. The theme might say "Activated successfully" but instantly forget it on the next page refresh.
Solution: Access your database management tool (like phpMyAdmin) and ensure that the option_value column inside your wp_options table is set to a proper modern encoding standard like utf8mb4_unicode_ci.
Outdated Server Modules (cURL & WP Memory Limit)
- cURL Module: Outdated server-side cURL modules can fail to establish modern secure handshakes with our registration endpoints. You can check your current environment version using a plugin like WP Server Stats and match it against the latest cURL Releases. If your host cannot update it, you can apply this custom Cipher suites hack inside your Child Theme.
- WP Memory Limit: In very rare occurrences, a severely choked server environment can run out of memory when processing scripts. Double-check that your server is compliant with the minimum required WP Memory Limit indicated in your System Status tab.
Comments
0 comments
Article is closed for comments.