My issue was with mod_ruid2 not accessing session file/data.

Ask your host to install EasyApache4 with MPM ITK. This is a replacement for mod_ruid2 and recommended for servers running CentOs 7. Learn more here:

https://documentation.cpanel.net/display/EA4/Apache+Module%3A+MPM+ITK

EasyApache4 has been great for me.

Best of luck to you as this was extremely frustrating for me.

SOLVED: Installed EasyApache4 with MPM ITK on server. Issue was with mod_ruid2 not accessing session file/data.

Mod_Security wasn’t showing a hit in logs as a it would for a normal hit, rather server wasn’t allowing site to access session data.

Why this anomaly happened only on this individual site, I may never know.

Installing of EasyApache4 with ITK solved the issue.

The mod_ruid2 Apache module changes the permissions of the HTTP requests for a domain to the permissions of the owner of that domain.

Warning:
If you do not select an Apache module that changes the permissions of Apache requests, your Apache web server will run Apache processes as the nobody user, which presents security risks. The following Apache modules also change the permissions of Apache requests:
mpm_itk_module
suexec
mod_suphp

—QUOTE——-

Bogdan: Most of the times, hosting features such as security, caching, optimization is not recommended to be used as they will conflict with WP. Disable any hosting related “features” and install WordPress specific tools to take the hosting solution’s place.

—-/QUOTE——-

As a humble host with many wordpress installs, I strongly disagree with Bogdan. In today’s day and age, you need all the security tools at your diposal.

Wordpress security measures should be used in conjunction with server security measures such as Mod_Security and ConfigServer Firewall.

I do appreciate Bogdan and everyone who contributed to this thread in an effort to help me get tagDiv composer working. Now that I’ve recreated a few Visual Composer pages in tagDiv Composer, I can’t see that I’m any better off. I trust tagDiv’s advice that the transition will pay dividends in the future.

I just hope supporting the new tagDiv Composer plugin doesn’t hinder their effort in providing the best publishing platform WordPress has to offer.

Elmer
RheaReview.com

• This reply was modified 9 years by elmer.harris.

UPDATE:

Disabled Mod_Security on site and now works.

Any idea what Mod_Security rule could have been causing the login redirect loop with composer activated?

BTW, I just overwrote all wordpress files.

Strange thing is… I don’t get the redirect loop timeout when I activate td_composer with twenty-twenty, only when using Newspaper theme (which is a clean install of the theme).

Mayapur Voice,

Changes to core files are what’s concerning me most now. I’m unable to locate the culprit and have already changed to vanilla .htaccess and wp-config.php

Does anyone know any other files that could cause this err_too_many_redirects ??

I installed Newspaper on test site on same server and tagDiv works on fresh install. Just can’t figure out what file or setting is screwed up on main site.

Thanks Chris!

I installed wp-optimize and deleted transients. Likely a good thing, but didn’t fix my problem. Also resaved permalinks.

thanks again

I have eliminated the issue down to strangely enough, the “Newspaper” theme.

I can enable td_composer with standard wp theme, but it seems to have this redirect issue when logging into dashboard or login page only when “Newspaper” theme is installed.

Again, all plugins disabled using default .htaccess and wp-config.php files.
I’m running on a dedicated server with cPanel and CloudLinux installed. All systems go in Newspaper’s System Status in theme panel.

Question… could there have a been a theme update in the past 10 months that would have made a database change? I deleted entire “Newspaper” directory and re-uploaded new folder with version 8.

I have nothing else to eliminate. Or do I? Maybe I can reupload a fresh wordpress install.

What should I do?

Update: I converted multisite install to single site. No dice. Problem with “err_too_many_redirects” continues when tagDiv Composer is activated.

Thing is… I have a lot of plugins (currently disabled) that has never caused this problem. None of tagDiv’s other plugins have ever caused an issue.

So currently, all plugins are disabled. The following files have been reverted to default: wp_config.php and .htaccess

The problem still persists but only when I activate tagDiv Composer by itself.

Next step is to try tagDiv composer with twenty-twenty them.

I’d appreciate any help or suggestions from support or community at large.

thanks

Elmer

I guess I found out the hard way. I implore you add this disclosure to upgrade instructions. I also find it beyond the pale with 40k+ users, you didn’t test this major release on a multisite install.

You cost me two days I’ll never get back.

BTW, my multisite environment was not created with a plugin.

Catalin,

Thanks for your help. It looks like spelling out “Dayton, Tennessee, USA” is the way to go. I believe I was abbreviating the state which causing the issue.

Your help is much appreciated.

Thanks again,

Elmer

Hi Catalin,

My location is Dayton, Tennessee, USA

What should I put and where should I put it to get the correct readout?

thanks in advance for any help,

Elmer