1and1 http 500 errors

  • I’m at the end of my rope. 1and1, my hosting company, has done something (they won’t say what) to their backend that’s giving my site http 500 server-side errors for long stretches — a couple of hours at a time. Their tech support is typically clueless.

    From what I’ve gleaned, it seems like my .htaccess settings are now conflicting with whatever 1and1’s done. I can’t tell what it is or what I should fix. If anyone can offer advice, I’d appreciate.

    I’m running WP 1.2 (don’t want to upgrade at this point unless it’s absolutely necessary). Here’s my .htaccess content:

    RewriteEngine On
    RewriteBase /
    RewriteRule ^archives/category/(.*)/(feed|rdf|rss|rss2|atom)/?$ /wordpress/wp-feed.php?category_name=$1&feed=$2 [QSA]
    RewriteRule ^archives/category/?(.*) /index.php?category_name=$1 [QSA]
    RewriteRule ^archives/author/(.*)/(feed|rdf|rss|rss2|atom)/?$ /wordpress/wp-feed.php?author_name=$1&feed=$2 [QSA]
    RewriteRule ^archives/author/?(.*) /index.php?author_name=$1 [QSA]
    RewriteRule ^archives/([0-9]{4})?/?([0-9]{1,2})?/?([0-9]{1,2})?/?([_0-9a-z-]+)?/?([0-9]+)?/?$ /index.php?year=$1&monthnum=$2&day=$3&name=$4&page=$5 [QSA]
    RewriteRule ^archives/([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/([_0-9a-z-]+)/(feed|rdf|rss|rss2|atom)/?$ /wordpress/wp-feed.php?year=$1&monthnum=$2&day=$3&name=$4&feed=$5 [QSA]
    RewriteRule ^archives/([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/([_0-9a-z-]+)/trackback/?$ /wordpress/wp-trackback.php?year=$1&monthnum=$2&day=$3&name=$4 [QSA]
    RewriteRule ^feed/?([_0-9a-z-]+)?/?$ /wordpress/wp-feed.php?feed=$1 [QSA]
    RewriteRule ^comments/feed/?([_0-9a-z-]+)?/?$ /wordpress/wp-feed.php?feed=$1&withcomments=1 [QSA]
    RewriteCond %{HTTP_REFERER} !^$
    RewriteCond %{HTTP_REFERER} !^https://(.*).populationstatistic.(.*)/.*$ [NC]
    RewriteCond %{HTTP_REFERER} !^https://populationstatistic.(.*)/.*$ [NC]
    RewriteRule (.*.(gif|jpg|avi|mpg)$) https://populationstatistic.com/images/rewrite.gif [R,NC]

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

  • i use 1and1 also, and even though i’m working on my blog, redesigning it and what not, and it looks like shizz, it’s working just fine. you might want to upgrade to the latest wp version.

    Same here…. I’ve been using 1and1 for a couple of years now, and WP on it for nearly just as long…. never a problem.
    You may not like the answer of upgrading, but there were ALOT of things fixed between 1.2 and 1.5.2….. And this maybe one of those things.

    -tg

    Thread Starter popstat

    (@popstat)

    Several months later, this is moot, as I’ve since upgraded to 1.5.x… But I can tell you that running 1.2 was absolutely not the problem in this case. So, as I said, this was a non-response case.

    Moderator James Huff

    (@macmanx)

    If you would have responded with that information sooner, we probably would have helped you solve the issue, and this would not have remained a (as you have so politely labeled it) “a non-response case”.

    Contrary to popular believe, “just upgrade” is a common solution, and works at least 50% of the time. Not mention that it also keeps you safe from the known security vulnerabilities that exist before the upgrade’s release. If “just upgrade” did not work for you, please respond to that fact, and we will help you find the proper solution.

    Also, due to the volume of posts of this forum and the volunteer nature of its staff, we cannot support obsolete versions of WordPress.

    Thread Starter popstat

    (@popstat)

    Again, all this came and went months ago, so it’s moot. But:

    – At the time of the original post, I wasn’t sure whether or not it was a 1.2 issue. By the time I determined it wasn’t, I’d given up on getting any response here, since there was none forthcoming (aside from the upgrade advice).

    – I wouldn’t call 50% a “common” solution. That means half the people who upgrade as a potential solution do so needlessly. And contrary to the lingo here, upgrading is not a simple process for many, due to customization a lot of us perform. My upgrade from 1.2 to 1.5 was, as I predicted, rocky. Which was why I avoided it at first.

    – Since, again, the problem referenced here turned out to not be a version issue, I don’t see why support for obsolete versions of WP even enters this discussion.

    This is all I’ve got to say on the subject here. If each .x upgrade signals the end of support expections for prior versions, fine; I’ll keep it in mind in the future.

    Moderator James Huff

    (@macmanx)

    – I wouldn’t call 50% a “common” solution. That means half the people who upgrade as a potential solution do so needlessly.

    I wouldn’t say that they do so needlessly. Like I said, “it also keeps you safe from the known security vulnerabilities that exist before the upgrade’s release.” In other words, upgrading is for your own good.

    – Since, again, the problem referenced here turned out to not be a version issue, I don’t see why support for obsolete versions of WP even enters this discussion.

    The point is that, due to the volume of posts of this forum and the volunteer nature of its staff, we cannot support obsolete versions of WordPress. Though you have finally upgraded, you were running v1.2 (an obsolete version) at the time of posting and you were refusing to upgrade to v1.5. That is why support for obsolete versions of WP entered this discussion.

    If you think that the changes between v1.2 and v1.5 are minor, try looking at the code again. They are almost two different blogging platforms. Upgrading may not fix your current problem, but it will help us to find a solution to your problem.

    If you think that we should continue to support obsolete versions of WordPress, then feel free to start paying us, or become a volunteer in these forums and specialize in answering v1.2 questions.

    Again, due to the volume of posts of this forum and the volunteer nature of its staff, we cannot support obsolete versions of WordPress.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘1and1 http 500 errors’ is closed to new replies.