Dave McHale on "500 - Internal server error"

September 11, 2015, 11:21 am

≫ Next: IngridLissette on "500 - Internal server error"

≪ Previous: Matthew on "500 - Internal server error"

$

0

0

IngridLissette: I would reach out to your web developer for assistance. It sounds like you have a user/password for the WordPress admin area, but those credentials will NOT get you access to your server via FTP. The "Response: 530 User cannot log in. Error: Critical error: Could not connect to server" is FileZilla's long-winded way of saying "user or password failed".

Without FTP credentials, you will not be able to log in using FileZilla to access your files.

Do you have access credentials to your GoDaddy hosting account? It is possible that you may be able to access your website files directly via some type of File Manager in their control panel, rather than use an FTP client such as Filezilla to connect.

---

IngridLissette on "500 - Internal server error"

September 11, 2015, 11:26 am

≫ Next: Dave McHale on "500 - Internal server error"

≪ Previous: Dave McHale on "500 - Internal server error"

$

0

0

yes I do have my go daddy log in . should I call them for this issue then?

Dave McHale on "500 - Internal server error"

September 11, 2015, 11:47 am

≫ Next: langermank on "[Plugin: dsIDXpress IDX Plugin] Dialog boxes are not loading (500 error)"

≪ Previous: IngridLissette on "500 - Internal server error"

$

0

0

No, I would still talk to you web developer first. Chances are they can look at your error logs to find out what specifically the 500 error is, and fix the issue once you know what's actually happening.

langermank on "[Plugin: dsIDXpress IDX Plugin] Dialog boxes are not loading (500 error)"

September 12, 2015, 3:36 pm

≫ Next: DS_Riley on "[Plugin: dsIDXpress IDX Plugin] Dialog boxes are not loading (500 error)"

≪ Previous: Dave McHale on "500 - Internal server error"

$

0

0

I'm having this same issue with the dialog boxes not working. I have the latest version of Contact Form 7, so I tried deactivating it and still having the issue. Any ideas of how to fix this? I also tried deleting it completely and re-installing..

DS_Riley on "[Plugin: dsIDXpress IDX Plugin] Dialog boxes are not loading (500 error)"

September 14, 2015, 10:07 am

≫ Next: edelen on "[Plugin: Wordfence Security] 500 Errors and memory/CPU overflow?"

≪ Previous: langermank on "[Plugin: dsIDXpress IDX Plugin] Dialog boxes are not loading (500 error)"

$

0

0

Hey Langermank,

Below are some trouble shooting steps I would recommend taking to see if this resolves the problem.

I would recommend that you try disabling all of your extra plugins that are installed to make sure that no other plugin is conflicting with ours. If this fixes it then you'll want to re-enable them one at a time to find the one that was causing the problem.

If you take the above steps and are still having issues then you'll want to check to see if this is a conflict with your theme design. To test this we recommend temporarily disabling your current theme and applying something default like Twenty Ten or Twenty Eleven. If this resolves the issue then you will need to follow up with your Theme Developer. You will want them to take a look at any PHP errors that might have generated. Our Plugin uses your template files to format the data properly and this type of issue normally occurs because of improper coding.

Please try checking these two things and let us know if you are still having any problems with the plugin so we can look into the issue further for you.

Please do not hesitate to contact us if you have any other questions or concerns regarding this issue or your account.

If the problem persists after the above has been tested please create a support ticket by emailing Support@diversesoltions.com

Please feel free to reach out to us via the following:

Customer Support:
Support@DiverseSolutions.com
p. 877.348.7654 Ext. 3

Sales:
Sales@DiverseSolutions.com
p. 877.348.7654 Ext. 1

Sincerely,
Riley

edelen on "[Plugin: Wordfence Security] 500 Errors and memory/CPU overflow?"

October 1, 2015, 6:52 am

≫ Next: nurenu on "[Plugin: Wordfence Security] 500 Errors and memory/CPU overflow?"

≪ Previous: DS_Riley on "[Plugin: dsIDXpress IDX Plugin] Dialog boxes are not loading (500 error)"

$

0

0

