Viewing 15 replies - 16 through 30 (of 57 total)
  • I think if you delete your other theme folders (backed up of course) wp will default to the “default” folder. If not, reinstall wp and don’t install any themes/plugins. does it work?

    are you on dreamhost by chance? If so, localhost doesn’t work.

    Thread Starter yo139

    (@yo139)

    I already re installed it like 3 times. It works but then ends up breaking in a day or two again.

    And I use cirtex hosting

    Did you look for any other ,htaccess files that are named something different?

    Like this .htaccess.addHandlerBak?

    Just curious.

    And another thing, Why the hell would a CMS like WordPress allow this type of activity? Clearly, by default, .htaccess should not allow someone to browse file like this.

    https://www.thegamerscafe.net/wp-includes/

    Thread Starter yo139

    (@yo139)

    There is a .htaccessbak

    What could that mean?

    If that is anything like mine, it overrides your admin privileges and allows the hacker to edit basically any file they choose.

    I’m not 100% positive but, I’m pretty certain that is not a default WordPress .htaccess file.

    I just posted this in another forum.

    I just repaired a major hacked site myself. It was a complete pain in my ass.

    Look for .htaccess.addHandlerBak or any .htaccess that doesn’t belong there and delete it immediately!

    Because NOONE responded to any of my requests, I will only tell you what I found on my server. As you can see here HERE

    Your file changes look almost identical to mine and the hackers added files throughout my server that mirrored certain files in my directory but added a prefix to the file, Mine was fx_

    Through these files and the .htaccess.addHandlerBak they essentially had overridden my admin privileges and made their own through .htaccess. They also uploaded some sort of admin panel of their own (eval script) I believe, that gave them full reign of my main directory and mysql database as well.

    I would suggest backing up your current theme, database and completely delete ALL current files on your host and uploading a fresh install of WordPress 2.5.1.

    Be sure to double, tipple check your theme for files you don’t recognize and delete those files before uploading to the server. Otherwise it’s a backdoor for them to get back in.

    I also read somewhere to add an index.html file to your plugins directory to prevent hackers from browsing that directory. (A sort of dumb thing for WordPress to leave out in my opinion)

    Browse MySql wp_options / current_plugins for any suspicious looking code that pertains to uploads or .jpg images.

    Check all of your uploads in your current theme for any file you don’t recognize and delete.

    Also, Look here , you might find a few things that help (even though It didn’t help me much)

    Also, if your hosting company offers fantastico wordpress setup and you do a manual install. I found out that the old version installed on fantastico can be hack which compromises your current (up to date) installation.

    You might want to contact your hosting company to see if your server has been compromised in any way.

    Good luck.

    Thread Starter yo139

    (@yo139)

    The .htaccessback is suppose to be there I believe

    I just cant see it being a hacker at this point. Why would they want to jack up my site that I just bought the domain for like last week. My other site has been running fine through this whole thing and it is on the same hosting.

    I had a site, no lie, that was hacked within a week on a brand new server brand new domain, brand new install.

    I think they robot WordPress for it’s vulnerabilities. I might be crazy but, that’s the only way someone could have possibly found my new site that was hacked.

    Don’t kid yourself by thinking WordPress is hackersafe. No matter how new the site is.

    I’d love to see that .htaccessbak file (edited for safety of course)

    Thread Starter yo139

    (@yo139)

    Here it is

    <IfModule mod_security.c> # Turn off mod_security filtering. SMF is a big boy, it doesn’t need its hands held. SecFilterEngine Off # The below probably isn’t needed, but better safe than sorry. SecFilterScanPOST Off</IfModule>

    SMF is simple machines forums which I run

    The .htaccessback is suppose to be there I believe

    no, it is not. its a useless file, named as such, and regardless of how it got there, its not doing anything.

    Thread Starter yo139

    (@yo139)

    I know that I mean I dont think it was added by a hacker or anything

    I Just got rid of it

    Well… My file actually was some sort of redirect for the admin. It had a password associated with it that allowed the attacker to edit my files. Not sure about yours.

    Thread Starter yo139

    (@yo139)

    Seriously? What should I do now?

    you havent described anything that is even remotely diagnosable. What do your error_logs say? If you dont have error logs, enable them.

    I changed my post above.. I don’t claim to be an expert but, I was hacked and no one in here had any answers. I found the problems myself.

    Do you see any funny files in your recent uploads file? Do you use FTP?

    Thread Starter yo139

    (@yo139)

    “you havent described anything that is even remotely diagnosable. What do your error_logs say? If you dont have error logs, enable them.”

    Here is my error log page

    [8732] EACCELERATOR: PHP crashed on opline 109 of (null)() at /home/wiilenet/public_html/TheGamersCafe.net/wp-includes/theme.php:91
    [9787] EACCELERATOR: PHP crashed on opline 109 of (null)() at /home/wiilenet/public_html/TheGamersCafe.net/wp-includes/theme.php:91
    [Mon Jul 7 21:00:41 2008] [error] [client 76.189.79.8] client denied by server configuration: /home/wiilenet/public_html/TheGamersCafe.net/.htaccess
    [Mon Jul 7 21:00:37 2008] [error] [client 76.189.79.8] client denied by server configuration: /home/wiilenet/public_html/TheGamersCafe.net/.htaccessbak
    [5211] EACCELERATOR: PHP crashed on opline 109 of (null)() at /home/wiilenet/public_html/TheGamersCafe.net/wp-includes/theme.php:91
    [9173] EACCELERATOR: PHP crashed on opline 109 of (null)() at /home/wiilenet/public_html/TheGamersCafe.net/wp-includes/theme.php:91
    [Mon Jul 7 20:51:24 2008] [error] [client 76.189.79.8] client denied by server configuration: /home/wiilenet/public_html/TheGamersCafe.net/.htaccessbak
    [Mon Jul 7 20:51:20 2008] [error] [client 76.189.79.8] client denied by server configuration: /home/wiilenet/public_html/TheGamersCafe.net/.htaccessbak
    [8722] EACCELERATOR: PHP crashed on opline 109 of (null)() at /home/wiilenet/public_html/TheGamersCafe.net/wp-includes/theme.php:91
    [Mon Jul 7 20:27:23 2008] [error] PHP Fatal error: Call to undefined function: get_header() in /home/wiilenet/public_html/TheGamersCafe.net/wp-content/themes/default/index.php on line 1
    [Mon Jul 7 20:26:53 2008] [error] PHP Fatal error: Call to undefined function: get_header() in /home/wiilenet/public_html/TheGamersCafe.net/wp-content/themes/default/index.php on line 1
    [Mon Jul 7 20:26:50 2008] [error] PHP Fatal error: Call to undefined function: get_header() in /home/wiilenet/public_html/TheGamersCafe.net/wp-content/themes/classic/index.php on line 2
    [Mon Jul 7 20:25:00 2008] [error] PHP Fatal error: Call to undefined function: is_robots() in /home/wiilenet/public_html/TheGamersCafe.net/wp-includes/template-loader.php on line 66
    [Mon Jul 7 20:24:25 2008] [error] PHP Fatal error: Call to undefined function: add_action() in /home/wiilenet/public_html/TheGamersCafe.net/wp-content/plugins/akismet/akismet.php on line 25
    [7672] EACCELERATOR: PHP crashed on opline 109 of (null)() at /home/wiilenet/public_html/TheGamersCafe.net/wp-includes/theme.php:91
    [Mon Jul 7 20:24:02 2008] [error] PHP Fatal error: Call to undefined function: get_header() in /home/wiilenet/public_html/TheGamersCafe.net/wp-content/themes/classic/index.php on line 2
    [Mon Jul 7 20:23:56 2008] [error] PHP Fatal error: Call to undefined function: get_header() in /home/wiilenet/public_html/TheGamersCafe.net/wp-content/themes/default/index.php on line 1
    [3332] EACCELERATOR: PHP crashed on opline 109 of (null)() at /home/wiilenet/public_html/TheGamersCafe.net/wp-includes/theme.php:91
    [3063] EACCELERATOR: PHP crashed on opline 11 of (null)() at /home/wiilenet/public_html/TheGamersCafe.net/wp-includes/kses.php:949
    [2153] EACCELERATOR: PHP crashed on opline 109 of (null)() at /home/wiilenet/public_html/TheGamersCafe.net/wp-includes/theme.php:91
    [29676] EACCELERATOR: PHP crashed on opline 109 of (null)() at /home/wiilenet/public_html/TheGamersCafe.net/wp-includes/theme.php:91

Viewing 15 replies - 16 through 30 (of 57 total)
  • The topic ‘WordPress keeps breaking No clue whats wrong’ is closed to new replies.