Personally I think they do it to cut down on the number of support calls because different hosting providers run with different user/group for the https process. It's easier to tell people to chmod the hell out of any folder needing write access rather than try to explain what I've tried to explain here and what I've tried to explain here is part of how the GoDaddy hack went down. My h4x0r linkBut that's just me and I don't trust vendors farther than I can throw a boat anchor. :cheers:Without seeing the logs I couldn't tell you but when the connection is refused that typically means the https server process isn't running on the server and the OS is rejecting the connection.IPB is doing the hosting and you'd think that they'd know how to set the permissions correctly. Also if httpsd was crashing, that wouldn't explain why things get better when we turn off searches.

Periodic timeouts... [MEGA-MERGED]
#41
Posted 20 September 2011 - 12:33 PM
#42
Posted 20 September 2011 - 12:45 PM
Yes absolutely but if httpsd is starved due to a very long db query the same thing could happen. But then that would imply that they're running on Windows or other defective OS.Without seeing the logs I couldn't tell you but when the connection is refused that typically means the https server process isn't running on the server and the OS is rejecting the connection.
#43
Posted 20 September 2011 - 12:57 PM
It appears it is Apache 2.2.16 on some sort of *nix. That version of Apache is vulnerable to the range header flaw (if they haven't implemented one of the work arounds) and you guys could be getting DOS'd, although I doubt it. It could be a DB query, it could be a PHP problem, it could be any of the Apache modules but without the Apache error log (if it is crashing) we are shooting in the dark.Yes absolutely but if httpsd is starved due to a very long db query the same thing could happen. But then that would imply that they're running on Windows or other defective OS.
#44
Posted 20 September 2011 - 01:36 PM

#45
Posted 20 September 2011 - 01:38 PM
#46
Posted 20 September 2011 - 01:45 PM
#47
Posted 20 September 2011 - 02:11 PM
#48
*_Guest_BigBossMan_*
Posted 20 September 2011 - 09:19 PM
I had that same thought. That things are acting like there is some half assed DOS attack going on.It appears it is Apache 2.2.16 on some sort of *nix. That version of Apache is vulnerable to the range header flaw (if they haven't implemented one of the work arounds) and you guys could be getting DOS'd, although I doubt it. It could be a DB query, it could be a PHP problem, it could be any of the Apache modules but without the Apache error log (if it is crashing) we are shooting in the dark.
#49
Posted 21 September 2011 - 10:11 AM
2 user(s) are reading this topic
0 members, 2 guests, 0 anonymous users