QUIC.cloud’s access to your WP REST API seems to be blocked

Resolved Alexis
(@yelho)

8 months, 1 week ago
Hello there, I have a domain that was previously associated with Quic.Cloud via Litespeed and then removed. When I try to re-associate it, I get the following errors:
- Communication with QUIC.cloud server failed: Unknown error: unknown [server] https://wpapi.quic.cloud [service] tool/wp_rest_echo
- QUIC.cloud’s access to your WP REST API seems to be blocked.
I’ve followed a few steps to verify that my REST API is responding, but I haven’t done anything special except unassociating Litespeed from Quic.Cloud on the Quic.Cloud Dashboard. I asked my hoster to check if there was anything they could do on their end, but apparently nothing.

Last version WP / LS

I’ve uninstalled and reinstalled Litespeed, deleting all the database tables, but that doesn’t seem to make much difference. I also deactivated all other plugins, same. Any help would be appreciated, thanks a lot.
- This topic was modified 8 months, 1 week ago by Alexis.
- This topic was modified 8 months, 1 week ago by Alexis.
The page I need help with: [log in to see the link]

Viewing 15 replies - 1 through 15 (of 17 total)

1 2 →

Plugin Support litetim
(@litetim)

8 months, 1 week ago

@yelho

Please paste the logs from connection attempt.
This can be done from: go to toolbox -> debug setting -> debug log to ON , debug level to advanced , add send_report to debug include URI

To create a report go to LSC => Toolbox => Report => click on “send to Litespeed” and get the ID generated and share that ID

after it , go to toolbox -> log view , share the log it generates via https://pastebin.ubuntu.com/
Thread Starter Alexis
(@yelho)

8 months ago
Hello @litetim,

Thanks for you quick response. Here is the ID : DUUHMT

And here is the log: https://pastebin.ubuntu.com/p/9JNz7CX3gb/

Hope you will find the solution.
- This reply was modified 8 months ago by Alexis.
Thread Starter Alexis
(@yelho)

8 months ago
@litetim Litespeed web adc is, however, activated on the server side. I don’t understand the reason of this problem.
- This reply was modified 8 months ago by Alexis.
Plugin Support qtwrk
(@qtwrk)

8 months ago

have you checked this guide ?

please enable the debug log on the REST API endpoint , I will send a test request from there

Thread Starter Alexis
(@yelho)

8 months ago

Hello @qtwrk

I’ve already followed this guide before write this post. After adding php snippet, the remote ip isn’t the same that the x_forwarded_for, and the proxy_remote_addr returned “Null”. I don’t use any CDN like Cloudflare or others, but previously, I tried activating CDN function on Quic.Cloud dashboard, without changing my DNS records on the server end because of an hesitation and then I delete the function on the Quic.Cloud dashboard. On the guide, it’s said “contact your hosting provider to properly configure the client IP detection”, I’ve already do so but they tell me all they could do is already done and the problem don’t come from them, which would make sense since I didn’t do anything special and it has worked before.

I’ve enabled the debug log. Here is another log : https://pastebin.ubuntu.com/p/6mwRkG27GB/

Thanks a lot.

Plugin Support qtwrk
(@qtwrk)

8 months ago

07/05/25 22:54:03.460 [109.234.160.203:12010 1 oXD] ❄️ ❌ Not our cloud IP

I think your hosting provider needs to install mod_remoteIP for Apache , in order to make PHP to see the correct incoming request IP

ref: https://httpd.apache.org/docs/2.4/mod/mod_remoteip.html
Thread Starter Alexis
(@yelho)

8 months ago
@qtwrk Thanks for you quick response. However, I manage other sites through this same hosting provider and I have no problems. If the problem came from there, it would affect the other sites, right ?
- This reply was modified 8 months ago by Alexis.
Plugin Support qtwrk
(@qtwrk)

8 months ago

yes , if you ask me why , I have no explanation , maybe different server , differnet conf or something , I merely tell what I see from the log output…
Thread Starter Alexis
(@yelho)

8 months ago
Understood, thank you for your time. Unfortunately, I find myself stuck because, as I mentioned, the hosting provider tells me that they have done everything they can on their side by checking that no protection could interfere with Litespeed. Maybe I have to insist with them..
- This reply was modified 8 months ago by Alexis.
- This reply was modified 8 months ago by Alexis.
- This reply was modified 8 months ago by Alexis.
- This reply was modified 8 months ago by Alexis.
Plugin Support qtwrk
(@qtwrk)

8 months ago
```
<?php
$data = array(
        'remote_ip'         => $_SERVER['REMOTE_ADDR'] ?? 'Null',
        'x_forwarded_for'   => $_SERVER['HTTP_X_FORWARDED_FOR'] ?? 'Null',
        'proxy_remote_addr' => $_SERVER['PROXY_REMOTE_ADDR'] ?? 'Null'
);

var_dump($data);
```
please create a php file name it like ip_check.php and then share the link to it
Thread Starter Alexis
(@yelho)

8 months ago

@qtwrk Done. Here is the link : https://pastebin.ubuntu.com/p/FxhYrM79YP/. It seems to be the same as the other way.

Plugin Support qtwrk
(@qtwrk)

8 months ago

https://fermanvilleenscene.fr/ip_check.php

give me result array(3) { ["remote_ip"]=> string(15) "109.234.160.203" ["x_forwarded_for"]=> string(13) "79.116.xx.xxx" ["proxy_remote_addr"]=> string(4) "Null" }

where the 79.116.xx.xxx is my IP , it supposedly to be show on the remote_ip field , but instead, it shows the server IP itself , this is clear evidence that shows the mod_remoteIP is not properly configured , because if so , the remote_ip should show 79.116.xx.xxx
Thread Starter Alexis
(@yelho)

8 months ago
Thanks for your response. That’s the same for me. I Understood, I clearly told them right away exactly what you told me. If the problem is with Appache (mod_remoteIP), I have no control over it since it is shared/cloud hosting. They can therefore normally doing something. I hope their response will resolve the issue.
- This reply was modified 8 months ago by Alexis.
- This reply was modified 8 months ago by Alexis.
Thread Starter Alexis
(@yelho)

8 months ago
Hello @qtwrk,

Issue fixed. The support of my hosting provider finally accepted to take a look with your instructions… So it was necessary to insist by presenting the elements directly.

In any case, I really thank you for your help ! This topic may allow others to solve an identical problem.
- This reply was modified 8 months ago by Alexis.
- This reply was modified 8 months ago by Alexis.
Plugin Support qtwrk
(@qtwrk)

8 months ago

glad to know it sorted out now 🙂

Viewing 15 replies - 1 through 15 (of 17 total)

1 2 →

The topic ‘QUIC.cloud’s access to your WP REST API seems to be blocked’ is closed to new replies.