So i'm working with the wpmudev snapshot plugin which gives an 'max_execution_time' warning (30 is to low), when I update this to 180 by adding
php_value max_execution_time 180
to the .htaccess file (wp root) my site gives an internal server error. Is there an reason why this happens? And how can I fix this?
your code is correct and refer below scenario,
Check with your error log and if it is a PHP error try to troubleshoot that.
what is your server engine, because Apache engine only have .htaccess file others like nginx not support .htaccess file
If not got solution check with your hosting before that make sure your site not have an issue.
Related
I have a wordpress site with Yoast SEO plugin. The plugin generate's my sitemap_index.xml but i cant access some of them.
I can access my post-sitemap.xml and category-sitemap.xml.
But i can't access my tags XML (post_tag-sitemap.xml). It gives error 500.
This is my eeror log:
PHP Fatal error: Allowed memory size of 268435456 bytes exhausted
(tried to allocate 72 bytes) in
/home/******/public_html/wp-content/plugins/wordpress-seo/inc/class-sitemaps.php on line 439
I already tried to change the define('WP_MEMORY_LIMIT', '64M'); in my wp-config.php with no success.
I already tried to decrease the number of items in Yoast Sitemap plugin with no success.
Can someone help me?
This solution woked perfectly with me couple of times:
if (!defined('WP_MEMORY_LIMIT'))
define('WP_MEMORY_LIMIT','128M');
If still facing the problem add this line to wp-config.php:
define('WP_MEMORY_LIMIT', '64M');
If the kept appearing create php.ini file in your site root (usually www, public_html or htdocs folder) and add the following line:
memory_limit = 64MB
Goodluck.
Source WPAPI
A friend of mine asked me to move wordpress website from development server to production. I've copied all the files, backed up and restored database. After that I'd changed sitename and home values in database (_options table) to new domain and it started. Though only home page is working fine. When I navigate to any other page it gives me 500 error. In error_log I got following errors:
1423021301: /home1/crankst1/public_html/fish-dev-site/ssv3_payload_extractor-r0Xkqq2xFD.php startup
[24-Feb-2015 19:16:59 UTC] PHP Warning: require_once(/home1/crankst1/public_html/fish-dev-site/wp-content/plugins/js_composer_theme/include/classes/core/class-vc-sort.php): failed to open stream: No such file or directory in /home1/crankst1/public_html/fish-dev-site/wp-content/plugins/js_composer_theme/js_composer.php on line 168
[24-Feb-2015 19:16:59 UTC] PHP Fatal error: require_once(): Failed opening required '/home1/crankst1/public_html/fish-dev-site/wp-content/plugins/js_composer_theme/include/classes/core/class-vc-sort.php' (include_path='.:/usr/php/54/usr/lib64:/usr/php/54/usr/share/pear') in /home1/crankst1/public_html/fish-dev-site/wp-content/plugins/js_composer_theme/js_composer.php on line 168
Paths that cause errors are related to development server and I can't find where to change them. I'm not very good with wordpress, so I suppose that solution should be very simple.
I'm sure there is an issue with a plugin http://codecanyon.net/item/visual-composer-page-builder-for-wordpress/242431/comments?page=149 try to see if there are any hardcoded paths on the plugin dashboard.
Delete your .htaccess file then go to the permalinks page change to another permalink type save page then change back to permalink you had this will force wordpress to recreate the .htaccess file and it will allow all pages you have to show correctly on the site. :-)
I have been look around trying to get this working right for a while now, and finally bit the bullet and posted here.
I've got a LAMP stack with ModSecurity using the OWASP core rule set (v 2.2.5) and just installed Wordpress. I expected conflicts with ModSecurity, but I haven't been able to ignore or work aroudn the only error I've encountered so far.
The Apache error.log file and the modsec_audit.log both list the same error:
ModSecurity: Rule 7f5d9a449228 [id "950901"][file "/etc/modsecurity/owasp-crs/activated_rules/modsecurity_crs_41_sql_injection_attacks.conf"][line "77"] - Execution error - PCRE limits exceeded (-8): (null).`
I've tried creating a new .conf file where the crs conf files are located containing
<LocationMatch .*>
<IfModule mod_security2.c>
SecRuleRemoveById 950901
</IfModule>
</LocationMatch>
and even removed the IfModule statement and then LocationMatch statement when it didn't work.
Finally I resorted to commenting out lines 76 and 77 in the .conf file, and the error still appeared. This also had no effect.
Only changing SecRuleEngine to Off in modsecurity.conf finally let me access the page. Of course this defeats the purpose of ModSec.
Where am I going wrong?
Try adding this to your php.ini file (or included conf file):
pcre.backtrack_limit = 10000000
pcre.recursion_limit = 10000000
And then this to your modsecurity.conf:
SecPcreMatchLimit 150000
SecPcreMatchLimitRecursion 150000
This should allow for recursion without having to fully disable mod_security.
I have problem with my server configuration. I use Apache 2.216, PHP 5.3.3 and wordpress 3.4.2 with Shopperpress. Time to time I receive error "client denied by server configuration: path/to/file" in apache log file. It is path to _tbs.php file, but it is not problem in rights of file, because this file is called 12 times on page for getting thumbs of photos and there is error only several times. I think that it has no connection to concrete photo, because once this photo is displayed corectly and next time same photo produce error.
Do you have any idea what can be reason?
Thank you for all advices.
Viktor
I think thats a problem by the configuration of MaxClients or MaxRequestsPerChild.
Try to restore the default configuration and try it again. If that not works, reinstall Apache and purge the old configuration.
You have given very little information. It is not clear under what conditions do you work (OS, installed modules, Log entrys,...).
WordPress 3.4.2 is very old and safety-relevant. Please update WordPress and your WP-Plugins.
Go to you VHOST-file and replace:
Deny from all
Allow from 127.0.0.0/255.0.0.0
with:
Require all granted
This cause for old Config-Files and newer Apache-Version. Since Apache 2.4.3 a new security feature is added.
Most htaccess 404 error rules are based on an absolute directory location, eg /404.php. I want one that is relative to the location it's placed in (so when I transfer from test environment in WAMP to live, I don't have to hope I edit the file right).
Unfortunately,
ErrorDocument 404 404Error.php
Just prints out 404Error.php to the browser, it doesn't call the actual error page like
ErrorDocument 404 /FOOBAR/404Error.php
does.
Edit:
I guess I wasn't clear enough. Test environment is a WAMP local server, with the error file at /FOOBAR/404Error.php while the 'live' server would be www.fubar.com/404error.php -- placing it in the root.
How's this?
ErrorDocument 404 ../directory/404page.html
RewriteBase /FOOBAR/
ErrorDocument 404 404Error.php
This works too, but Tycho's solution is a bit more elegant. Only use this one if you don't plan on using .htaccess for anything outside of /FOOBAR/ pretty much.