Continuing the support related to the new issue here. Thank you for sharing all the details and the information about what you have done in order to try solving the problem.
To help you with a better support I will need that you share a temporary access with me, so I can check the logs and some extra advanced settings on your site. Could you please share a temporary access? This is super private and if you agree with it, please share the access on the form you'll see above this reply. This will keep the information private and nobody will have access to it.
Please do not share access if is not on the private form or email.
Thanks for sharing the access. I have tried to duplicate the issue but I couldn't 🙁 I recorded a loom where I show you what I'm seeing right now -> hidden link
Having said this, I have reviewed your site and here are some findings:
The message "WPML didn't manage to translate this page" appears when WPML tries to create or open the Advanced Translation Editor (ATE) job, but something goes wrong in that process. Instead of opening the editor, your site is redirected back to the admin page with an error flag, which is why you see the page reload and the translation jobs look stuck.
What I found in the ATE logs
We reviewed the ATE error logs you provided, and they show a recurring pattern of connection timeouts (cURL error 28) when your site tries to reach our ATE servers (`ate.wpml.org` and `ams.wpml.org`). There was also an instance of Service Unavailable (HTTP 503). This indicates that the connection between your site’s server and our ATE service is failing, so jobs cannot be sent or synced properly. The logs also show multiple “Job resent to ATE” entries with increasing retry counts, which confirms that jobs are repeatedly failing to reach our servers.
**What to try next**
Please follow these steps, ideally on a staging copy of the site first if possible:
1. First, let's try again if you are able to translate now
- Please confirm that it works by testing again.
2. **Check server connectivity to WPML**
- Ask your hosting provider to verify that outgoing HTTPS connections to `ate.wpml.org` and `ams.wpml.org` on port 443 are not blocked by any firewall, WAF, security rules, or proxy.
- Request that they check whether server-side network issues or resource limits could be causing connection timeouts.
(Think this one is not the case, but just in case, I mention this)
3. **If the problem continues**
- Please provide:
- The full URL from your browser’s address bar after you click “Take and Translate” and the page reloads.
- Any new ATE error log entries around the time of the failed attempt.
- Confirmation from your host that the server can reach `ate.wpml.org` and `ams.wpml.org` on port 443.
With this information, we can determine whether the issue is ongoing connectivity with ATE or something else, and then either clean up the affected jobs or adjust the ATE connection so the Translation Editor opens correctly.
