Thread Starter
jay437
(@jay437)
BTW, the website is hosted on Hostinger.
Error messages:
Failed to communicate with QUIC.cloud server: Unknown error: unknown [server] https://wpapi.quic.cloud [service] tool/wp_rest_echoDismiss this notice.
QUIC.cloud’s access to your WP REST API seems to be blocked.
@jay437 Thank you for report.
Looking over it I see 2 things that caught my atention:
– You have wps-hide-login installed. Make sure you allow XML-RPC and is not limited by this plugin or other code
– .htaccess content seems very small and missing rules. Is not a wrong thing, but might cause errors on some links
-
This reply was modified 6 months, 3 weeks ago by
litetim.
Thread Starter
jay437
(@jay437)
In Step 1 of the troubleshooting process, I got the following. “remote_ip” is the ip of my browser. is it a problem to miss the other 2 ip addressed? The site is behind the Cloudflare proxy.
{
“remote_ip”: “119.xxx.xxx.163”,
“x_forwarded_for”: “Null”,
“proxy_remote_addr”: “Null”
}
@jay437 Is your server(direct IP) 191.xxx.xxx.219?
@jay437 please enable DEBUG
Clear debug logs
And retry connecting to QC.
Please share the LSC logs, generated. You can use something like: https://pastebin.com/ or https://pastebin.ubuntu.com/
Thread Starter
jay437
(@jay437)
Hi, I have figured the problem and found a solution. Thanks for looking into this.
I have the Cloudflare proxy in front of the server with Hostinger. The headers are like the following.
“remote_ip”: Cloudflare IP
“x_forwarded_for”: Visitor’s IP
The solution that I found is to install the Cloudflare wordpress plugin, which corrected the remote_ip header.
If I didn’t find the solution, then I would have to write our own php code to achieve the same thing. Ideally, the LS plugin should accept the x_forwarded_for header.
@jay437 ok.
nice debugging and I will talk with the developers and see what we can do about this. No promises 🙂
Closing the topic
