Search results for query: *

Confirming that it appears to be working again. If you don't mind me asking, what was the cause of the issue?

I just want to confirm that the PM was received as I hadn't gotten a response in a couple of days.

We disabled all plugins aside from vBSecurity but were still having issues with the whitelist taking effect.

I will try that just to rule it out as a possibility, but no new plugins have been added since the OS change.

I did disable the 'exclude Super Administrator' option, but even with or without it enabled it was having no effect regardless of if someone is a Super Admin (we have ~50 people with Forum Admin; I don't necessarily agree with that number but I digress...) It doesn't prevent them from accessing...

Nothing from the forum itself was changed. The server was actually formatted and reinstalled with CentOS 7 (from CentOS 6).

We've always had CloudFlare's CDN enabled - I would think this would prevent logging into the AdminCP if it was reporting a different IP though, no? There have been some settings modified, but nothing that would effect the REMOTE_ADDR variable I don't believe. I did do a quick test to ensure...

Ever since we upgraded to PHP 7, the IP whitelist function no longer works, in that anyone can access the AdminCP regardless of if their IP is actually whitelisted or not. I have not seen any errors listed in the error log relating to this.

Looks like NTP was the issue and I've at least personally verified that the authentication is working properly again. Thank you for the help!

I did adjust PHP's server timezone to the same as the set server time (America/Chicago) and restarted Apache. Are there any particular ideas I should try?

That may be a bit difficult as we don't have a FTP server installed on the machine and only utilize SSH/SFTP for access, along with IP whitelisting for said access.

Up until recently, I hadn't been having any issues with 2FA on our forums, but now when anyone attempts to enter a code from the code generator to the forums, it gives them the 'Invalid authentication code' error. I verified that the system time was set correctly as referenced in this thread...

I have verified that I tested this against the latest version of Chrome. It may be a conflicting plugin that's causing this, but I am unable to test that at the moment.

It seems as though inputting an invalid URL into the URL BBcode in a shoutbox causes the page to crash in Google Chrome. Example code: asdf

Odd, it appears to be working properly again, though I didn't make any changes (there weren't any templates to revert).

Since upgrading to the latest version of vBShout (6.1.0), I can no longer see shouts, except in the Archive. This is all that displays in the shoutbox currently: I also tried pruning the shoutbox to see if that would have any effect on it, but nothing continues to display.