Since yesterday, when i try to access the message board from one of our office computers, I get an error message, then the message that i have been blocked from accessing the board, and then "333 is 666" or something of that nature. This is on a network computer but from the other computer, I don't have any problems. Has this happened to anyone else, is the problem from the Mugoo board of could it be an anti-Mac network admin who's pulling my leg..?
What you are seeing on the "offending" computer is a cached page. The message board is definitely NOT generating this error message any more. I am certain because I can see the error logs, and right now all that they contain are bad password login attempts.
If you are in an office where your access to the outside world is through a proxy server, the page may be cached by the proxy server. To test this, try going to the page from a different machine on the same network. If you do not get the error message, it is not a proxy server problem.
It is much more likely that what you are seeing has been cached by your browser. Clear your browser cache and remove any cookies related to MUGOO. The message board sets a cookie which can be safely removed.
If you don't wish to make the changes suggested above, use a different browser on the same machine and see what you get. For example, my Firefox browser kept showing me the 666 message, but Internet Exploder worked fine. Clearing the cache and cookie cured Firefox.
If none of these suggestions work (or even if they do!), please post a reply indicating what happened.
If you want to know why this happened, read the rest of this post - otherwise, you are done!
=========
Why this happened:
On Sunday, Jan 28, 2007, I "upgraded" the Apache web server to version 2.2.4 as advised by Apache! Unfortunately, version 2.2.4 contains a bug that prohibits scripts (like the message board) from detecting the inbound IP number. (This bug was only posted to BugZilla on January 27, 2007, but it has bit a lot of admins.)
The message board is set to reject any inbound IPs that look suspicious.
I "downgraded" to version 2.2.3 and that seems to solve the problem except for people who had visited the page when the bug was alive. They got the error message and their browsers cached it.