@prabinm please send a report to Litespeed and share the ID generated.
You can follow these steps: https://docs.litespeedtech.com/lscache/lscwp/thirdparty/#document-report
Hi @litetim,
Thank you for your reply. Sorry to say this, I can’t share the report ID. Because this is one of our client’s site and they need absolute privacy on it.
Is there any other way to check and sort this issue?
@prabinm create a ticket and share this topic URL.
To creat a ticket send a email to: support at litespeedtech.com
Thank you
Since you cannot share the report ID publicly, I would debug the response path rather than the UCSS result itself.
That message usually means the remote LiteSpeed node notified WordPress, but WordPress returned something other than the expected REST/API response.
Check these privately:
- Open this in a logged-out browser:
/wp-json/
It should return JSON, not HTML, a redirect, a firewall page, or a maintenance page.
- Check server access logs around the time of the error for requests from:
38.114.121.40
Look at the status code and response type.
- Check whether any layer is blocking or changing REST requests:
- Cloudflare/WAF/Bot Fight mode
- ModSecurity
- security plugin
- basic auth
- maintenance mode
- custom redirects
- cache-everything CDN rule
- Exclude REST/API paths from aggressive cache/security rules:
/wp-json/*
admin-ajax.php
LiteSpeed callback/API paths if present in the logs
- Temporarily disable UCSS and reproduce. If the warning stops, the issue is likely the callback/notification path rather than general page speed.
If privacy is the concern, the private ticket is still probably the right route, but the server logs should show whether WordPress returned JSON, a 403, a redirect, or an HTML error page.
