This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.
Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
|---|---|---|---|---|---|---|
| - | 9:00 – 12:00 | 9:00 – 12:00 | 9:00 – 12:00 | 9:00 – 12:00 | 9:00 – 12:00 | - |
| - | 13:00 – 18:00 | 13:00 – 18:00 | 13:00 – 18:00 | 14:00 – 18:00 | 13:00 – 18:00 | - |
Supporter timezone: America/Jamaica (GMT-05:00)
I am trying to build a website using toolset types and the beta version of views.
hidden link
After the initial install of Toolset types, I got a server error 500.
When refreshing the page, the plugin was installed correctly.
Over the next few hours after installing the plugin and working with toolset, the server errors got more frequent.
I completely removed WordPress and all plugins, emptied the database and started from scratch.
After installing WordPress again, installing the toolset plugin, the problems were the same (and sometimes even more frequent).
I contacted my hosting (Combell.com) and they had a look al the logs and they noticed this:
[Tue Oct 15 13:47:56.635194 2019] [error] [pid 27574] mod_proxy_fcgi.c(676): [client 217.21.177.71:58293] AH01067: Failed to read FastCGI header
[Tue Oct 15 13:47:56.635215 2019] [error] [pid 27574] mod_proxy_fcgi.c(980): (104)Connection reset by peer: [client 217.21.177.71:58293] AH01075: Error dispatching request to :
They informed me that this happens when there is a problem with the communication between the PHP service and Apache.
I looked up the requirements of Toolset and from what I can tell, everything is present in my hosting.
I have the Essential hosting:
hidden link
The normal PHP memory_limit is 128 MB.
I have attached the different settings from my hosting.
After the intial ticket, they restarted the services and everything was fine for a couple of hours. After that, the server errors began again. I was in the process of creating post types, custom fields, designing archive pages, and the single post display when it stared happening again.
For testing purposes, they have just at the time of writing this text temporarily upgraded my hosting to Professional to see if the problem persists. That is why you will see 265MB in the debug info below.
The solution they suggest is testing if the problem persists on their professional package for a few days.
But seeing as there is a significant added cost to the professional package, I want to be 100% sure that I am unable to run toolset with their Essential hosting.
Could you please advise?
Best,
Kenny
