Skip to content Skip to sidebar

This thread is resolved. Here is a description of the problem and solution.

Problem:
The client is experiencing an issue where attempting to validate the Litespeed extension with QUIC.cloud results in a 404 error page when WPML is activated. This problem persists even after resaving permalinks with WPML deactivated, indicating a potential redirect issue caused by WPML.
Solution:
We recommend the following steps to troubleshoot and potentially resolve the issue:
1. Deactivate WPML and connect to the Litespeed Cloud. If successful, reactivate WPML and check if the issue reoccurs.
2. If the problem persists, create a sandbox site with a fresh WordPress, WPML, and Litespeed installation to verify if the issue is specific to the client's current site setup.
3. Consult with the hosting providers to check for any server-side configurations, firewall rules, or security directives that might be causing the redirect issue. Additionally, reviewing server logs may provide further insights into the problem.

If these steps do not resolve the issue or if the solution seems outdated or irrelevant to your case, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the problem persists, please open a new support ticket at WPML support forum for further assistance.

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

This topic contains 16 replies, has 1 voice.

Last updated by Carlos Rojas 2 months, 2 weeks ago.

Assisted by: Carlos Rojas.

Author Posts
December 7, 2025 at 9:45 am #17641417

philippeB-68

Hi Carlos,

I reckon that we will not get to the root of this. Similar to your claim, the hosting company is claiming that without WPML, Litespeed QUIC Cloud server is reachable and with WPML it is not, and that hence the problem is with WPML.

Please note that this is happening with two distinct hosting providers:
o2swith (hidden link)
AlpHosting (hidden link)

So this may be linked to a specific hosting environment, but not a unique hosting environment.

Best regards,
Philippe

December 8, 2025 at 11:20 am #17643563

Carlos Rojas
WPML Supporter since 03/2017

Languages: English (English ) Spanish (Español )

Timezone: Europe/Madrid (GMT+01:00)

Hi Philippe,
Thank you very much for your message.

Did they say what was causing this problem on WPML? Were they more specific?