My site has been experiencing Apache server 500 errors due to too many active processes (according to my host). A quick check of what plugins might be causing this (using P3) shows WordFence regularly spiking in activity. In addition, it's consuming nearly half of all the server resources allocated to the site. Even cutting back its memory allocation to 128MB has done nothing. I fell back from Falcon to standard caching too, and that's not it either.

I wiped out the entire site and reinstalled. Cut the number of plugins running in half, and have followed traditional debugging practices for wayward plugins.

I'm at a loss to know what else to do. All signs show WordFence as the likely culprit.

Did the latest update introduce a bug? It wasn't until recently that any problems arose, and only WordFence and Akismet have updated recently among my plugins.

Thanks.

https://wordpress.org/plugins/wordfence/

nurenu on "[Plugin: Wordfence Security] 500 Errors and memory/CPU overflow?"

October 1, 2015, 9:53 am

≫ Next: WFMattR on "[Plugin: Wordfence Security] 500 Errors and memory/CPU overflow?"

≪ Previous: edelen on "[Plugin: Wordfence Security] 500 Errors and memory/CPU overflow?"

$

0

0

Also getting time-outs and Rackspace said it was due to Wordfence. Deactivated and running again.

WFMattR on "[Plugin: Wordfence Security] 500 Errors and memory/CPU overflow?"

October 1, 2015, 6:04 pm

≫ Next: edelen on "[Plugin: Wordfence Security] 500 Errors and memory/CPU overflow?"

≪ Previous: nurenu on "[Plugin: Wordfence Security] 500 Errors and memory/CPU overflow?"

$

0

0

Do you know if the increased usage is during Wordfence scans? Or while a lot of IP addresses are being blocked? If there is an attack going on, then Wordfence would be doing more work, in logging the IPs to block.

If it is during scans (or if you are not sure when it happens), can you check if you have any of these enabled on your Wordfence Options page?
* Scan files outside your WordPress installation
* Scan image files as if they were executable
* Enable HIGH SENSITIVITY scanning
* Enable debugging mode (near the bottom of the page)

Usually you can disable these, if you've turned them on in the past -- for most sites without a current infection, they shouldn't be necessary.

(If you scroll through the scan summary on the Scan page, you can see the start and end times of the last scan, to see if it is taking a very long time.)

I don't know of any new bugs that are causing excess CPU or memory usage. Do the "500" errors show any other text, if you've seen them yourself? Or if not, can you find any details in the site's error log file? (Often error_log or error.log, but the location and name varies by host.)

-Matt R

---

edelen on "[Plugin: Wordfence Security] 500 Errors and memory/CPU overflow?"

October 2, 2015, 8:59 am

≫ Next: dwinden on "[Plugin: iThemes Security (formerly Better WP Security)] 500 internal server error"

≪ Previous: WFMattR on "[Plugin: Wordfence Security] 500 Errors and memory/CPU overflow?"

$

0

0

Matt,

I ran P3 at different times and the results were the same, so I doubt that WordFence was in the middle of the same function every time. Not ruling that out, just less likely.

As for scans, no, I have none of those higher intensity functions enabled.

I have a another less trafficked site also running WordFence, and it too is consuming far more memory and CPU processes--just not enough to cause the site to shut down. Still, a concern. And again, this is an increase since the previous version.

The error logs show only that too much memory is being consumed. Sadly, it vaguely traces this back to the index.php file in WordPress, and all that tells me is that someone tried to hit the site, it attempted to load, and it failed due to memory restrictions--which we've determined are due to too many background processes.

My ISP, midphase, is saying that the site keeps spawning processes that then fail to close, eventually exceeding the server limits. The ISP raised those limits and all it did was permit more processes--which also failed to close, causing the same error. They can't tell me exactly what those processes are linked to, but since disabling WordFence and returning to my previous firewall plugin, the site has calmed down dramatically.

I hope that helps. Wish there were further details to provide.

dwinden on "[Plugin: iThemes Security (formerly Better WP Security)] 500 internal server error"

October 7, 2015, 8:28 am

≫ Next: liquidcross on "[Plugin: iThemes Security (formerly Better WP Security)] 500 internal server error"

