I've been working on our Cloudflare settings for about a week now, and I've found that settings that work on the main site don't work on the subdomain, so blanket settings needed to be coded for one and not the other, and vice versa.

With that said, I've made some tweaks in the last few minutes, as I believe the login/logout issue is due to the SON Community caching itself for speed, which would explain why, when some users attempt to log in, nothing seems to happen. Thank you for the screenshots; they gave me something to look at in terms of what to look for.

Thanks @ranger1rg that's mine too.

34 minutes ago, ranger1rg said:

Errol, here's what I get when I attempt to login on Chrome.

As soon as I enter my username and password, they disappear and I'm returned to the same page.

I have cleared my cache numerous times but that hasn't helped.

Just to be clear, by username, you mean your email address, correct?

4 minutes ago, Errol said:

Just to be clear, by username, you mean your email address, correct?

Yes. Sorry I misspoke.

6 minutes ago, ranger1rg said:

Yes. Sorry I misspoke.

No worries. Just wanted to make sure we were on the same page.

@Errol Just got the "error 500" message again.

2 hours ago, Liberty City said:

@Errol Just got the "error 500" message again.

Found the problem. Implemented the solution. Shouldn't happen again.

50 minutes ago, Errol said:

Found the problem. Implemented the solution. Shouldn't happen again.

Now I am having difficulty making posts, and the board keeps loading weird. 🫠

Edited 16 hours ago16 hr by Liberty City

The max connections issue has been happening due to a larger frequency of visits to the message boards, particularly by bots. Despite blocking them in Cloudflare, a large amount of traffic is still being tracked by Google Analytics from places like Japan, Vietnam, Singapore, etc.

Regardless, the issue is being fully resolved: I've increased the max_connections to 500 (default was 150). However, to maintain the stability of the MySQL database that holds information about the SON Community, we need to use a caching service such as Redis. After my last response, I tried turning the setting on, but it failed because the required port number had not yet been enabled by our hosting company.

Once enabled, hopefully it will finally, finally, finally resolve the 500 error and, with it, the login/logout issue, which I believe started occurring due to a misconfigured setting in our Data Storage Method (MySQL database vs. file system vs. Redis).

Long-winded response. Hopefully, with actual solutions forthcoming.

5 minutes ago, Errol said:

The max connections issue has been happening due to a larger frequency of visits to the message boards, particularly by bots. Despite blocking them in Cloudflare, a large amount of traffic is still being tracked by Google Analytics from places like Japan, Vietnam, Singapore, etc.

Regardless, the issue is being fully resolved: I've increased the max_connections to 500 (default was 150). However, to maintain the stability of the MySQL database that holds information about the SON Community, we need to use a caching service such as Redis. After my last response, I tried turning the setting on, but it failed because the required port number had not yet been enabled by our hosting company.

Once enabled, hopefully it will finally, finally, finally resolve the 500 error and, with it, the login/logout issue, which I believe started occurring due to a misconfigured setting in our Data Storage Method (MySQL database vs. file system vs. Redis).

Long-winded response. Hopefully, with actual solutions forthcoming.

Love the update - thanks, @Errol! Appreciate you working hard.

I have formally completed the installation of the Redis system, which now handles our Data Storage, and should ease the burden on MySQL. I'm expecting this will now solve all the issues, as Error 500 was a max_connections issue (MySQL), and inadvertently, MySQL wasn't being utilized as the Data Storage method, which likely also caused the issues with login/logout, since nothing was writing to the database.

Of course, ya'll will tell me if all that work was worth it or not, and I hope it was.

7 hours ago, Errol said:

I have formally completed the installation of the Redis system, which now handles our Data Storage, and should ease the burden on MySQL. I'm expecting this will now solve all the issues, as Error 500 was a max_connections issue (MySQL), and inadvertently, MySQL wasn't being utilized as the Data Storage method, which likely also caused the issues with login/logout, since nothing was writing to the database.

Of course, ya'll will tell me if all that work was worth it or not, and I hope it was.

Thanks for all of this, Errol. I know it must be pain dealing with so much, but you've done an impeccable job thus far.