wp-media / wp-media/imagify-plugin
Improve getaddrinfo Error Message
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 82
- Forks
- 31
- Avg merge
- 5d 10h
- Merged PRs (30d)
- 9
Description
Sometimes users get the following error message:

I tried searching the imagify-plugin and imagify repos, but found no mention of this error, so I assume it's a message coming from the server. Do we know specifically why these errors happen?
It's definitely not clear to the users from the current error message why the error is happening or what to do about it.
In some cases, this is resolved by having users log out and log back in:
https://secure.helpscout.net/conversation/1346912386/215251
https://secure.helpscout.net/conversation/1341841336/213392
In others, we see users getting cURL error 28's:
https://secure.helpscout.net/conversation/1372646588/224792
https://secure.helpscout.net/conversation/1645552341/297931
Instead, we could offer a more helpful message linking to either Optimization is Stuck or a new page for this specific error. Possibly something like:

<strong>A server error occured during optimization: <a href="https://imagify.io/documentation/optimization-is-stuck/" rel="noopener" target="_blank">More info and possible solutions</a></strong>
Though it could be a bit different / more descriptive based on the reason why these errors occur.
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
Start by locating the plugin's handling of getaddrinfo and cURL error 28 responses, then review the Optimization is Stuck documentation linked in the issue. Done means users receive a clearer optimization error message with a relevant link and guidance for these failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend, documentation
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100