Forum Replies Created

Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter lassirra

    (@lassirra)

    Nope, I tried it and had no luck. I’m not sure whether it was a matter of the file format I was using or what, but whenever I attempted to use it to embed, I got blank “plug-in required” boxes in my browser that led nowhere (firefox couldn’t find any plugin for whatever the embed was trying to do). Either way, the bottom line was that viper didn’t do what I needed it to, unfortunately.

    I’ve had exactly the same problem, with the same results.

    I consistently clean out the database to make sure it’s not loading (or auto-loading) anything it shouldn’t be and there aren’t orphaned entries kicking around. Also, I run WP Super Cache. I’ve moved the install to a VPS with 512mb RAM and it’s the only site on the server, and it still crashes. I can’t keep the site up for longer than 24 hours without a server restart. My site doesn’t typically get more than 30k visitors per month, so I know it’s not a matter of traffic itself bringing the server down–a lot more popular sites running on smaller servers seem to do just fine.

    This has been a problem for me for the better part of a year now, I’ve tried everything I could think of to try. I’ve checked with my hosting providers and they’re stumped too.

    I’m losing visitor loyalty, credibility, Alexa and Technorati rankings and advertising revenue the longer this problem persists. (Ad revenue has dropped 50% and my Alexa rank has gone down 40k.) Not to mention the wasted time trying to troubleshoot this issue.

    At this point, I’m clearly extremely frustrated and at my wit’s end. Any suggestions for things I haven’t tried yet would be greatly appreciated. I’m really sick of this. (And I apologize for the tone–I’m simultaneously trying to vent frustration and find a solution, heh.)

    Hopefully someone knows what the heck is going on here, because I sure don’t.

    I’m having serious memory issues myself at the moment. I’ve tried both wp-cache and wp-super-cache and both seem to make the problem worse, rather than better.

    My site was shut down by my host for memory usage and moved to a temp server. I then moved my site to a VPS with 2gb of ram in the box, and my site was crashing the VPS daily.

    I don’t have what I would call an overly popular site. (About 700 RSS subscribers, according to Feedburner.) This is something that needs to be addressed.

    Any word on this?

    I run minimal plug-ins, tried wp-cache and wp-super-cache, and still my blog crashes and requires a server restart on an almost daily basis. While my blog gets decent traffic, it’s by no means enough to crash a server that has only my site on it, and 2GB of memory in the box.

    Forum: Fixing WordPress
    In reply to: 500 Internal Error
    Thread Starter lassirra

    (@lassirra)

    As per my host’s instructions, I actually removed the following line altogether:
    AddHandler x-httpd-<IfModule mod_rewrite.c>
    And deleted the duplicate entries (though I’m not sure where the duplicate entries came from in the first place–I’ve never modified the .htaccess file manually).
    I did notice the f and had already removed it, after running the .htaccess file through a validator (https://www.lyxx.com/freestuff/002.html).

    I had actually tried all those things previously and had still been experiencing the 500 error. After fiddling with it for a while, I tried again, and it actually worked, so I’m not sure what else may have changed.

    Thanks for the help (though I could’ve lived without the profanity).

    Forum: Fixing WordPress
    In reply to: 500 Internal Error
    Thread Starter lassirra

    (@lassirra)

    I corrected the “typo” on line 4:
    ReRewriteCond %{REQUEST_FILENAME} !-f
    To:
    RewriteCond %{REQUEST_FILENAME} !-f

    And still experience the error described above.

Viewing 6 replies - 1 through 6 (of 6 total)