a305587

Figured it out, it was something bigger. Web host had its own cache that we didn’t install, configure or know about. Once they flushed, the maintenance mode re-appeared.

Thank you for the responsiveness and support.

Thanks for the response.

No caching plugins are being used (this is a brand new site), tested in purged cache incognito windows, and the problem happens on devices and browsers that have never pulled up this url before (and don’t have wp cookies).

Might be a bigger issue. The elementor maintenance mode doesn’t work either as well as none of the other maintenance mode options in the plugin library.

I think there’s something with the site that is blocking whatever it is that makes maintenance mode work.

Aha, I see the issue.

Thank you for the response and link to your helpful webpage on the matter. This is clearer now.

Cheers!

Thank you for the response.

We have three users and everyone has been actively using Google Authenticator successfully.

It’s just the newly created user who is not being presented with a QR code. It’s as if the site thinks they have already set it up.

Update: Odd. The user was able to click through the login bypassing the 2FA field and get in without the code. It took them directly to the QR code scan page where they were able to set up 2FA.

I guess disregard? Although I’m wondering how one could bypass the 2FA…

I will echo this. I manage > 2 dozen websites and Wordfence is barking up a storm about the changes you made to your plugin. If you make a change and don’t commit to official WordPress plugin repo, Wordfence does not get a copy and if you did not know, they check against official version. Since a file has changed, WF thinks potential attacker activity is taking place.

I’m getting this warning 30 times so I know it’s obviously an update RSSL made, but agreed with OP I would stick to major release update patches to avoid this in the future. If a single site user gets this warning from Wordfence they will think they’ve been hacked or your plugin has been compromised.

Cheers. Love your work.

• This reply was modified 4 years, 5 months ago by a305587.

Thank you, this was helpful.

Cheers!

Thank you very much, this solved our issue.

BTW, this is an excellent plugin. We trialed several forum plugins and found WPForo to be the best. Top marks!

Edit: Left a 5-star review btw, thank you again!

• This reply was modified 4 years, 9 months ago by a305587.

Who is your webhost? Are you on a shared server or VPS?

Might be your webhost. I was using SiteGround and they have an upstream auto updater which overrides Companion Auto Update.

I generally love SiteGround but their autoupdate service is a very frustrating thing, and getting them to shut it down to use this plugin is like getting Congress to pass a bill.

Check Companion Auto Update Plugin Settings –> Status tab. Is it a green dot or red dot?

Hey Tom,

Thanks, figured it out. Using a child theme, added templates. That user control box auto-appears when I add templates.

Side note: Didn’t realize you made the Simple CSS plugin as well, just connected the dots on that one. I’ve been using that plugin for a while now, it’s served us well over the years. One of my favorites. Thank you.

I went ahead and purchased GeneratePress premium. Appreciate what you’re doing, want to support. Cheers.

Hello Gerroald,

Thank you again for continuing attention. All sites are on a single Bluehost VPS, however they are split between two cPanels. We have control up to WHM level.

Regards

• This reply was modified 5 years, 1 month ago by a305587.

Hello Gerroald,

Thank you for your continuing attention to this matter.

This particular issue is affecting every site under our purview (~15 sites across multiple servers) and we have a variety of plugins installed on each site. There are overlaps in the plugins used on each site, however there are many differences depending on the website’s mission.

I’ll pick one site for your query (same one used above from the error log):

* Advanced Custom Fields PRO
* Classic Editor
* Companion Auto Update
* Custom Post Type UI
* Ivory Search
* Jetpack
* LearnPress
* Post Snippets
* Really Simple SSL
* Shortcoder
* Simple CSS
* Slimstat Analytics
* UpdraftPlus Backup/Restore
* Wordfence Security
* WP Crontrol
* WPForms
* WPForms Custom Captcha
* Yoast SEO

These are the only plugins we have installed on every site (common denominators):

* Classic Editor
* Companion Auto Update
* Really Simple SSL
* UpdraftPlus Backup/Restore
* WordFence Security

Thank you again.

Thank you Gerroald, I appreciate your time. I have submitted the report via email.

I did not obfuscate the IP address, it actually comes through as that on the error log. And it appears to do this for most entries. I did obfuscate the URL of my site for public display here (although this will be visible to you in the emailed report).

I did try changing how WordFence gets IPs to the 2nd option (Use PHP’s built-in REMOTE_ADDR), but this did not appear to fix the issue. When I checked the error log afterward I was still seeing the errors.

A note on the error logs when you view the emailed report: When I make a change to the settings, I reset the error logs by appending the date to the end of the file. So for example when I tried changing a setting in WordFence on 9/23/19 to test if it fixed the issue, I wanted to reset the error log, so I renamed the old error log “error_log-092319”. I’m explaining this so when you get said report you’ll understand the meaning of all the error logs and the numbers after them. ?? The error log without a number after it is the current one. Most recent change attempt was me changing how WF gets its IP addresses.

Thanks again for taking the time to look into this, I appreciate your help sir.

Sorry, I missed notification on Mark’s original response.

Thank you Mark, and Rogier. I attempted the fix in Mark’s shared link by manually inserting “$_SERVER[“HTTPS”] = “on”;” into the wp-config and this fixed my problem. For some reason this was not inserted prior, but putting this in did fix my problem.

Thank you very much!