iThemes 6.2.0 update causing fatal failure on Windows

@brendonmills

Any additional info in the web server error_log ?

Here too.

After update from 6.1.1 to 6.2.0 –>> 500 internal server error.
Downloading 6.2.0 and manually replacing files via ftp does not help either.

Sorry unable to provide additional info/logs
But i′m on linux shared hosting, not windows.

Where can i download 6.1.1 again? (wp repository is already updated to 6.2.0)

• This reply was modified 7 years, 8 months ago by tmf33.
• This reply was modified 7 years, 8 months ago by tmf33.

[Wed Mar 15 14:30:16 2017] [alert] [client 81.19.xxx.xx] /home/.sites/32/sitexxxxx/web/xxxxx/.htaccess: Options not allowed here, referer: https://www.abc.com/wp-cron.php?doing_wp_cron=1489584616.6276669502258300781250

and

[Wed Mar 15 15:17:23 2017] [alert] [client 212.186.xx.xxx] /home/.sites/32/sitexxxxx/web/xxxxx/.htaccess: Options not allowed here, referer: https://www.abc.com/wp-admin/admin.php?page=itsec&module_type=recommended
[Wed Mar 15 15:31:28 2017] [alert] [client 212.186.xx.xxx] /home/.sites/32/sitexxxx/web/xxxxx/.htaccess: Options not allowed here, referer: https://www.abc.com/

renaming (= disabling) .htaccess gets the site + backend working for now.
But of course not the best/safe option
(renaming better-wp-security folder = disabling without any result, still 500 internal error)

• This reply was modified 7 years, 8 months ago by tmf33. Reason: mask pers. details
• This reply was modified 7 years, 8 months ago by tmf33.

While not on Windows, a server setup that uses a lot of symlinks had a similar problem today. We had to revert back to 6.1.1.

We got some very strange error messages, like:

Cannot declare class , because the name is already in use in /blah/plugins/better-wp-security/core/modules/system-tweaks/settings.php on line 0

^ Yes, “class ,”.

require_once(): Failed opening required '????' (include_path='.:/blah') in /blah/plugins/better-wp-security/core/modules/system-tweaks/class-itsec-system-tweaks.php on line 68

It seemed to be further exacerbated by an internal caching mechanism that was caching admin requests, but that’s unconfirmed.

Same here:
after update to 6.2.0 I got an internal server error when trying to access the site.
Apache log says:
.htaccess: Require not allowed here

Inside the .htaccess file: if I comment out the iThemes section called “Protect System Files…System Tweaks”
and restart apache the error will go away.

@tmf33

Check out this solution for the error: Options not allowed here.

(Enabling the Directory Browsing setting in the System Tweaks module adds the lines below to the .htaccess file:

# Disable Directory Browsing - Security > Settings > System Tweaks > Directory Browsing
Options -Indexes

)

The iTSec 6.1.1 release can be downloaded from here.

• This reply was modified 7 years, 8 months ago by pronl.
• This reply was modified 7 years, 8 months ago by pronl.
• This reply was modified 7 years, 8 months ago by pronl.

@pronl

Thanks mate! Will check it out..

You rock! ??

Check out this solution for the error: Options not allowed here.

Accordingly, the “.htaccess: Require not allowed here” error will go away, if You put “Allow Override All” into your apache config.

Question remains why it worked before without that rule.

hmm well right now i′m not able to get even itsec 6.1.1 working again
(has worked all well till the 6.2.0 update)

Have removed/renamed itsec folder and removed itsec from .htaccess. (The latter did the trick to bring up my site again)

@photongui

Perhaps your hosting provider coincidentally switched from Apache 2.2.x to 2.4.x.

Do note the correct syntax is:

AllowOverride All

Anyway there can be any number of reasons.
The important thing to remember is that these are Apache configuration issues.
It’s not something the iTSec plugin is doing wrong.

People tend to point towards the last change they made as the cause of troubles.
However there is a whole stack of technology behind a WordPress site.
Anything in that stack (MySQL, PHP, Apache, WordPress, plugins, themes etc) can change any moment ??

Totally agreed – thanks for pointing that out.

However.. I love when things just flat out work.. if after an upgrade the site is down.. the easiest way is to blame and remove that plugin (by altering any config or other parts of that ecosystem could start making troubles somewhere else)