won’t prebuild cache on one site (rare scenario)

Who is it hosted with? Same as the others?

Hosted on my VPS. And yes, other sites on the exact same server have no problem caching.

Same problem. I found that for one site it didn’t create the table wp_swift_performance_warmup in the DB. I then created the table manually but it still doesn’t create the cache and the settings are exactly the same as on another site which works fine.

I also tried deleting and re-installing but no difference.

When I ran the install wizard on the site which it doesn’t work it didn’t ask me for my account details so whether that has got anything to do with it?

• This reply was modified 6 years, 7 months ago by applejack1923.

When did you install the plugin the first time? When did you notice this behavior? When you uninstall / reinstall, did you check htaccess to see if rewrite rules were deleted? We are trying to nail down a bug. The more info the better.

Installed today on 3 sites 2 working one not and yes htaccess is correct. They are all on the same server which is mine as it is a dedicated.

• This reply was modified 6 years, 7 months ago by applejack1923.

Same. Maybe a nginx thing?

When looking in the /wp-content/cache/swift-performance/ folder it is empty.

Edit – was missing nginx helper, once added that plugin I can see all post types except pages are now cached, still not sure why pages won’t cache but they appear to load much faster as if they were.

• This reply was modified 6 years, 7 months ago by pingram.
• This reply was modified 6 years, 7 months ago by pingram.

My site with the problem is on regular apache.

• This reply was modified 6 years, 7 months ago by treeflips.

I am getting these types of error messages in the debug log.

2018-04-05 03:04:20 [Error] Prebuild cache stopped due an error: cURL error 28: Operation timed out after 120000 milliseconds with 0 bytes received ( Memory:17.46Mb CPU:13.20% )
2018-04-05 03:04:26 [Error] DOM parser failedURL:/grants/, Request:a:0:{} ( Memory:13.40Mb CPU:12.32% )

Now solved!

Tactics that worked (but not always):
– temporarily changing htaccess permission to 755 during install (then back to 644 again)
– reinstall SWIFT
– clicking around random settings…changing cache modes from INTELLIGENT to TIME-BASED

Tactics that didn’t work:
– deleting cache folders in FTP
– reset warmup table, and prebuild cache
– change options

I wouldn’t exactly say solved more pot luck that you got it working. It needs to be sorted as to why it sometimes doesn’t work as I have had this now on 2 different sites which I really hope it can be, as when it does work this is a fantastic plugin.

Is there a way of completely getting rid of this in terms of any and all data so I can try a complete re-install ?

It is a fantastic plugin and it will be solved. Troubleshooting random issues is one of the most difficult jobs to tackle, but it is actively being worked on as we speak. Thank you everyone that has given input so far.

Thanks for the update and yes I can appreciate because of it’s random nature it makes it more difficult to sort. If there is anything I can help with let me know.

Sorry, I need to fix my answer above. I meant to say…
– changing cache mode from intelligent to ACTION-BASED! (this seems to be the best option, anyway)

@applejack1923 the plugin is usually pretty good about cleaning up after itself, but if you want to check it you can uninstall the normal way through wp-admin dashboard. You will need to get in your hosts cpanel / file manager or ftp program. Check the htaccess file to make sure all re-writes related to swift are gone. Then go to wp-content > cache and check for a ‘swift performance’ folder. If the folder is there, you can delete it. That will give you a clean space to re-install.