• Plugin Support qtwrk

    (@qtwrk)


    Step 1: Verify IP Detection

    Add this code snippet to your theme’s functions.php file:

    function ip_check_callback() {
        $data = array(
            'remote_ip'         => $_SERVER['REMOTE_ADDR'] ?? 'Null',
            'x_forwarded_for'   => $_SERVER['HTTP_X_FORWARDED_FOR'] ?? 'Null',
            'proxy_remote_addr' => $_SERVER['PROXY_REMOTE_ADDR'] ?? 'Null'
        );
        
        return rest_ensure_response($data);
    }
    
    function register_ip_check_route() {
        register_rest_route('lscwp', '/ip-check', array(
            'methods'  => 'GET',
            'callback' => 'ip_check_callback'
        ));
    }
    
    add_action('rest_api_init', 'register_ip_check_route');

    This creates a REST API endpoint for IP verification. Test it by visiting:
    https://your_domain.com/?rest_route=/lscwp/ip-check

    Expected Result:

    {
      "remote_ip": "79.xxx.xxx.183",
      "x_forwarded_for": "79.xxx.xxx.183, 176.xxx.xxx.157",
      "proxy_remote_addr": "176.xxx.xxx.157"
    }
    • remote_ip should match your actual IP (verify at whatsmyip.org)
    • This confirms PHP detects the correct client IP

    Problem Scenario:

    {
      "remote_ip": "176.xxx.xxx.157",
      "x_forwarded_for": "79.xxx.xxx.183, 176.xxx.xxx.157",
      "proxy_remote_addr": "176.xxx.xxx.157"
    }

    If remote_ip doesn’t match your actual IP, your server isn’t properly forwarding client IPs. This typically occurs when using:

    • CloudFlare
    • CDN services
    • Reverse proxies

    Solution: Contact your hosting provider to properly configure the client IP detection:

    • For LSWS/OLS: Enable “Use client IP in header” in webadmin console
    • For Apache: Install and configure mod_remoteIP
    • Other web servers: Implement corresponding client IP detection solution

    Step 2: Check REST API Accessibility

    If you receive 401, 403, or 404 errors:

    • Your WP REST API may be disabled
    • Common causes: Security plugins or optimization plugins
    • Action: Re-enable WP REST API (required for plugin functionality)

    Step 3: Advanced Troubleshooting

    If steps 1 and 2 all check out

    3.1 Submit Report

    1. Go to LiteSpeed Cache → Toolbox → Report
    2. Click “Send to LiteSpeed”
    3. Share the 8-character report number (e.g., “ABCDEFGH”) when you create topic

    3.2 Enable Debug Logging

    1. Navigate to LiteSpeed Cache → Toolbox → Debug Settings
    2. Configure:
      • Debug Log: ON
      • Debug Level: Advanced
      • Debug Include URI: rest_route=/litespeed
    3. Clear existing logs (Toolbox → Log View)
    4. Our team will send test requests
    5. Share logs via Ubuntu Pastebin or similar service

    If you have enabled debug log , please also mention it when you create topic

    This should help us efficiently diagnose and resolve your WPAPI issues.

    • This topic was modified 1 month, 1 week ago by qtwrk.
    • This topic was modified 1 month, 1 week ago by qtwrk.
Viewing 2 replies - 1 through 2 (of 2 total)
Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Troubleshooting: Failed to get echo data from WPAPI’ is closed to new replies.