≪ Previous: edelen on "[Plugin: Wordfence Security] 500 Errors and memory/CPU overflow?"

$

0

0

Yup.

dwinden

liquidcross on "[Plugin: iThemes Security (formerly Better WP Security)] 500 internal server error"

October 7, 2015, 8:36 am

≫ Next: liquidcross on "[Plugin: iThemes Security (formerly Better WP Security)] 500 internal server error"

≪ Previous: dwinden on "[Plugin: iThemes Security (formerly Better WP Security)] 500 internal server error"

$

0

0

Tried that, and the good news is that the site loaded immediately once I uploaded the new htaccess file. Bad news: after saving settings in iThemes Security (WITHOUT making any changes), it immediately breaks the site again and returns the 500 error. I don't know what in the htaccess file could have caused it.

liquidcross on "[Plugin: iThemes Security (formerly Better WP Security)] 500 internal server error"

October 7, 2015, 12:11 pm

≫ Next: dwinden on "[Plugin: iThemes Security (formerly Better WP Security)] 500 internal server error"

≪ Previous: liquidcross on "[Plugin: iThemes Security (formerly Better WP Security)] 500 internal server error"

$

0

0

After completely uninstalling the plugin, then reinstalling and checking off preferences one by one, I've found that the 500 error was caused if either of these two options are checked:

Banned Users: Hackrepair check
System Tweaks: Disable PHP in Uploads

Once those settings are written to the htaccess file...the 500 error shows up after the site is refreshed. The odd part is that BOTH of these options have ALWAYS been checked, from the first time I installed the plugin ages ago. The change I made this morning (the WPtouch exclusion noted above) actually did NOT add anything to the htaccess file. Just the very act of saving the file without changes was enough to do it, since the Hackrepair and Disable PHP functions were in there. I've since gotten the plugin settings back to where they were minus those two, and everything works fine after multiple saves to htaccess.

Makes no sense to me; any ideas? I'm contacting my webhost about this, too.

dwinden on "[Plugin: iThemes Security (formerly Better WP Security)] 500 internal server error"

October 7, 2015, 3:08 pm

≫ Next: liquidcross on "[Plugin: iThemes Security (formerly Better WP Security)] 500 internal server error"

≪ Previous: liquidcross on "[Plugin: iThemes Security (formerly Better WP Security)] 500 internal server error"

$

0

0

@liquidcross

