Thread

I just switched hosting plans and with the migration of my site to this new server, I’ve been getting some wonky errors, the latest of which is this:

[Thu May 10 21:24:23 2012] [warn] [client xx.132.87.152] mod_fcgid: stderr: PHP Fatal error: Call to a member function masked_url() on a non-object in /var/www/vhosts/xx.net/httpdocs/system/expressionengine/libraries/Filemanager.php on line 888, referer: https://www.tableture.net/index.php/setup_wizard/publication_profile
[Thu May 10 21:27:31 2012] [warn] [client xx.132.87.152] mod_fcgid: HTTP request length 137900 (so far) exceeds MaxRequestLen (131072), referer: https://www.tableture.net/index.php/setup_wizard/publication_profile

Users must be logged in to reach this page, which is a Safecracker account setup form, and it was never an issue that came up before on my shared hosting plan. Any ideas on what might cause this? Anyone seen something like this before? Is there a server setting that might need to be changed?

The two are very possibly related - for the second error, I’ve had this a few times on a new VPS running Plesk.  You need to increase the MaxRequestLen value as the default is really low (128Kb).

To you this, you will need root access via terminal to the server, and you’ll need to edit the file:

fcgid.conf

...then add a new value (or change the existing setting, if there is one):

FcgidMaxRequestLen 1073741824

Now restart Apache on the server and try again - hopefully that will kill both errors in one go.

See also: http://forum.parallels.com/showthread.php?t=112735

Hi tableture,

Indeed, Dan set you on the right path. Can you check the values as he described? If you need assistance with that, you will have to contact your hosting provider.

Let me know if you still see the errors after making the changes.

Cheers,

Thanks for the advice - It definitely fixed the memory error, but I’m still getting the masked_url warning. Anyone have additional thoughts on that?

Hi tableture,

Can you double check the steps in Moving ExpressionEngine to Another Server?

Google indicates those errors are related to file paths being incorrect, so look closely at Step 9.

Cheers,