SMF Support > SMF 1.1.x Support
SMF 1.1.9 - You were unable to login. Please check your cookie settings.
K@:
That could be it, then.
mod_security should be disabled. :)
Wabiloo:
I don't think that's it...
Here is what the hosting company's support team has to say about it:
I've checked the error log and it doesn't look like mod_security is flagging anything and it would be extremely unlikely for it to stop a login form. Also nothing has changed with the mod_security ruleset recently.
mod_security has to be turned on to protect the server because it is shared with many customers and not all customers tend to write the most secure code so it needs the software firewall.
K@:
I think your host's having a laugh.
mod_security isn't that effective.
All it does, is look for words like ”poker”, ”pictures”, or ”sex” and words containing the letters, to block comment and referrer spam.
It has zilch to do with code, as I understand it.
Your host is either spinning you a line, or they're Godaddy totally incompetent.
Almost every site with SMF on it has mod_security disabled, if not all of them.
If the word "Sex" is blocked, for example, anything like "Wessex", "Essex", etc. can cause problems.
Even a term like "Less extreme" can trigger the damned thing.
Wabiloo:
Well, maybe so, but I have no control over this.
Plus, they've clearly always had it on, and the forum used to work until a few weeks ago...
There must be something else going on here...
K@:
The thing is, if it's on, it's bound to screw something, sometime.
Maybe the switch from Winderz to Apache was where this cropped up?
Tell ya what... What if you ask them to disable it, temporarily, just to prove whether or not this is what the problem is?
If they disable it and everything works, we'll know what the problem is.
If they disable it and the problem persists, we'll know that we have to look at something else.
But, as you haven't changed anything and this hassle seems to have appeared at around the time that they switched systems, it seems, to me, to be pointing to that being the problem.
In all honesty, I can't think of anything else that could be causing this, at all.
That doesn't mean that it might not be something else. Someone with a bit more knowledge than I have might have other ideas. But, for me, this is really screaming "mod_security"!!!
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version