litespeedtech / litespeedtech/lscache_wp
Curl errors for service img_optm
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 257
- Forks
- 123
- PR merge metrics
- No merged PRs in 30d
Description
Recently when I sign into various sites that use this cache, I'm seeing this error:
`Failed to request via WordPress: cURL error 28: Operation timed out after 15001 milliseconds with 0 bytes received [server] https://node119.quic.cloud [service] img_optm`
EG:
It's happening with multiple sites, and I opened a ticket with our hosting company who said it looks like we are getting blocked, perhaps for too many requests, but its nothing on their side blocking the outgoing request.
Is there anything I need to do to fix this?
btw, the node119 bit varies between each time that I see it, and sometimes its in the dashboard multiple times when I sign in.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file, test, or entry point is named. Start by reproducing the WordPress sign-in flow and tracing the cURL request to the varying img_optm nodes, then determine whether the 15-second timeout is consistently caused by the service or request volume. Done means the timeout has an identified cause and affected requests no longer fail, or the limitation is clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php, wordpress
- Domain
- backend, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100