Plugin Support
qtwrk
(@qtwrk)
test@node119:~$ curl -XGET https://somethingintheweb.fr/?rest_route=/lscwp/ip-check
<!--Debug [[Security_Rule = "badbots"; More_info = "L'accès est bloqué suite à l'activation de la sécurité badbots dans cPanel. Cette sécurité bloque les robots ayant une mauvaise réputation."; HTTP_Code = "403""; Request_ID = "bd66a0ca868126ae316c877d8e892de3"; Support = "[email protected]"; Link = "https://faq.o2switch.fr/hebergement-mutualise/tutoriels-cpanel/tiger-protect"]] EndOfDebug-->
<!DOCTYPE HTML>
<html lang="en-US">
<head>
<meta charset="UTF-8" />
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<meta http-equiv="X-UA-Compatible" content="IE=Edge,chrome=1" />
<meta name="robots" content="noindex" />
<meta name="retry-after" content="240" />
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1" />
<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/5.15.3/css/all.min.css" integrity="sha512-iBBXm8fW90+nuLcSKlbmrPcLa0OT92xO1BIsZ+ywDWZCvqsWgccV3gFoRBv0z+8dLJgyAHIhR35VZc2oM/gI1w==" crossorigin="anonymous" referrerpolicy="no-referrer" />
<script src="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/5.15.3/js/all.min.js" integrity="sha512-RXf+QSDCUQs5uwRKaDoXt55jygZZm2V++WUZduaU/Ui/9EGp3f/2KZVahFZBKGH0s774sd3HmrhUy+SgOFQLVQ==" crossorigin="anonymous" referrerpolicy="no-referrer"></script>
<script src="https://cdnjs.cloudflare.com/ajax/libs/jquery/3.6.1/jquery.min.js" integrity="sha512-aVKKRRi/Q/YV+4mjoKBsE4x3H+BkegoM/em46NNlCqNTmUYADjBbeNefNxYV7giUp0VxICtqdrbqU7iVaeZNXA==" crossorigin="anonymous" referrerpolicy="no-referrer"></script>
<link id="favicon" rel="shortcut icon" type="image/svg+xml" href="https://o2swit.ch/assets/favicon.svg"/>
<link href="https://o2swit.ch/assets/style.css" rel="stylesheet">
<title>HTTP 403</title>
</head>
<body>
<table width="100%" height="100%" cellpadding="20">
<tr>
<td align="center" valign="middle">
<div class="o2s-browser-check">
<div id="o2s-content">
<h1>
<i class="fas fa-shield-alt"></i>️
HTTP 403<br/>
<small data-i18n-key="title">
Accès interdit
</small>
</h1>
<p style="margin-top:2em;" data-i18n-key="lead">
Cette requête a été bloquée par une sécurité activée sur l'hébergement. <br/>
Si vous êtes le webmaster de ce site, vous pouvez désactiver cette sécurité depuis votre compte cPanel.
</p>
<p style="margin-top:1em;">
<span style="text-decoration: none;"><i class="fas fa-external-link-alt"></i> </span>
<a href="https://faq.o2switch.fr/hebergement-mutualise/tutoriels-cpanel/tiger-protect" target="_blank">
<span data-i18n-key="link">
Comment gérer cette sécurité avec TigerProtect dans cPanel ?
</span>
</a>
</p>
<p>
<span data-i18n-key="rule">Nom de la règle de sécurité déclenchée </span> : <strong>badbots</strong>
</p>
</div>
</div>
<div>
<img id="img" width="250" src="https://o2swit.ch/assets/tiger.svg" />
<br/><br/>
<small>
<a href="https://www.o2switch.fr" target="_blank">[email protected]</a>
-
<a href="https://faq.o2switch.fr/hebergement-mutualise/tutoriels-cpanel/tiger-protect" target="_blank">Tiger Protect</a> <br/>
<strong>Request ID </strong>: 777364bd962989ebee6e90cc7826c97a
</small>
<br>
</div>
</td>
</tr>
</table>
<script type="text/javascript">
$(document).ready(function() {
const supportedLocales = ["en", "fr"];
const translations = {
"en": {
"title": <br><br> Access denied<br><br>,
"lead": <br><br> This request was blocked by a security enabled on the hosting account. <br/><br> If you are the webmaster of this site, you can disable this security from your cPanel account.<br><br>,
"link": "How to manage this security with the Tiger Protect Tool on cPanel ?",
"rule" : "Name of the security rule triggered"
},
"fr": {
"title": <br><br> Accès interdit<br><br>,
"lead": <br><br> Cette requête a été bloquée par une sécurité activée sur l'hébergement. <br/><br> Si vous êtes le webmaster de ce site, vous pouvez désactiver cette sécurité depuis votre compte cPanel.<br><br>,
"link": "Comment gérer cette sécurité avec TigerProtect dans cPanel ?",
"rule" : "Nom de la règle de sécurité déclenchée"
},
};
function browserLocales(languageCodeOnly = false) {
return navigator.languages.map((locale) =>
languageCodeOnly ? locale.split("-")[0] : locale,
);
}
function isSupported(locale) {
return supportedLocales.indexOf(locale) > -1;
}
function supportedOrDefault(locales) {
return locales.find(isSupported) || 'en';
}
const locale = supportedOrDefault(browserLocales(true));
document.querySelectorAll("[data-i18n-key]").forEach(function(element) {
const key = element.getAttribute("data-i18n-key");
const translation = translations[locale][key];
element.innerHTML = translation;
}
);
});
</script>
</body>
</html>
<!--Debug [[Security_Rule = "badbots"; More_info = "L'accès est bloqué suite à l'activation de la sécurité badbots dans cPanel. Cette sécurité bloque les robots ayant une mauvaise réputation."; HTTP_Code = "403""; Request_ID = "9301eaf74489a3c9b78202e14a926e53"; Support = "[email protected]"; Link = "https://faq.o2switch.fr/hebergement-mutualise/tutoriels-cpanel/tiger-protect"]] EndOfDebug-->
it looks like your provider has some kind of firewall that is blocking the request
Hello,
Thank you for your analysis and for checking the endpoint from your side.
I just wanted to let you know that the issue is now resolved.
After further investigation, the problem was caused by an inconsistent LiteSpeed Cache state following the manual removal of the wp-content/litespeed directory. This seems to have broken the internal QUIC.cloud linkage (tokens / generated data), which resulted in QUIC.cloud nodes being unable to properly reach the REST endpoints.
I fixed the issue by:
- Resetting LiteSpeed Cache settings
- Fully uninstalling and reinstalling the LiteSpeed Cache plugin
- Re-linking the site to QUIC.cloud
After that, QUIC.cloud connectivity was restored and CCSS / UCSS generation is working normally again. The warning message no longer appears.
For clarity: no changes were made to the hosting firewall configuration. TigerProtect and its existing security rules (including badbots protection) were left exactly as they were before the issue and remain enabled.
Thanks again for your support and for pointing out the firewall behavior during your test.
Best regards,
Aurélien
