Hi,
That’s a new one. It’s not the same as a 500 error. A 500 error is sent by the webserver, and indicates that the PHP engine crashed when running the script. However, your error is not from the webserver level, but from the networking level. It indicates that something in between you and the webserver terminated the network connection.
It’s most likely that the web hosting company has some proxy setup that is doing that; but it could alternatively be at your end. You should test it from different network locations (i.e. a different computer on a different network), to try to find the commonality. If it is at the web hosting company’s end, then you should request support from them.
It would also be worth asking them where your PHP error logs are, and reading those. It’s possible that, despite what I said above, in their setup a PHP error triggers a network reset.
Best wishes,
David
Thanks very much for that answer. I have WordPress sites with another host, and your plug-in works beautifully there. I will contact my host and post an update here.
Thanks again 🙂
Hi again,
I got this response from my hosting company:
_____________________
It seems like the plugin is either not installed properly or the codes have problems. I have ran the php scripts manually and found the following errors :
Fatal error: Call to undefined function plugins_url() in /home/silverfl/public_html/wp-content/plugins/updraftplus/updraftplus.php on line 151
Fatal error: Call to undefined function add_action() in /home/silverfl/public_html/wp-content/plugins/updraftplus/updraftplus.php on line
244
Can you please check this with the developer? Hopefully, they have a better idea than us on this.
_____________________
Any ideas? Thanks again for your help!
Hi,
Sounds like your web hosting company doesn’t know much about WordPress! The component parts of WP plugins aren’t meant to be run directly, and any/every WordPress plugin will produce similar errors to those above if you attempt to do so.
It would be more helpful to know if any errors are logged in the host’s PHP error logs when the settings page is loaded in the ordinary way, i.e. through the WP dashboard.
Best wishes,
David
Thanks! I contacted my host and provided your response.
Okay, response from host:
_____________________
Nope there are no errors logged except for “[notice] child pid 3794 exit signal Segmentation fault (11)”
_____________________
Thanks again!!!
If that error is logged when the UD settings page loads, then it is significant. It means that the PHP engine crashed. A segmentation fault (segfault) is a low-level error (see: http://en.wikipedia.org/wiki/Segmentation_fault#Common_causes) – not something directly due to faulty PHP code as such; what version of PHP are they running? If it’s not the latest, then it may be an already fixed problem in their PHP install (see http://php.net/ChangeLog-5.php and search for ‘segfault’).
David
Hi again 🙂
I thought my host abandoned this issue, but they came back with this:
______________________
there is something wrong in the file
./wp-content/plugins/updraftplus/updraftplus.php string 253
add_action(apply_filters(‘updraft_admin_menu_hook’, ‘admin_menu’), array($this, ‘admin_menu’), 9);
this line causes the segfault
______________________
What do you think?
Thanks again!
Claire
Hi Claire,
If PHP segfaults, then it’s the PHP install that’s faulty; the particular line of code that triggers it is the incidental cause, not the final cause. (To give a simile, if your cylinder head is faulty, then pressing the accelerator was not the real reason why your engine overheats).
That particular line of code is the kind of thing you’ll find many times in a WordPress install; what your host needs to do is to find out the fault in their PHP install (though, in practice, this usually just means they’ll want to update it to a later version).
Best wishes,
David
And of course you were right about the problem being an outdated PHP install. My host has some incompatibilities with PHP, so the workaround they gave me was to add
AddHandler application/x-httpd-php54 .php
to .htaccess. It works now 🙂 Thanks so much for your responses and patience!
Claire
