My users and myself are having issues with blank pages, forbidden and not acceptable errors, what can I do?
There is a very good chance your host has installed a add-on for apache called mod_security.
Quote:
ModSecurityTM is an open source intrusion detection and prevention engine for web applications (or a web application firewall). Operating as an Apache Web server module or standalone, the purpose of ModSecurity is to increase web application security, protecting web applications from known and unknown attacks.
While mod_security can be a very powerful tool, misconfigured or overly strict rule sets can interfere with vBulletins Operation. Below for Apache users you can use an htaccess file and add a specific rule to disable mod_security.
Make or edit your forum .htaccess file and add the following code
Code:
<IfModule mod_security.c>
SecFilterEngine Off
SecFilterScanPOST Off
</IfModule>
Note, place this file in your main forum directory.
I scroll down the forum and open multiple threads in different tabs. When I'm opening multiple messges at once, I get it on a few of them. When I get to that tab, I hit F5 and it clears it and brings up the page I was looking for. I figured it was some type of defense (denial of service) against the multiple requests from the same site in a very short time period.
The permissions on the web server are not correct. Apparently our profiles are set in various web based directories, maybe due to the meltdown and a temporary, and now, permanent new world that was created to keep the server running? That's my guess but it's added a high layer of complexity to the management of security on the TBH server.
I would recommend running syslogs to verify where the issues lie?
Not sure if the server is supporting CGI scripting and other functionality inherent with Apache? It's time for Chuck
I think it's related to the backend database as our calls to specific areas of the server are processed from the Apache front-end. That's my guess but what do I know
The permissions on the web server are not correct. Apparently our profiles are set in various web based directories, maybe due to the meltdown and a temporary, and now, permanent new world that was created to keep the server running? That's my guess but it's added a high layer of complexity to the management of security on the TBH server.
I would recommend running syslogs to verify where the issues lie?
Not sure if the server is supporting CGI scripting and other functionality inherent with Apache? It's time for Chuck
I think it's related to the backend database as our calls to specific areas of the server are processed from the Apache front-end. That's my guess but what do I know
Comment