This can't be stated enough, contact board administrator.

[wizard4]

An error has been encountered in accessing this page.

1. Server: irrlicht.sourceforge.io
2. URL path: /forum/viewtopic.php
3. Error notes: Server unable to read htaccess file, denying access to be safe
4. Error type: 403
5. Request method: GET
6. Request query string: p=308367
7. Time: 2025-03-07 15:10:37 UTC (1741360237)

The main Sourceforge web site runs like a dream, even downloading the code has no problems. The forums inaccessible most times I try. I'd like this to be fixed if possible. Too many times I've seen error messages on this board and fiddling about with posting.

[Brainsaw]

Yes, it's a bit annoying, but as this is no commercial service I keep calm and don't panic

[CuteAlien]

Yeah, to our knowledge it happens when the sourceforge servers are overloaded. And yes, main sourceforge servers seem to have a bit more priority than project forums (svn on the other hand is also often overloaded). Anyway - I wish we could do something about it, but we can't. Otherwise we would have fixed it years ago.

My feeling is that it's usually worse around the time we have spam-bot attacks (just had some which got through yesterday). So basically forum getting ddos'ed and we have not enough rights on the server to fight back. For example we can't block IP's as there is a cache-server involved and our forum only sees the cache-server IP.

[wizard4]

I saw it as something that was put off and stuck in a todo list that kept the admin up at night.

I was about to contact the Sourceforge support but as this is irrlicht.sourceforge it's not their domain, so to speak.

I think something needs addressing that is a bother to attempt and actually is easier to forget about than fix?

[CuteAlien]

How to address - "the servers are overloaded" when you have no control over the server? It's annoying as hell, but in the end we're guests on free servers. Other services like github won't even provide this much. Pretty much the alternative is closing the forum (which we won't).

[wizard4]

I think if you nust ham the back button and try again it eventually works.

[CuteAlien]

*sigh* so it was down again. We seem to have currently some problem with cache messing up regularly. Not quite my area of expertise, but at least now I know some workaround (delete whole cache...). I hope I can find out more, have to learn a bit about debugging PHP first :-)