-
I randomly (and regularly) am experiencing server timeouts.
There is nothing in the PHP logs
Hosting says there is nothing in ModSecurity or any other firewall logs.
I thought it was only happening while editing an Element (and possibly 2 elements containing Query Loops); however, I now continue to experience this on standard Pages.
There are no WAF rules in Cloudflare causing this, and nothing appears in the Event logs.
Same for WOrdfence – no WAF rules and nothing in the logs.Error message on the front end:
This site can’t be reached – took too long to respond.
Checking the connection
Checking the proxy and the firewall
Running Windows Network Diagnostics
ERR_CONNECTION_TIMED_OUTRed error message (at top of page) on backend pages when they freeze up:
Server TimeoutThis is happening more frequently and ONLY when editing in GeneratePress/Blocks.
I am frozen out for usually between 5 and 15 minutes at a time.Any help is much appreciated.
-
Hi there,
Can you disable all other plugins except GB and GP Premium and all server-level security settings to test?
And is there a specific page that is likely to show the issue?
-
Hi Ying
I cannot disable all plugins as the site is currently live.
I have done this in the past (a couple of months ago) and have not found a culprit.
I can try again with the Site Health Troubleshooting – if that is acceptable to you?All server firewalls have been disabled.
Originally, I only noticed it happening with on a Block ContentTemplate Element but have since experienced it randomly and much more often. URL below
If you want me to test again with the Site Health option let me know (or if you wanted to, you are more than welcome also)
Justin
-
I would recommend creating a staging site and sharing the credentials with us so we can test on it.
Can you do that? Thanks!
-
Hi Ying
I have created the staging site – details below
I have confirmed all firewalls and server-side security is off – 100%When i created the staging site i was getting a critical error. After sorting our what I though was LiteSpeed Cahce plugin causing this i noticed that Query Monitor plugin would not activate – if i tried activating it, i got this message: Plugin could not be activated because it triggered a fatal error.
(I was planning on deactivating & deleting it anyway)
So I went back to the live site and deactivated it and then reactivated it, and it activated fine (without error).I then left it deactivated and spent the day working on the live site to test again – I made edits to EVERY PAGE AND POST and had no problems at all.
UNTIL – I made a change that I thought may require clearing the cache – I “Purged All” in LiteSpeed Cache and the issue happened again.Error on the back end:
Updating failed. Could not get a valid response from the server.
Page URL below.Error on the frontend:
This site can’t be reached
xx.com took too long to respond.
Try:Checking the connection
Checking the proxy and the firewall
Running Windows Network Diagnostics
ERR_CONNECTION_TIMED_OUTSo i initially thought it was the Query Monitor plugin crashing, but now it could be a cache issue, or both, or still something with GP???
Yesterday I changed a setting in LiteSpeed Cache to NO LONGER auto-flush the cache on Page or Archive Post Save – so now that the first time i clear the cache manually it happened…could there be an issue with GP AND LiteSpeed (both together or one or the other)I hope some of this helps,
-
Hi Ying
Just to add something I have also just discovered:
When trying to Add a Display Condition (Create New Condition) the page opens but the loading wheel spins fora very long time. Eventually it opens but if i choose Post Meta – the Select Operator and Select Rule drop-downs appear but when I click on them nothing happens. If i try to save the Condition as is teh bule save button says Saving… (for a very long time) but fails and a red banner with this appears: Failed to save condition. Please try again.
I cannot create a condition (i have done in the past without issue)And when trying to “Create New Overlay Panel” it also does not load, I get this:
Loading editor…
Please wait while the overlay panel editor loads
THEN
It does not load – just an image of an unhappy file and this message:
dolomitesactivetours.com took too long to respond.So nothing to do with caching at this point.
-
Thanks for the info and creating the staging site, but the staging login link is returning 404 error, can you check?
I would suggest testing with all plugins deactivated except GP Premium and GB to check if it’s a standalone GB issue first.
-
Sorry, I updated it.
-
I’ve disabled all plugins except GB, GB Pro, GP Premium, ACF and Custom Post Type UI; the page editor has no issue at all. I tried making small changes and saved a couple of times, but I didn’t see any issues.
So it looks like the issue isn’t from GB but from one of the plugins.
I also activated the Lightspeed cache plugin; there is no issue either.
You can now try to activate the plugins one at a time, to see which one is causing it.
`
-
Hi Ying
I have figured it out.
It is not another plugin.
It is GeneratePress (or the way I have created/built a Block Content Template Element – ID 48789 and QUIC.cloud related (our CDN).Apparently every time i save this template or make an edit (possibly due to the number of ACF fields, Query loops and repeaters the CDN server was bing bombarded with requests – appearing to the CDN server (not our Cloudflare DNS or actual VPS) as a DDoS attack and they we blocking us (and only from Italy – our closest server that I would access hence no one else can see the issue ever). It was basically appearing as constant bot attacks. If you want i can send you the logs?
I have adjusted some CDN config settings and got them to remove any permanent block, and for the last couple days, all has been working fine again.
I am in the process of shifting our Tours to a new template anyway, and will delete this Element. I am worried as the NEW template is actually a little larger (has more fields and query loops).
However, I am hoping you can tell me (or have a quick look at the templates in question) if this is normal or expected behaviour for a Block Content Element of this nature? Or have I done something fundamentally wrong to cause this?
I added both to the Private Info box. -
The template is using a lot of queries and pulling many post meta from ACF.
However, for the question of whether it’s going to have an issue, I think it depends on the capacity of your server. I would recommend checking with your host.
- You must be logged in to reply to this topic.