emachuca

Done! Main domain is showing now.

?Muchísimas gracias!

That did the trick!

In Cloudflare:

• Security –> Bots –> Bot Fight Mode (disable it,and keep it disabled!)
• Now the domain key request from OLS Cache plugin to quic.com can work!
• I’m curious why this worked, because I have already tested by going to Overview –> Advanced actions –> Pause Cloudflare on site, which allegedly, bypasses all of Cloudflare′s medlying with the site.
• AND, in addition to that, I have had also disabled the Proxy status on DNS –> Records, for the A and CNAME records.
• Guess that, as they say, “Cloudflare works in mysterious ways.” ??

Still have a minor problem or doubt, I’m already connected to quick and have the domain key. However, there is a yellow message that says: “Main domain not generated yet.”

But, if I go the my quic dashboard, my domain is listed there an the status is OK.

Should I be worried about the yellow warning or is it normal?

Muchas gracias,

• This reply was modified 1 year, 11 months ago by emachuca.

I got desperate with this thing. I’m deleting the server and reinstalling everything again. If that doesn’t work again, then I’m switching to NGiNX. Thank you very much, really. Consider this issue closed.

Did that, but guess what?

Request failed from WordPress: [server] https://api.quic.cloud [service] wp/report

This is a case for the spider. By the way, the installations was made using the Openlitespeed/ WordPress script from the Google Cloud Marketplace.

Moreover, I even created a new WordPress database, just in case the one installed by the script had gremlins that corrupted it, but even that did not work.

Any other way to send the report and access URL?

• This reply was modified 1 year, 11 months ago by emachuca.

Disregard the domain name on 1) The POST call tohttps://studyandlearning.com/wp-json/litespeed/v1/token?failed.

By the way, you may close this issue. I’m deleting the Multisite and install individual WordPress sites.

Gracias,

Hola,

I think you should revert back to the old version of the WordPress plugin because I tried signing in to my site admin and the WP Bouncer immediately banned my IP!

Tried a different IP and again, firts try to access, then banned immediately. I can access the public site, though.

Funny thing is, in the server cscli alerts lists and cscli decisions list shows ” no active alerts/decisions”. So, I can’t un-ban my IP because is not banned ??

Moreover, if I go to https://app.crowdsec.net/ there are no alerts and no banned IPs listed.

Guess it is the Crowdsec plugin banning immediately when trying to access wp-admin or wp-login.

So, no, it doesn’t work with WP Multisite, as you mentioned.

Please revert it back to the old version.

Saludos,

Thanks for answering. I tested network disabling all plugins, except for Crowdsec but the problem persists: in the main site it all works fine, but in the subdomain site:

• Crowdsec tab: I can enter the configuration (same API Key and all the rest) and click Save and it seems to work, but if I try to “Test Bouncing” I get redirected to https://sub1.mysite.com/wp-admin/admin-post.php with error “There’s been a critical error on this web”.
• Advanced tab: I can enter the configuration but when I click the Save button, I get redirected to https://sub1.mysite.com/wp-admin/options.php with error “There’s been a critical error on this web”.
• Note that I get redirected to different pages but the error message is the same.
• I can hit the Back button in the browser and still have access to my site.
• I enabled Debug Mode in the main site (I can’t in the subdomain because when hitting the Save button I get the error).
• You can see the debug log text file here https://docs.google.com/document/d/1g6PUGv3UYkZcWNSW9G79XiIF3cbOkbkinbwWDys56Eg/edit?usp=sharing
• Note: haven’t yet tried assigning a different name to the WP bouncer, as you mentioned it should work fine with the same API, and would like to have it work that way.
• Also, I rebooted the server in case it would help, but no.

Added:

• Here is the nginx error log: https://docs.google.com/document/d/1OslN8Vi_UlBla9ycimYj4SiO1yJyLrZD-sc3uBAgfYc/edit?usp=sharing
• Here is the php error log: https://docs.google.com/document/d/1qfO6aHcVWDJw31sVW9CbZmbBOByYyjxNvMbF38xtAmo/edit?usp=sharing
• Note: as I’ve been testing, some plugins may have been activated but, after around the 8:30 am timestamp, only the NGiNX helper plugin was activated (FastCGI, with NGiNX Map enabled) and the Crowdsec plugin.

Gracias,

• This reply was modified 2 years, 1 month ago by emachuca.

Solved

So, sorry! It wasn’t your plugin but Google’s Site Kit the one making these weird redirections.

I wasn’t able to read the redirection string but I recorded it and was able to capture a frame and it redirects to /myblog.com/post-name-url/?_gl=1^18b…(many more letters).

I disabled the Google Site Kit plugin and the redirections stopped.

Firts time using this Google plugin.

Sorry again,

Forgot to mention that I had already deleted the browser’s history and also had flushed the DNS in Win10. And it happens with both Chrome and Edge, in both my PC and laptop.

In admin and in the frontend the plugin was still in English. However, I’m using now another Reviews plugin, mainly because this new one can make the avatar images to lazy load (I was getting errors for that on Google’s PageSpeedInsights). Thanks,

NOTE
You also need to turn off Load Google Fonts Async in Page Optimization –> Optimization Settings in LS Cache plugin.

Thus, turn off both Load CSS Asynchronously and Load Google Fonts Asynchronously for the page to validate on AMP.

SOLVED

After so much fiddling with the plugin options, I solved the AMP validation problem by turning off Load CSS Asynchronously in Page Optimization –> CSS Settings in LS Cache plugin.

My blog nos shows Valid AMP page.

deleted the plugin and no longer need it fixing. Made my own faq using good old html text.