The iTSec plugin HackRepair.com template files (*.inc) were fairly recently updated. Not a positive change so I recommend to disable the feature till iThemes produces a fixed copy ...
(Don't hold your breath ...)

There also was a recent change to the Disable PHP in Uploads feature. There is more info in this topic.

And finally you are absolutely correct the WPtouch exclusion itself does not add any specific changes to the .htaccess file.
Any changes to this setting are stored as an option in the database.

I guess one of the recent iTSec plugin update(s) (4.8\4.9\5.0.1) broke your specific configuration...

dwinden

liquidcross on "[Plugin: iThemes Security (formerly Better WP Security)] 500 internal server error"

October 7, 2015, 7:10 pm

≫ Next: dwinden on "[Plugin: iThemes Security (formerly Better WP Security)] 500 internal server error"

≪ Previous: dwinden on "[Plugin: iThemes Security (formerly Better WP Security)] 500 internal server error"

$

0

0

Thanks so much, that explains a lot. Strange that the Disable PHP in Uploads feature is listed as "fixed" in that other thread, when it sure as hell broke mine!

dwinden on "[Plugin: iThemes Security (formerly Better WP Security)] 500 internal server error"

October 8, 2015, 12:29 am

≫ Next: dwinden on "[Plugin: iThemes Security (formerly Better WP Security)] 500 internal server error"

≪ Previous: liquidcross on "[Plugin: iThemes Security (formerly Better WP Security)] 500 internal server error"

$

0

0

@liquidcross

The weird thing is that the line added to the .htaccess by the Disable PHP in Uploads setting does not break my env ...

I did not rename my wp-content folder.
Even if I did, I don't see how that could be a problem (assuming the bug as described in the other topic is indeed fixed).
Did you change your wp-content folder ?
Could you copy\paste the .htaccess line added by the Disable PHP in Uploads setting into the topic ?

Also I'm using Apache 2.4.x. What web server are you using ?

dwinden

---

dwinden on "[Plugin: iThemes Security (formerly Better WP Security)] 500 internal server error"

October 8, 2015, 1:40 am

≫ Next: dwinden on "[Plugin: iThemes Security (formerly Better WP Security)] 500 internal server error"

≪ Previous: dwinden on "[Plugin: iThemes Security (formerly Better WP Security)] 500 internal server error"

$

0

0

My .htaccess entry looks like this and it is perfectly valid:

<IfModule mod_rewrite.c>
RewriteEngine On

# PHP Uitschakelen in Uploads - Beveiliging > Instellingen > Systeem Tweaks > Uploads
RewriteRule ^wp\-content/uploads/.*\.(?:php[1-6]?|pht|phtml?)$ - [NC,F]
</IfModule>

dwinden

dwinden on "[Plugin: iThemes Security (formerly Better WP Security)] 500 internal server error"

October 8, 2015, 4:30 am

≫ Next: dwinden on "[Plugin: iThemes Security (formerly Better WP Security)] 500 internal server error"

≪ Previous: dwinden on "[Plugin: iThemes Security (formerly Better WP Security)] 500 internal server error"

$

0

0

It turns out the .htaccess RewriteRule for the Disable PHP in Uploads setting completely changed when updating from the 4.6.13 to the 4.8.0 release ...

However there is no mention of this change in the 4.7.0\4.8.0 changelog...
(4.7.0 is an internal build and was never released to the public).

dwinden

dwinden on "[Plugin: iThemes Security (formerly Better WP Security)] 500 internal server error"

October 8, 2015, 5:29 am

≫ Next: liquidcross on "[Plugin: iThemes Security (formerly Better WP Security)] 500 internal server error"

≪ Previous: dwinden on "[Plugin: iThemes Security (formerly Better WP Security)] 500 internal server error"

$

0

0

It turns out the .htaccess RewriteRule for the Disable PHP in Uploads setting completely changed when updating from the 4.6.13 to the 4.8.0 release ...

should be:

It turns out the .htaccess RewriteRule for the Disable PHP in Uploads setting completely changed when updating from the 4.6.13 (or older) to the 4.8.0 (or newer) release ...

dwinden

liquidcross on "[Plugin: iThemes Security (formerly Better WP Security)] 500 internal server error"

October 8, 2015, 5:41 am

≫ Next: dwinden on "[Plugin: iThemes Security (formerly Better WP Security)] 500 internal server error"

≪ Previous: dwinden on "[Plugin: iThemes Security (formerly Better WP Security)] 500 internal server error"

$

0

0

I'm running Apache (not sure which version); and I did not rename my wp-content folder.

The Disable PHP in Uploads entry in my htaccess file looks like this:

# Disable PHP in Uploads - Security > Settings > System Tweaks > Uploads
RewriteRule ^wp-content/uploads/.*\.(?:php[1-6]?|pht|phtml?)$ - [NC,F]

And I confirmed once more that it results in a 500 error on my site. Removing it brings the site back to normal.

dwinden on "[Plugin: iThemes Security (formerly Better WP Security)] 500 internal server error"

October 8, 2015, 6:10 am

≫ Next: liquidcross on "[Plugin: iThemes Security (formerly Better WP Security)] 500 internal server error"

≪ Previous: liquidcross on "[Plugin: iThemes Security (formerly Better WP Security)] 500 internal server error"

$

0

0

Only difference is the unescaped dash in wp-content.
I removed the \ in front of the dash from my .htaccess, but it still works. Could you manually add the \ in front of the dash and test to see whether it makes any difference in your env ?

Too bad you don't know the Apache version ... could also be relevant.

There must be an error in the Apache error_log that will tell us more ...
Contact your hosting provider ...

There really is nothing wrong with the RewriteRule (apart from not escaping the dash in wp-content).
But somehow your Apache env doesn't like the RewriteRule ...

dwinden