php7.2 502 error

Does anyone know how to trigger the errors so I can test the fix?

In the wp-admin area, goto Events -> Settings, Advanced Settings -> Cache Report… now be careful, if you bonk the “check again” you can whitescreen your site for non-logged in users getting uncached hits.

Nope! No dice. Still getting the 502 randomly. I’ll keep digging.

So, to be clear @redearryan, you changed the caching setting but have not tried explorador20’s fix.
Thank you,

Correct – but I’m familiar with the way/reason for his work around. I naively assumed that it was *just* the JS caching, started digging into more of the code and holy smokes! Lot’s of caching on the file system! We’re gonna need more checkboxes xD

I’m wondering how effective it would be temporarily to just have that _cache method simply return false… at least to stop the bleeding.

@sunny454
When i checked the cache report as advised by @redearryan i get this error. Is it relative to our other issues? “Templates cache is not writable”
I get that error with the JS Cache is turned off or on.

• This reply was modified 5 years, 9 months ago by great-taste.

I am seeing a 502 error when JS Cache is turned off or on.

Yep – I saw them return shortly thereafter. It did fix some things, but then there must be a cronjob that comes in and starts rewriting caches and whatnot. One thing I’ve been meaning to try is to turn of WP Cron by adding the following line to the wp-config.php file:

define('DISABLE_WP_CRON', true);

If you need cron still, I know WPE has a process where they’ll hit the wp cron url locally. I can’t remember if that happens in an authenticated fashion though… so again, no promises.

In the 11th hour last night, I finally disabled ai1ec to get the site up to php7.2 =\

This does boil down to write permissions from unauthenticated requests though; Can’t write executable files to disk when the requests aren’t logged in. This is a bit of a pickle considering how ai1ec works.

Feels like this could be handled a little more gracefully by checking first if is_writable and if is_readable when caching to prevent the fatals beforehand. I’d dig deeper, but I got deadlines! D=

• This reply was modified 5 years, 9 months ago by Rohjay.

Has anyone tried explorador20’s fix? Please let us know your results.

Hi @great-taste,

If it’s referring to a specific folder, set the permissions of that cache folder to be writable by setting the permissions to 755.

@sunny454 what are you referring to in your comment, “If it’s referring to a specific folder, set the permissions of that cache folder to be writable by setting the permissions to 755”? Is this in reference to my other support thread regarding robots.txt?

• This reply was modified 5 years, 9 months ago by great-taste.

Hi @great-taste,

No it’s not in relation to robots.txt. I’ll need the exact error message. I believe your error message is telling you a specific cache folder is unwritable. Changing the permissions will make it writable, eliminating this specific problem. You can do it using an FTP program or if you are unfamiliar with that, you can ask your hosting support to do it for you.

Ahhhh. Templates Cache. Thank you,

After resetting my permissions and resaving my config file, my templates cache is now working properly. No idea if it’s relative to the 521’s or segmentation faults – i don’t think so but fingers crossed.

Hi @great-taste,

Not related and was just a minor mishap. You should be fine in regards to this particular error now.