destilwell

So, I had my hosting company install a new ssl certificate on the site in question. I then deactivated really simple ssl and activated the easy https plugin instead. Site didn’t break, so that was nice after the warnings, lol.

Reactivated the after login redirection plugin and tested the login from the front side of the website. It worked! And I learned an important lesson about reading the forums. This issue was covered before and I didn’t use the advice about the Easy Https plugin because I thought it should have worked the same as the really simple ssl plugin, but that is not the case.
Reactivated Jetpack, login redirection still works as it should. Looks like all is well again!

Thank you for taking the time to address my questions and concerns. ??

Okay, this might be of importance. Duplicate site is running as http and not https. I use the really simple ssl plugin, but it seems a recommendation a couple of months ago is to use the Easy https plug in. Should I remove that before trying the other one? It seems they might conflict as they are similar in scope of function.

• This reply was modified 3 years, 10 months ago by destilwell. Reason: added really simple ssl plugin information
• This reply was modified 3 years, 10 months ago by destilwell.

Update: I used the wp migration tool to pull down a copy of the site in question, and used the same plugin to install it on a fresh wordpress install on a subdomain. Before changing the theme, I tried to duplicate the error by reactivating jetpack and the redirection plugin. Site worked fine. So I haven’t tried using a new theme because the duplicate site works.

If you have a suggestion, I’d be grateful.

• This reply was modified 3 years, 10 months ago by destilwell. Reason: Wrong about second site

Thank you for responding. This is a site with a paywall and I don’t want potentially run into problems switching the theme and switching back. I can try downloading a copy and setting up a staging site where I can change the theme, reactivate the plugins, and see if the problem is duplicated.

Jetpack had an update on the 12th. Wondering if that has something to do with the problem? I was only using the brute force protection offered, and have installed Login Attempts Limiter Reloaded instead, with no issues so far.

I’ll try the staging site later (2 am here) and get back to you. Thanks!